Merge pull request #330 from gruntwork-io/chore/fix-grammar-errors

Fixes spelling and grammar errors throughout the repo [WWW-89]

Author: oredavids

_data/devops-checklist.yml

@@ -28,7 +28,7 @@
         You have several options for running Docker containers in AWS. One is to use the
         <a href="https://aws.amazon.com/ecs/" target="_blank">Elastic Container Service (ECS)</a>, where you run a
         cluster of EC2 Instances, and Amazon takes care of scheduling containers across them. Another is
-        <a href="https://aws.amazon.com/eks/" target="_blank">Elasic Kubernetes Service (EKS)</a>, which is a Amazon's
+        <a href="https://aws.amazon.com/eks/" target="_blank">Elastic Kubernetes Service (EKS)</a>, which is a Amazon's
         managed <a href="https://kubernetes.io/" target="_blank">Kubernetes</a> (note, EKS is still in preview mode
         as of May, 2018). A third option is <a href="https://aws.amazon.com/fargate/" target="_blank">AWS Fargate</a>,
         a service where AWS manages and scales the underlying EC2 Instances for you and you just hand it Docker
@@ -112,7 +112,7 @@
       description: |
         Use <a href="https://aws.amazon.com/cloudfront/" target="_blank">CloudFront</a> as a
         <a href="https://en.wikipedia.org/wiki/Content_delivery_network" target="_blank">Content Distribution Network (CDN)</a>
-        to cache and distribute your content across servers all over the world. This signicantly reduces latency for
+        to cache and distribute your content across servers all over the world. This significantly reduces latency for
         users and is especially effective for static content.
 
     - title: Configure caching
@@ -540,7 +540,7 @@
     - title: Set up SSH access
       description: |
         Do NOT share <a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html" target="_blank">EC2 KeyPairs</a>
