Apply suggestions from code review

Co-authored-by: Esha Noronha <[email protected]>

Author: sofietoft

umbraco-cloud/getting-started/git-repository-in-a-cloud-project.md

@@ -33,7 +33,7 @@ You need to put your custom code in a different source control repository of you
 
 ## A source control repository with the locally cloned Umbraco project
 
-We recommend creating a Cloud project with at least two environments: a Live environment including one extra mainline environment. Work with a local copy of the site by cloning down the left-most environment. This repository is different from your source control repository.
+It is recommended to create a Cloud project with at least two environments: a Live environment including one extra mainline environment. Work with a local copy of the site by cloning down the left-most environment. This repository is different from your source control repository.
 
 Once you're happy with the results or wish to see how your website has progressed, you push the changes back to the Cloud. If everything is working as expected, deploy your changes to the Live environment.
 

umbraco-cloud/getting-started/migrate-to-umbraco-cloud.md

@@ -131,8 +131,8 @@ You can create a new Umbraco Cloud project in one of the two ways:
 Once the project is set up:
 
 1. Select **Configure environments**.
-2. Add an new **mainline environment**.
-    * Throughout this guide we will refer to this environment as the **Development environment**
+2. Add a new **mainline environment**.
+    * Throughout this guide, this mainline environment will be referred to as the **Development environment**.
 
 Having more than one environment on your project, will enable you to start over with the migration process should it be needed.
 

umbraco-cloud/getting-started/team-workflow-on-cloud.md

@@ -12,7 +12,7 @@ Umbraco Cloud is built on top of Git which means that you can create branches lo
 
 ## Working with Environments in a team
 
-It is recommend to use multiple environments when you are working in teams. With additional environments, members of a team can work locally pushing up changes to the Cloud environment for testing.
+It is recommended to use multiple environments when you are working in teams. With additional environments, members of a team can work locally, pushing up changes to the Cloud environment for testing.
 
 Having multiple environments enables developers to continue developing, while content editors can focus on creating content in a separate environment.
 
@@ -24,6 +24,6 @@ Learn more about how this works in the [Flexible Environments](flexible-environm
 
 ## Team development workflow On Cloud
 
-For a more in-depth example of how to work in teams, Our Gold Partner ProWorks have written an article on [Team development workflows](https://skrift.io/issues/integrating-umbraco-cloud-with-team-development-workflow/).
+For a more in-depth example of how to work in teams, our Gold Partner ProWorks has written an article on [Team development workflows](https://skrift.io/issues/integrating-umbraco-cloud-with-team-development-workflow/).
 
 This article serves as inspiration if you looking into setting up a bigger project where multiple people will be working on Umbraco Cloud.

umbraco-cloud/product-upgrades/major-upgrades.md

@@ -53,7 +53,7 @@ Look for the "**Upgrade from/to Umbraco xx"** boxes. These boxes contain importa
 * Follow the **requirements** for [local development](https://docs.umbraco.com/umbraco-cms/fundamentals/setup/requirements#local-development).
 * An Umbraco Cloud project running [the latest version of your current Umbraco CMS installation](https://our.umbraco.com/download/releases)
 * The **latest** .[NET version](https://dotnet.microsoft.com/en-us/download/visual-studio-sdks) is installed locally.
-* **At least 2two environments** on your Cloud project.
+* **At least two environments** on your Cloud project.
 * A backup of your project database.
   * Directly from your environment. See the [Database backups](../databases/backups.md) article,
   * Or clone down, restore the project, and back up the local database.

umbraco-cloud/product-upgrades/version-specific-upgrades/migrate-from-8-to-latest.md

@@ -24,7 +24,7 @@ You also need to make sure that the packages that you are using are available on
 * A clean Cloud project running the latest version of Umbraco with **at least two environments**.
 * A backup of your Umbraco 8 project database.
 
-We strongly recommend having at least **two environments** on the new Umbraco project.
+It is recommended to have at least **two environments** on the new Umbraco project.
 
 {% hint style="info" %}
 If your Umbraco 8 site is using Umbraco Forms, make sure to configure it to store data in the database, before beginning this tutorial [Follow the guide for migrating Umbraco Forms data to the database.](https://docs.umbraco.com/umbraco-forms/developer/forms-in-the-database)
@@ -122,7 +122,7 @@ Depending on the extent of the project and the amount of custom code and impleme
 
 ## Step 4: Deploy and Test on Umbraco Cloud
 
-Once the new Cloud project runs without errors on the local setup, the next step is to deploy and test on the Cloud **left-most** mainline environment.
+After the project runs locally without errors, deploy and test it on the Cloud's left-most mainline environment.
 
 1. Push the migration and changes to the Umbraco Cloud **left-most** mainline environment.
 

umbraco-cloud/set-up/config-transforms.md

@@ -60,7 +60,7 @@ Using the tool will let you test whether the transform file transforms your conf
 
 ## Examples
 
-Rewrite rules are often something you only want to apply to your Live environment. To avoid the rewrites being applied to other mainline environments, you can create a transform file to apply the rewrite rules to your Live environment only.
+Rewrite rules are often something you only want to apply to your Live environment. To avoid the rewrites being applied to other mainline environments, create a transform file to apply the rewrite rules only to the Live environment.
 
 Here is an example of how that config transform would look: