Update first-time-setup.md

guides/v2.1/cloud/access-acct/first-time-setup.md

@@ -22,7 +22,7 @@ functional_areas:
 All environments for your project are read-only, requiring all work to be completed on your local environment and pushed to cloud environments. To start developing Magento, you need a configured local developer workspace, cloned {{site.data.var.ece}} code from your Git branch, and knowledge of the deployment workflow. These instructions guide through the entire process to create a development workspace on your local system.
 
 ## Project user account {#account}
-Depending on the [Project Owner]({{ page.baseurl }}/cloud/onboarding/onboarding-tasks.html), you may need to be invited by the owner to the project. This account gives you participation to the project and connects your local, credentials, and access to your company's {{site.data.var.ece}} account. The account includes all source code and deployment environments.
+Depending on the [Project Owner]({{ page.baseurl }}/cloud/onboarding/onboarding-tasks.html), you may need to be invited by the owner to the project. This account gives you participation in the project and connects your local, credentials, and access to your company's {{site.data.var.ece}} account. The account includes all source code and deployment environments.
 
 After you receive an invitation, you can complete tasks to create your local, pull code, and deploy your store.
 
@@ -31,7 +31,7 @@ We highly recommend having experience with the following technologies and method
 
 * Magento [technology stack]({{ page.baseurl }}/architecture/tech-stack.html)
 * [Git](https://git-scm.com/){:target="\_blank"} for repository and code management, [branching methodologies](https://git-scm.com/book/en/v2/Git-Branching-Branching-Workflows){:target="\_blank"}, and working with Magento Git code
-* [GitHub](https://github.com/){:target="\_blank"} for managing your code and accessing Magento repos
+* [GitHub](https://github.com/){:target="\_blank"} for managing your code and accessing Magento repositories
 * [Fastly](https://www.fastly.com/){:target="\_blank"} for CDN and caching, used in Staging and Production
 * [Galera Cluster](http://galeracluster.com/){:target="\_blank"} for databases, used in Staging and Production (with triple redundancy failover in Production)
 
@@ -43,7 +43,7 @@ Prior to setting up your workspace, you may want to gather the following credent
 * **Magento Encryption Key**: When importing an existing Magento system only, you will need to capture the Magento encryption key used to protect your access and data for the Magento database. For details on this key, see [Resolve issues with encryption key]({{ page.baseurl }}/cloud/trouble/trouble-crypt-key-variable.html)
 
 ## Create a local environment {#local}
-For development, you need to install and configure a local environment. All environments for {{site.data.var.ece}} are read-only, including all Starter environments and all Pro Integration, Staging, and Production environments. Working in a local environment, you can write and test code prior to pushing it to a Integration environment for further testing and deployment to Staging and Production.
+For development, you need to install and configure a local environment. All environments for {{site.data.var.ece}} are read-only, including all Starter environments and all Pro Integration, Staging, and Production environments. Working in a local environment, you can write and test code prior to pushing it to an Integration environment for further testing and deployment to Staging and Production.
 
 We recommend adding a virtual machine (VM) or Docker container and installing {{site.data.var.ee}}. The environment should closely match cloud environments. To develop Magento code, you will clone the project Git code and create branches to develop your sites and stores in this local environment.
 

guides/v2.1/cloud/project/project-webint-branch.md

@@ -135,7 +135,7 @@ If you do not see your Pro plan Staging and Production environments in the Proje
 4.	To view the build log, select the Success or Failure link per deployment record on the account.
 
 ## Pull code from a private Git repository {#private}
-Your {{site.data.var.ece}} project can include code located in a private Git repository. For example, a you may have code for a custom module or theme in a private repo. To do so, you must add your project's public SSH key to your private Git repository and update your project's `composer.json`.
+Your {{site.data.var.ece}} project can include code located in a private Git repository. For example, you may have code for a custom module or theme in a private repo. To do so, you must add your project's public SSH key to your private Git repository and update your project's `composer.json`.
 
 To add a deployment key to your private GitHub repository, you must be the administrator of that repository. GitHub allows you to use a deploy key for one repository only.