-        with your team! Otherwise, everyone will be using the same username and key for server acesss (so there's no
+        with your team! Otherwise, everyone will be using the same username and key for server access (so there's no
         audit trail), the key may easily be compromised, and if it is, or someone leaves the company, you'll have to
         redeploy ALL your EC2 Instances to change the KeyPair. Instead, configure your EC2 Instances so that each
         developer can use their own username and SSH key, and if that developer leaves the company, the key can be
@@ -560,7 +560,7 @@
 
     - title: Deploy a VPN Server
       description: |
-        We typically recommend running a VPN Server as the entrypoint to your network (as the Bastion Host).
+        We typically recommend running a VPN Server as the entry point to your network (as the Bastion Host).
         <a href="https://openvpn.net/" target="_blank">OpenVPN</a> is the most popular option for running a VPN server.
 
     - title: Set up a secrets management solution
@@ -723,7 +723,7 @@
       description: |
         <a href="https://aws.amazon.com/ec2/spot/" target="_blank">EC2 Spot Instances</a> allow you to "bid" a much
         lower price for EC2 Instances than what you'd pay on-demand (as much as 90% lower!), and when there is capacity
-        to fulfill your request, AWS will give you the EC2 Instances at that price. Note that if AWS needs to relcaim
+        to fulfill your request, AWS will give you the EC2 Instances at that price. Note that if AWS needs to reclaim
         that capacity, it may terminate the EC2 Instance at any time with a 2-minute notice. This makes Spot Instances
         a great way to save money on any workload that is non-urgent (e.g., all background jobs, machine learning, image
         processing) and pre-production environments (e.g., run an ECS cluster on spot instances by just setting a

_data/library.yml

@@ -413,7 +413,7 @@
       description: An AWS Lambda function that can automatically share an RDS snapshot with another AWS account. Useful for storing your RDS backups in a separate backup account.
     - name: lambda-copy-shared-snapshot
       blurb: copy RDS snapshots
-      description: An AWS Lambda function that can make a local copy of an RDS snapshot shared from another AWS account. Useful for storing yoru RDS backups in a separate backup account.
+      description: An AWS Lambda function that can make a local copy of an RDS snapshot shared from another AWS account. Useful for storing your RDS backups in a separate backup account.
     - name: lambda-cleanup-snapshots
       blurb: delete RDS snapshots
       description: An AWS Lambda function that runs on a scheduled basis to clean up old RDS database snapshots. Useful to ensure you aren't spending lots of money storing old snapshots you no longer need.

_data/privacy-policy.yml

@@ -206,10 +206,10 @@
           <li>Inferences, including information about your interests and preferences. </li>
           <li>Internet activity, including your interactions with the Services and what led you to Gruntwork. </li>
         </ul>
-        <p><u>The Purposes for Our Collection:</u> We collect and use these categories of personal data for our business and commercial purposes described in the “How do we use your information” section above, including providing and improving the Services, maintaining the safety and security of the Services, and for advertising and marketing our business. </p>
+        <p><u>The Purposes for Our Collection:</u> We collect and use these categories of personal data for our business and commercial purposes described in the “How do we use your information” section above, including providing and improving the Services, maintaining the safety and security of the Services, and for advertising and marketing our business.</p>
         <p><u>Third-Party Marketing and Your Rights (Opt-Out of “Sale”):</u> Gruntwork does not sell personal data to third parties for monetary value. However, the term “sale” is defined broadly in the CCPA. To the extent that “sale” under the CCPA is interpreted to include interest-based advertising or other data uses described in the “How do we use your information” section above, we will comply with applicable law with respect to those uses.</p>
         <p><u>“Do Not Track” Signals:</u> We do not recognize or respond to any web browser-initiated “Do Not Track” signals. At present, no universally accepted standard exists on how companies should respond to “Do Not Track” signals. In the event a universally accepted standard is established, we will assess and provide an appropriate response to these signals. If you wish, you can configure most browsers to reject cookies or to notify you when you are sent a cookie, giving you a chance to decide whether or not to accept it. Consult the help section of your browser to learn more about how to do this. Please note that if you choose to remove or reject cookies, this could affect the availability and functionality of the Services. </p>
-        <p><u>Shine The Light:</u> California Civil Code §1798.83 permits users of the Website who are California residents to request certain information regarding our disclosure of personal data to third parties for their direct marketing purposes. Gruntwork does not share personal data with third parties for their direct marketing purposes.         </p>
+        <p><u>Shine The Light:</u> California Civil Code §1798.83 permits users of the Website who are California residents to request certain information regarding our disclosure of personal data to third parties for their direct marketing purposes. Gruntwork does not share personal data with third parties for their direct marketing purposes.</p>
 
 - question: Changes to our Privacy Policy
   items:

_data/reference-architecture.yml

@@ -33,7 +33,7 @@ infrastructure:
 
   - title: Bastion host
     description: |
-      Choose from either a plain bastion host or an OpenVPN server as the sole entrypoint to your network.
+      Choose from either a plain bastion host or an OpenVPN server as the sole entry point to your network.
 
   - title: CI server
     description: |

_data/terms-of-service.yml

@@ -16,7 +16,7 @@
   items:
     - title: 1. Updates to these Terms
       legalese: |
-        <p><strong>1.1. Revisions.</strong> We may revise these Terms or any additional terms and conditions which are relevant to a particular Service from time-to-time. We will post the revised terms to our website (currently <a rel="internal" rel="internal" href="/terms/" title="Grountwork Terms of Service">https://gruntwork.io/terms</a>) (the “Website”) with a “last updated” date, and we will attempt to notify you of any material updates to these Terms via email or through the Services. IF YOU CONTINUE TO USE THE SERVICES AFTER THE REVISIONS TAKE EFFECT, YOU AGREE TO BE BOUND BY THE REVISED TERMS. You agree that we shall not be liable to you or to any third party for any modification of the Terms.</p>
+        <p><strong>1.1. Revisions.</strong> We may revise these Terms or any additional terms and conditions which are relevant to a particular Service from time-to-time. We will post the revised terms to our website (currently <a rel="internal" rel="internal" href="/terms/" title="Gruntwork Terms of Service">https://gruntwork.io/terms</a>) (the “Website”) with a “last updated” date, and we will attempt to notify you of any material updates to these Terms via email or through the Services. IF YOU CONTINUE TO USE THE SERVICES AFTER THE REVISIONS TAKE EFFECT, YOU AGREE TO BE BOUND BY THE REVISED TERMS. You agree that we shall not be liable to you or to any third party for any modification of the Terms.</p>
         <p><strong>1.2. Notifying You of Updates.</strong> You agree to receive electronically all communications, agreements, and notices that we provide in connection with any Services (“Communications”), including by email, by posting them to our website, or through any Services. You agree that all Communications that we provide to you electronically satisfy any legal requirement that such Communications be in writing and you agree to keep your Account contact information current.</p>
       plain: |
         We might update these Terms of Service at some point, and if we do, we'll proactively notify you about it.

_data/where-we-work.yml

@@ -8,8 +8,6 @@
   position: [26%, 6%]
 - location: London, England
   position: [18%, 43%]
-- location: Lagos, Nigeria
-  position: [51%, 45%]
 - location: Orlando, FL
   position: [35%, 18%]
 - location: New York, NY
@@ -18,9 +16,13 @@
   position: [25%, 22%]
 - location: Woodbury, CT
   position: [25%, 21%]
-- location: Woodbury, CT
-  position: [25%, 21%]
-- location: Helsinki, Finland
-  position: [13%, 50.5%]
 - location: Berlin, Germany
   position: [20%, 48%]
+- location: Calgary, Canada
+  position: [19%, 12%]
+- location: Chicago, Illinois
+  position: [23%, 17%]
+- location: San Francisco, CA
+  position: [25%, 6%]
+- location: Portland, OR
+  position: [21%, 9%]

_posts/2019-05-08-deploying-a-dockerized-app-on-gcp-gke.adoc

@@ -90,7 +90,7 @@ using the Gruntwork Infrastructure as Code Library.
 [[pre_requisites]]
 === Pre-requisites
 
-This walkthrough has the following pre-requistes:
+This walkthrough has the following pre-requisites:
 
 Terraform::
   This guide uses https://www.terraform.io/[Terraform] to define and manage all the infrastructure as code. If you're

_posts/2019-08-12-how-to-configure-production-grade-aws-account-structure.adoc

@@ -683,7 +683,7 @@ and automated users in your child accounts. The exact set of IAM roles you need
 requirements, but here are some common ones:
 
 allow-auto-deploy-access-from-other-accounts::
-  This is an IAM role that grants permissions for automatically deploying (e.g., as part of a CI / CD pipline)
+  This is an IAM role that grants permissions for automatically deploying (e.g., as part of a CI / CD pipeline)
   some specific service. For example, this role may have a trust policy that allows it to be assumed by a Jenkins
   server in the shared-services account, and gives that server permissions to deploy EC2 Instances and Auto Scaling
   Groups. Note that anyone who has to your CI server (e.g., anyone who can create/modify/execute Jenkins jobs) can
@@ -886,7 +886,7 @@ the central place where you manage billing. You create this initial account manu
 === Apply the security baseline to the root account
 
 Next, we'll apply a security baseline to the root account that is responsible for configuring AWS Organizations, IAM Roles, IAM Users,
-IAM Groups, IAM Password Policies, Amazon GuardyDuty, AWS CloudTrail and AWS Config including setting up the child accounts.
+IAM Groups, IAM Password Policies, Amazon GuardDuty, AWS CloudTrail and AWS Config including setting up the child accounts.
 
 Let's first apply the security baseline by using the `account-baseline-root` module from https://github.com/gruntwork-io/module-security[module-security].
 
@@ -1000,7 +1000,7 @@ variable "child_accounts" {
   #   Defaults to the Organization default Root ID.
   #
   # - role_name:
-  #   The name of an IAM role that Organizations automatically preconfigures in the new member account. This role trusts
+  #   The name of an IAM role that Organizations automatically pre-configures in the new member account. This role trusts
   #   the master account, allowing users in the master account to assume the role, as permitted by the master account
   #   administrator. The role has administrator permissions in the new member account. Note that the Organizations API
   #   provides no method for reading this information after account creation.

_posts/2019-08-13-how-to-deploy-production-grade-vpc-aws.adoc

@@ -610,7 +610,7 @@ Infrastructure as Code Library.
 [[pre_requisites]]
 === Pre-requisites
 
-This walkthrough has the following pre-requistes:
+This walkthrough has the following pre-requisites:
 
 Gruntwork Infrastructure as Code Library::
   This guide uses code from the https://gruntwork.io/infrastructure-as-code-library/[Gruntwork Infrastructure as Code Library], as it

_posts/2019-08-26-how-to-use-gruntwork-infrastructure-as-code-library.adoc

@@ -278,7 +278,7 @@ _The Production-Grade Infrastructure Checklist_:
 | Bash, Chef, Ansible, Puppet
 
 | Provision
-|  Provision the infrastructure. Includes EC2 instances, load balancers, network topology, security gr oups, IAM permissions, etc.
+|  Provision the infrastructure. Includes EC2 instances, load balancers, network topology, security groups, IAM permissions, etc.
 | Terraform, CloudFormation
 
 | Deploy
@@ -1049,7 +1049,7 @@ Configure variables::
   This is similar to the `testing/terraform.tfvars` used in manual testing.
 
 Configure the backend::
-  This is similar to tthe `testing-backend.hcl` used in manual testing.
+  This is similar to the `testing-backend.hcl` used in manual testing.
 
 Namespace resources::
   The code uses `random.UniqueId()` to generate unique identifiers for all the resources in this test. This allows
@@ -1426,7 +1426,7 @@ Use TFC without Terragrunt::
 
 Use TFC with Terragrunt::
   Alternatively, you can use both `infrastructure-modules` and `infrastructure-live` repositories as described above,
-  storing the wrapper modules in `infrastructure-modules`, and using `infastructure-live` and Terragrunt for
+  storing the wrapper modules in `infrastructure-modules`, and using `infrastructure-live` and Terragrunt for
   deployments. In this approach, TFC is used as a https://www.terraform.io/docs/backends/types/remote.html[remote backend]
   for Terraform. You use Terragrunt to run deployments from the CLI, which in turn invokes Terraform on the TFC backend.
   The TFC UI is used for audit and tracking capabilities, but not for executing Terraform runs.
@@ -1708,9 +1708,9 @@ There are a few ways to set these credentials:
 
 . Create all the workspaces manually in advance, and set the `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` in each workspace, as described in  <<configure_credentials_and_variables>>.
 . Create all the workspaces manually by running `terragrunt init`, and still set up the environment variables as previously mentioned.
-. To set this up programatically, you can use the https://www.terraform.io/docs/providers/tfe/r/workspace.html[`tfe_workspace`] and https://www.terraform.io/docs/providers/tfe/r/variable.html[`tfe_variable`] resources to configure the workspaces with Terraform.
+. To set this up programmatically, you can use the https://www.terraform.io/docs/providers/tfe/r/workspace.html[`tfe_workspace`] and https://www.terraform.io/docs/providers/tfe/r/variable.html[`tfe_variable`] resources to configure the workspaces with Terraform.
 
-In all cases, you'll need to ensure that your workspaces stay in sync with your Terragrunt configuration. Each time you add a new module in Terragrunt, you'll need a corresponding workpace. Furthermore, if you rotate your AWS API keys, you'll need to update them within each workspace. For that reason, the final option above is recommended.
+In all cases, you'll need to ensure that your workspaces stay in sync with your Terragrunt configuration. Each time you add a new module in Terragrunt, you'll need a corresponding workspace. Furthermore, if you rotate your AWS API keys, you'll need to update them within each workspace. For that reason, the final option above is recommended.
 
 ===== Setting variables