Merge pull request #8779 from TimeIncOSS/docs-fix-misspellings

docs: Fix misspelled words

website/source/assets/stylesheets/_announcement-bnr.scss

@@ -7,7 +7,7 @@ $enterprise-bnr-consul-color: #B52A55;
 $enterprise-color-dark-white: #A9B1B5;
 
 body{
-  // when _announcment-bnr.erb (ie. Consul Enterprise Announcment) is being used in layout we need to push down content to accomodate
+  // when _announcment-bnr.erb (ie. Consul Enterprise Announcment) is being used in layout we need to push down content to accommodate
   // add this class to body
   &.-displaying-bnr{
     #header{

website/source/docs/configuration/interpolation.html.md

@@ -113,7 +113,7 @@ The supported built-in functions are:
      Example: `concat(aws_instance.db.*.tags.Name, aws_instance.web.*.tags.Name)`
 
   * `distinct(list)` - Removes duplicate items from a list. Keeps the first
-     occurrence of each element, and removes subsequent occurences. This
+     occurrence of each element, and removes subsequent occurrences. This
      function is only valid for flat lists. Example: `distinct(var.usernames)`
 
   * `element(list, index)` - Returns a single element from a list

website/source/docs/providers/aws/index.html.markdown

@@ -203,7 +203,7 @@ The following arguments are supported in the `provider` block:
   (static credentials set as ENV vars or config)
 
 * `s3_force_path_style` - (Optional) set this to true to force the request to use
-  path-style adressing, i.e., http://s3.amazonaws.com/BUCKET/KEY. By default, the
+  path-style addressing, i.e., http://s3.amazonaws.com/BUCKET/KEY. By default, the
   S3 client will use virtual hosted bucket addressing when possible
   (http://BUCKET.s3.amazonaws.com/KEY). Specific to the Amazon S3 service.
 

website/source/docs/providers/aws/r/alb_target_group.html.markdown

@@ -32,7 +32,7 @@ resource "aws_vpc" "main" {
 The following arguments are supported:
 
 * `name` - (Required) The name of the target group.
-* `port` - (Required) The port on which targets receive traffic, unless overriden when registering a specific target.
+* `port` - (Required) The port on which targets receive traffic, unless overridden when registering a specific target.
 * `protocol` - (Required) The protocol to use for routing traffic to the targets.
 * `vpc_id` - (Required) The identifier of the VPC in which to create the target group.
 * `deregistration_delay` - (Optional) The amount time for Elastic Load Balancing to wait before changing the state of a deregistering target from draining to unused. The range is 0-3600 seconds. The default value is 300 seconds. 

website/source/docs/providers/aws/r/autoscaling_lifecycle_hooks.html.markdown

@@ -46,7 +46,7 @@ EOF
 The following arguments are supported:
 
 * `name` - (Required) The name of the lifecycle hook.
-* `autoscaling_group_name` - (Requred) The name of the Auto Scaling group to which you want to assign the lifecycle hook
+* `autoscaling_group_name` - (Required) The name of the Auto Scaling group to which you want to assign the lifecycle hook
 * `default_result` - (Optional) Defines the action the Auto Scaling group should take when the lifecycle hook timeout elapses or if an unexpected failure occurs. The value for this parameter can be either CONTINUE or ABANDON. The default value for this parameter is ABANDON.
 * `heartbeat_timeout` - (Optional) Defines the amount of time, in seconds, that can elapse before the lifecycle hook times out. When the lifecycle hook times out, Auto Scaling performs the action defined in the DefaultResult parameter
 * `lifecycle_transition` - (Optional) The instance state to which you want to attach the lifecycle hook. For a list of lifecycle hook types, see [describe-lifecycle-hook-types](https://docs.aws.amazon.com/cli/latest/reference/autoscaling/describe-lifecycle-hook-types.html#examples)

website/source/docs/providers/aws/r/default_route_table.html.markdown

@@ -13,7 +13,7 @@ Provides a resource to manage a Default VPC Routing Table.
 Each VPC created in AWS comes with a Default Route Table that can be managed, but not
 destroyed. **This is an advanced resource**, and has special caveats to be aware
 of when using it. Please read this document in its entirety before using this
-resource. It is recommened you **do not** use both `aws_default_route_table` to
+resource. It is recommended you **do not** use both `aws_default_route_table` to
 manage the default route table **and** use the `aws_main_route_table_association`,
 due to possible conflict in routes.
 

website/source/docs/providers/aws/r/eip.html.markdown

@@ -21,7 +21,7 @@ resource "aws_eip" "lb" {
 }
 ```
 
-Muliple EIPs associated with a single network interface:
+Multiple EIPs associated with a single network interface:
 
 ```
 resource "aws_network_interface" "multi-ip" {

website/source/docs/providers/aws/r/lambda_function.html.markdown

@@ -58,7 +58,7 @@ resource "aws_lambda_function" "test_lambda" {
 * `timeout` - (Optional) The amount of time your Lambda Function has to run in seconds. Defaults to `3`. See [Limits][5]
 * `publish` - (Optional) Whether to publish creation/change as new Lambda Function Version. Defaults to `false`.
 * `vpc_config` - (Optional) Provide this to allow your function to access your VPC. Fields documented below. See [Lambda in VPC][7]
-* `source_code_hash` - (Optional) Used to trigger updates. This is only useful in conjuction with `filename`.
+* `source_code_hash` - (Optional) Used to trigger updates. This is only useful in conjunction with `filename`.
   The only useful value is `${base64sha256(file("file.zip"))}`.
 
 **vpc\_config** requires the following:

website/source/docs/providers/aws/r/load_balancer_policy.html.markdown

@@ -81,7 +81,7 @@ resource "aws_load_balancer_listener_policy" "wu-tang-listener-policies-443" {
 }
 ```
 
-Where the file `pubkey` in the current directoy contains only the _public key_ of the certificate.
+Where the file `pubkey` in the current directory contains only the _public key_ of the certificate.
 
 ```
 cat wu-tang-ca.pem | openssl x509 -pubkey -noout | grep -v '\-\-\-\-' | tr -d '\n' > wu-tang-pubkey

website/source/docs/providers/aws/r/opsworks_application.html.markdown

@@ -1,6 +1,6 @@
 ---
 layout: "aws"
-page_title: "AWS: aws_opsworks_aplication"
+page_title: "AWS: aws_opsworks_application"
 sidebar_current: "docs-aws-resource-opsworks-application"
 description: |-
   Provides an OpsWorks application resource.

website/source/docs/providers/aws/r/spot_fleet_request.html.markdown

@@ -70,7 +70,7 @@ resource "aws_spot_fleet_request" "foo" {
 ## Argument Reference
 
 Most of these arguments directly correspond to the
-[offical API](http://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_SpotFleetRequestConfigData.html).
+[official API](http://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_SpotFleetRequestConfigData.html).
 
 * `iam_fleet_role` - (Required) Grants the Spot fleet permission to terminate
   Spot instances on your behalf when you cancel its Spot fleet request using

website/source/docs/providers/aws/r/ssm_document.html.markdown

@@ -59,7 +59,7 @@ The following attributes are exported:
 * `status` - "Creating", "Active" or "Deleting". The current status of the document.
 * `parameter` - The parameters that are available to this document.
 * `permission` - The permissions of how this document should be shared.
-* `platform_type` - "Windows" or "Linux". A list of OS platforms compatiable with this SSM document.
+* `platform_type` - "Windows" or "Linux". A list of OS platforms compatible with this SSM document.
 
 ## Permissions
 

website/source/docs/providers/azurerm/r/virtual_machine.html.markdown

@@ -206,7 +206,7 @@ The following arguments are supported:
     create the virtual machine.
 * `location` - (Required) Specifies the supported Azure location where the resource exists. Changing this forces a new resource to be created.
 * `plan` - (Optional) A plan block as documented below.
-* `availability_set_id` - (Optional) The Id of the Availablity Set in which to create the virtual machine
+* `availability_set_id` - (Optional) The Id of the Availability Set in which to create the virtual machine
 * `vm_size` - (Required) Specifies the [size of the virtual machine](https://azure.microsoft.com/en-us/documentation/articles/virtual-machines-size-specs/).
 * `storage_image_reference` - (Optional) A Storage Image Reference block as documented below.
 * `storage_os_disk` - (Required) A Storage OS Disk block as referenced below.

website/source/docs/providers/clc/r/server.html.markdown

@@ -61,7 +61,7 @@ The following arguments are supported:
 * `memory_mb` - (Required, int) Provisioned RAM
 * `type` - (Required, string) The virtualization type
   One of "standard", "hyperscale", "bareMetal"
-* `password` - (Optional, string) The root/adminstrator password. Will be generated by platform if not provided. 
+* `password` - (Optional, string) The root/administrator password. Will be generated by platform if not provided. 
 * `description` - (Optional, string) Description for server (visible in control portal only)
 * `power_state` - (Optional, string) See [PowerStates](#power_states) below for details.
   If absent, defaults to `started`.

website/source/docs/providers/cobbler/r/system.html.markdown

@@ -162,7 +162,7 @@ The `interface` block supports:
 
 * `ipv6_address` - (Optional) The IPv6 address of the interface.
 
-* `ipv6_mtu` - (Optional) The MTU of the IPv6 adress.
+* `ipv6_mtu` - (Optional) The MTU of the IPv6 address.
 
 * `ipv6_static_routes` - (Optional) Static routes for the IPv6
   interface.

website/source/docs/providers/consul/r/keys.html.markdown

@@ -12,7 +12,7 @@ description: |-
 This is a powerful way to expose infrastructure details to clients.
 
 This resource manages individual keys, and thus it can create, update and
-delete the keys explicitly given. Howver, It is not able to detect and remove
+delete the keys explicitly given. However, It is not able to detect and remove
 additional keys that have been added by non-Terraform means. To manage
 *all* keys sharing a common prefix, and thus have Terraform remove errant keys
 not present in the configuration, consider using the `consul_key_prefix`
@@ -64,7 +64,7 @@ Prior to Terraform 0.7 this resource was used both to read *and* write the
 Consul key/value store. The read functionality has moved to the `consul_keys`
 *data source*, whose documentation can be found via the navigation.
 
-The pre-0.7 interface for reading is still supported for backward compatibilty,
+The pre-0.7 interface for reading is still supported for backward compatibility,
 but will be removed in a future version of Terraform.
 
 ## Attributes Reference

website/source/docs/providers/docker/r/image.html.markdown

@@ -13,7 +13,7 @@ description: |-
 Pulls a Docker image to a given Docker host from a Docker Registry.
 
 This resource will *not* pull new layers of the image automatically unless used in
-conjuction with [`docker_registry_image`](/docs/providers/docker/d/registry_image.html)
+conjunction with [`docker_registry_image`](/docs/providers/docker/d/registry_image.html)
 data source to update the `pull_trigger` field.
 
 ## Example Usage

website/source/docs/providers/fastly/r/service_v1.html.markdown

@@ -193,7 +193,7 @@ The `cache_setting` block supports:
 
 * `name` - (Required) A unique name to label this Cache Setting
 * `action` - (Required) One of `cache`, `pass`, or `restart`, as defined
-on Fastly's documenation under ["Caching action descriptions"](https://docs.fastly.com/guides/performance-tuning/controlling-caching#caching-action-descriptions)
+on Fastly's documentation under ["Caching action descriptions"](https://docs.fastly.com/guides/performance-tuning/controlling-caching#caching-action-descriptions)
 * `cache_condition` - (Required) Name of the condition used to test whether this settings object should be used.
 This Condition must be of type `CACHE`
 * `stale_ttl` - (Optional) Max "Time To Live" for stale (unreachable) objects.

website/source/docs/providers/librato/r/space_chart.html.markdown

@@ -96,7 +96,7 @@ The `stream` block supports:
 * `min` - (Optional) Theoretical minimum Y-axis value.
 * `max` - (Optional) Theoretical maximum Y-axis value.
 * `transform_function` - (Optional) Linear formula to run on each measurement
-  prior to visualizaton.
+  prior to visualization.
 * `period` - (Optional) An integer value of seconds that defines the period this
   stream reports at. This aids in the display of the stream and allows the
   period to be used in stream display transforms.

website/source/docs/providers/openstack/r/networking_secgroup_rule_v2.html.markdown

@@ -65,7 +65,7 @@ The following arguments are supported:
     Openstack ID of a security group in the same tenant. Changing this creates
     a new security group rule.
 
-* `security_group_id` - (Required) The security group id the rule shoudl belong
+* `security_group_id` - (Required) The security group id the rule should belong
     to, the value needs to be an Openstack ID of a security group in the same
     tenant. Changing this creates a new security group rule.
 

website/source/docs/providers/tls/d/cert_request.html.md

@@ -1,7 +1,7 @@
 ---
 layout: "tls"
 page_title: "TLS: tls_cert_request"
-sidebar_current: "docs-tls-resourse-cert-request"
+sidebar_current: "docs-tls-data-source-cert-request"
 description: |-
   Creates a PEM-encoded certificate request.
 ---

website/source/docs/providers/tls/r/locally_signed_cert.html.md

@@ -1,7 +1,7 @@
 ---
 layout: "tls"
 page_title: "TLS: tls_locally_signed_cert"
-sidebar_current: "docs-tls-resourse-locally-signed-cert"
+sidebar_current: "docs-tls-resource-locally-signed-cert"
 description: |-
   Creates a locally-signed TLS certificate in PEM format.
 ---

website/source/docs/providers/tls/r/private_key.html.md

@@ -1,7 +1,7 @@
 ---
 layout: "tls"
 page_title: "TLS: tls_private_key"
-sidebar_current: "docs-tls-resourse-private-key"
+sidebar_current: "docs-tls-resource-private-key"
 description: |-
   Creates a PEM-encoded private key.
 ---

website/source/docs/providers/tls/r/self_signed_cert.html.md

@@ -1,7 +1,7 @@
 ---
 layout: "tls"
 page_title: "TLS: tls_self_signed_cert"
-sidebar_current: "docs-tls-resourse-self-signed-cert"
+sidebar_current: "docs-tls-resource-self-signed-cert"
 description: |-
   Creates a self-signed TLS certificate in PEM format.
 ---

website/source/docs/providers/vsphere/r/file.html.markdown

@@ -3,7 +3,7 @@ layout: "vsphere"
 page_title: "VMware vSphere: vsphere_file"
 sidebar_current: "docs-vsphere-resource-file"
 description: |-
-  Provides a VMware vSphere virtual machine file resource. This can be used to upload files (e.g. vmdk disks) from the Terraform host machine to a remote vSphere or copy fields withing vSphere.
+  Provides a VMware vSphere virtual machine file resource. This can be used to upload files (e.g. vmdk disks) from the Terraform host machine to a remote vSphere or copy fields within vSphere.
 ---
 
 # vsphere\_file

website/source/layouts/tls.erb

@@ -22,13 +22,13 @@
 				<li<%= sidebar_current(/^docs-tls-resource/) %>>
 					<a href="#">Resources</a>
 					<ul class="nav nav-visible">
-						<li<%= sidebar_current("docs-tls-resourse-private-key") %>>
+						<li<%= sidebar_current("docs-tls-resource-private-key") %>>
 							<a href="/docs/providers/tls/r/private_key.html">tls_private_key</a>
 						</li>
-						<li<%= sidebar_current("docs-tls-resourse-self-signed-cert") %>>
+						<li<%= sidebar_current("docs-tls-resource-self-signed-cert") %>>
 							<a href="/docs/providers/tls/r/self_signed_cert.html">tls_self_signed_cert</a>
 						</li>
-						<li<%= sidebar_current("docs-tls-resourse-locally-signed-cert") %>>
+						<li<%= sidebar_current("docs-tls-resource-locally-signed-cert") %>>
 							<a href="/docs/providers/tls/r/locally_signed_cert.html">tls_locally_signed_cert</a>
 						</li>
 					</ul>

website/source/upgrade-guides/0-7.html.markdown

@@ -91,7 +91,7 @@ This allows double quote characters to be expressed properly within strings insi
 
 Prior to v0.7, the `terraform plan` command had the potential to write updates to the state if changes were detected during the Refresh step (which happens by default during `plan`). Some configurations have metadata that changes with every read, so Refresh would always result in changes to the state, and therefore a write.
 
-In collaborative enviroments with shared remote state, this potential side effect of `plan` would cause unnecessary contention over the state, and potentially even interfere with active `apply` operations if they were happening simultaneously elsewhere.
+In collaborative environments with shared remote state, this potential side effect of `plan` would cause unnecessary contention over the state, and potentially even interfere with active `apply` operations if they were happening simultaneously elsewhere.
 
 Terraform v0.7 addresses this by changing the Refresh process that is run during `terraform plan` to always be an in-memory only refresh. New state information detected during this step will not be persisted to permanent state storage.
 
@@ -189,10 +189,10 @@ variable "amis" {
 }
 ```
 
-The key "us-west-2" could be overridden using `-var "amis.us-west-2=overriden_value"` (or equivalent in an environment variable or `tfvars` file). The syntax for this has now changed - instead maps from the command line will be merged with the default value, with maps from flags taking precedence. The syntax for overriding individual values is now:
+The key "us-west-2" could be overridden using `-var "amis.us-west-2=overridden_value"` (or equivalent in an environment variable or `tfvars` file). The syntax for this has now changed - instead maps from the command line will be merged with the default value, with maps from flags taking precedence. The syntax for overriding individual values is now:
 
 ```
--var 'amis = { us-west-2 = "overriden_value" }'
+-var 'amis = { us-west-2 = "overridden_value" }'
 ```
 
 This will give the map the effective value:
@@ -200,7 +200,7 @@ This will give the map the effective value:
 ```
 {
   us-east-1 = "ami-123456"
-  us-west-2 = "overriden_value"
+  us-west-2 = "overridden_value"
   eu-west-1 = "ami-789123"
 }
 ```