website: Fix several spelling errors

website/docs/commands/0.12upgrade.html.markdown

@@ -36,7 +36,7 @@ Terraform v0.12.
 
 We recommend using this command in a clean version control work tree, so that
 you can easily see the proposed changes as a diff against the latest commit.
-If you have uncommited changes already present, we recommend aborting this
+If you have uncommitted changes already present, we recommend aborting this
 command and dealing with them before running this command again.
 
 Would you like to upgrade the module in the current directory?

website/docs/commands/cli-config.html.markdown

@@ -96,6 +96,6 @@ longer recommended for use:
 * `providers` - a configuration block that allows specifying the locations of
   specific plugins for each named provider. This mechanism is deprecated
   because it is unable to specify a version number for each plugin, and thus
-  it does not co-operate with the plugin versioning mechansim. Instead,
+  it does not co-operate with the plugin versioning mechanism. Instead,
   place the plugin executable files in
   [the third-party plugins directory](/docs/configuration/providers.html#third-party-plugins).

website/docs/commands/init.html.markdown

@@ -81,7 +81,7 @@ During init, the root configuration directory is consulted for
 [backend configuration](/docs/backends/config.html) and the chosen backend
 is initialized using the given configuration settings.
 
-Re-running init with an already-initalized backend will update the working
+Re-running init with an already-initialized backend will update the working
 directory to use the new backend settings. Depending on what changed, this
 may result in interactive prompts to confirm migration of workspace states.
 The `-force-copy` option suppresses these prompts and answers "yes" to the

website/docs/commands/plan.html.markdown

@@ -113,7 +113,7 @@ large configurations, prefer instead to break large configurations into
 several smaller configurations that can each be independently applied.
 [Data sources](/docs/configuration/data-sources.html) can be used to access
 information about resources created in other configurations, allowing
-a complex system architecture to be broken down into more managable parts
+a complex system architecture to be broken down into more manageable parts
 that can be updated independently.
 
 ## Security Warning

website/docs/configuration-0-11/interpolation.html.md

@@ -392,7 +392,7 @@ The supported built-in functions are:
   * `slice(list, from, to)` - Returns the portion of `list` between `from` (inclusive) and `to` (exclusive).
       Example: `slice(var.list_of_strings, 0, length(var.list_of_strings) - 1)`
 
-  * `sort(list)` - Returns a lexographically sorted list of the strings contained in
+  * `sort(list)` - Returns a lexicographically sorted list of the strings contained in
       the list passed as an argument. Sort may only be used with lists which contain only
       strings.
       Examples: `sort(aws_instance.foo.*.id)`, `sort(var.list_of_strings)`

website/docs/configuration-0-11/variables.html.md

@@ -287,7 +287,7 @@ one variable file, the last value specified is effective.
 ### Variable Merging
 
 When multiple values are provided for the same input variable, map values are
-merged while all other values are overriden by the last definition.
+merged while all other values are overridden by the last definition.
 
 For example, if you define a variable twice on the command line:
 

website/docs/configuration/data-sources.html.md

@@ -108,7 +108,7 @@ For example, local-only data sources exist for
 
 The behavior of local-only data sources is the same as all other data
 sources, but their result data exists only temporarily during a Terraform
-operation, and is re-calulated each time a new plan is created.
+operation, and is re-calculated each time a new plan is created.
 
 ## Data Resource Dependencies
 

website/docs/configuration/functions/distinct.html.md

@@ -15,7 +15,7 @@ earlier, see
 `distinct` takes a list and returns a new list with any duplicate elements
 removed.
 
-The first occurence of each value is retained and the relative ordering of
+The first occurrence of each value is retained and the relative ordering of
 these elements is preserved.
 
 ## Examples

website/docs/configuration/functions/jsonencode.html.md

@@ -16,7 +16,7 @@ earlier, see
 
 The JSON encoding is defined in [RFC 7159](https://tools.ietf.org/html/rfc7159).
 
-This fucntion maps
+This function maps
 [Terraform language values](../expressions.html#types-and-values)
 to JSON values in the following way:
 

website/docs/configuration/functions/replace.html.md

@@ -4,7 +4,7 @@ page_title: "replace - Functions - Configuration Language"
 sidebar_current: "docs-funcs-string-replace"
 description: |-
   The replace function searches a given string for another given substring,
-  and replaces all occurences with a given replacement string.
+  and replaces all occurrences with a given replacement string.
 ---
 
 # `replace` Function
@@ -14,7 +14,7 @@ earlier, see
 [0.11 Configuration Language: Interpolation Syntax](../../configuration-0-11/interpolation.html).
 
 `replace` searches a given string for another given substring, and replaces
-each occurence with a given replacement string.
+each occurrence with a given replacement string.
 
 ```hcl
 replace(string, substring, replacement)

website/docs/configuration/functions/split.html.md

@@ -4,7 +4,7 @@ page_title: "split - Functions - Configuration Language"
 sidebar_current: "docs-funcs-string-split"
 description: |-
   The split function produces a list by dividing a given string at all
-  occurences of a given separator.
+  occurrences of a given separator.
 ---
 
 # `split` Function
@@ -13,7 +13,7 @@ description: |-
 earlier, see
 [0.11 Configuration Language: Interpolation Syntax](../../configuration-0-11/interpolation.html).
 
-`split` produces a list by dividing a given string at all occurences of a
+`split` produces a list by dividing a given string at all occurrences of a
 given separator.
 
 ```hcl

website/docs/configuration/syntax-json.html.md

@@ -316,7 +316,7 @@ mapping rules that apply to each top-level block type.
 
 Some meta-arguments for the `resource` and `data` block types take direct
 references to objects, or literal keywords. When represented in JSON, the
-reference or keyword is given as a JSON string with no additonal surrounding
+reference or keyword is given as a JSON string with no additional surrounding
 spaces or symbols.
 
 For example, the `provider` meta-argument takes a `<PROVIDER>.<ALIAS>` reference

website/docs/configuration/syntax.html.md

@@ -88,7 +88,7 @@ require none as with the nested `network_interface` block type.
 
 After the block type keyword and any labels, the block _body_ is delimited
 by the `{` and `}` characters. Within the block body, further arguments
-and blocks may be nested, creating a heirarchy of blocks and their associated
+and blocks may be nested, creating a hierarchy of blocks and their associated
 arguments.
 
 The Terraform language uses a limited number of _top-level block types,_ which

website/docs/modules/composition.html.markdown

@@ -220,7 +220,7 @@ output "hostname" {
 ```
 
 You can then write _other_ modules that expect only a Kubernetes cluster
-hostname as input and use them interchangably with any of your Kubernetes
+hostname as input and use them interchangeably with any of your Kubernetes
 cluster modules:
 
 ```hcl

website/docs/modules/sources.html.markdown

@@ -203,7 +203,7 @@ suitable credentials for that repository.
 
 If you use the SSH protocol then any configured SSH keys will be used
 automatically. This is the most common way to access non-public Git
-repositories from automated systems beacuse it is easy to configure
+repositories from automated systems because it is easy to configure
 and allows access to private repositories without interactive prompts.
 
 If using the HTTP/HTTPS protocol, or any other protocol that uses
@@ -250,7 +250,7 @@ with suitable credentials for that repository.
 
 If you use the SSH protocol then any configured SSH keys will be used
 automatically. This is the most common way to access non-public Mercurial
-repositories from automated systems beacuse it is easy to configure
+repositories from automated systems because it is easy to configure
 and allows access to private repositories without interactive prompts.
 
 If your Terraform configuration will be used within [Terraform Enterprise](https://www.hashicorp.com/products/terraform),

website/docs/state/environments.html.md

@@ -12,7 +12,7 @@ The term _state environment_, or just _environment_, was used within the
 Terraform 0.9 releases to refer to the idea of having multiple distinct,
 named states associated with a single configuration directory.
 
-After this concept was implemented, we recieved feedback that this terminology
+After this concept was implemented, we received feedback that this terminology
 caused confusion due to other uses of the word "environment", both within
 Terraform itself and within organizations using Terraform.
 

website/upgrade-guides/0-11.html.markdown

@@ -270,7 +270,7 @@ configurations, see [_Providers Within Modules_](/docs/configuration-0-11/module
 
 ## Error Checking for Output Values
 
-Prior to Terraform 0.11, if an error occured when evaluating the `value`
+Prior to Terraform 0.11, if an error occurred when evaluating the `value`
 expression within an `output` block then it would be silently ignored and
 the empty string used as the result. This was inconvenient because it made it
 very hard to debug errors within output expressions.