Fix spelling mistakes/typos in documentation

docs/architecture.md

@@ -32,7 +32,7 @@ The full flow illustrated above does not actually apply to _all_ commands,
 but it applies to the main Terraform workflow commands `terraform plan` and
 `terraform apply`, along with a few others.
 
-For these commands, the role of the command implemtation is to read and parse
+For these commands, the role of the command implementation is to read and parse
 any command line arguments, command line options, and environment variables
 that are needed for the given command and use them to produce a
 [`backend.Operation`](https://godoc.org/github.com/hashicorp/terraform/backend#Operation)

docs/maintainer-etiquette.md

@@ -28,11 +28,11 @@ These apply to all contributors, but maintainers should lead by examples! :wink:
 
  - you're free to review PRs from the community or other HC employees and give :+1: / :-1:
  - if the PR submitter has push privileges (recognizable via `Collaborator`, `Member` or `Owner` badge) - we expect **the submitter** to merge their own PR after receiving a positive review from either HC employee or another maintainer. _Exceptions apply - see below._
- - we prefer to use the Github's interface or API to do this, just click the green button
+ - we prefer to use the GitHub's interface or API to do this, just click the green button
  - squash?
    - squash when you think the commit history is irrelevant (will not be helpful for any readers in T+6months)
  - Add the new PR to the **Changelog** if it may affect the user (almost any PR except test changes and docs updates)
-   - we prefer to use the Github's web interface to modify the Changelog and use `[GH-12345]` to format the PR number. These will be turned into links as part of the release process. Breaking changes should be always documented separately.
+   - we prefer to use the GitHub's web interface to modify the Changelog and use `[GH-12345]` to format the PR number. These will be turned into links as part of the release process. Breaking changes should be always documented separately.
 
 ## Release process
 

docs/resource-instance-change-lifecycle.md

@@ -134,7 +134,7 @@ operation, it should determine final values for any attributes that were left
 unknown in the planned new state, thus producing a wholly-known _new state_
 object.
 
-`ApplyResourceChange` also recieves the prior state so that it can use it
+`ApplyResourceChange` also receives the prior state so that it can use it
 to potentially implement more "surgical" changes to particular parts of
 the remote objects by detecting portions that are unchanged, in cases where the
 remote API supports partial-update operations.

website/docs/configuration/modules.html.md

@@ -420,7 +420,7 @@ Only [proxy configuration blocks](#proxy-configuration-blocks) are allowed.
 
 If a module contains proxy configuration blocks, the calling module block must be have the
 corresponding providers passed to the `providers` argument. If you attempt to use `count` or
-`for_each` with a module that does not satify this requirement, you will see an error:
+`for_each` with a module that does not satisfy this requirement, you will see an error:
 
 ```
 Error: Module does not support count