Update refs

Author: sofietoft

umbraco-cloud/product-upgrades/manual-upgrades/README.md

@@ -6,13 +6,13 @@ description: >-
 
 # Upgrade your projects manually
 
-In some cases, you might need to upgrade your Umbraco Cloud project manually. It's very similar to how you would upgrade any other Umbraco project but includes a few extra and **very important** steps.
+In some cases, you might need to upgrade your Umbraco Cloud project manually. It's similar to how you would upgrade any other Umbraco project but includes a few extra and **very important** steps.
 
 Umbraco Cloud project uses Umbraco Forms and Umbraco Deploy, which means there are also some dependencies you need to consider when upgrading your Umbraco Cloud project manually.
 
 ## Why and when would you do a manual upgrade?
 
-By default, all Umbraco Cloud projects are automatically upgraded when we release new patches (e.g. 8.8.**1**) to the Umbraco CMS as well as Umbraco Forms and Umbraco Deploy. When we release a new _minor_ version (e.g 8.**8**) the upgrade is applied to the Umbraco Cloud engine, and **not to the individual projects** - the same goes for the release of new _major_ versions (e.g. **10**.0). For these minor and major versions, there will be an option on your Umbraco Cloud Development environment to apply the upgrade. The Umbraco Cloud engine will take care of the entire process, and you only need to make sure everything works after the upgrade has been applied.
+By default, all Umbraco Cloud projects are automatically upgraded when we release new patches (e.g. 8.8.**1**) to the Umbraco CMS as well as Umbraco Forms and Umbraco Deploy. When we release a new _minor_ version (e.g 8.**8**) the upgrade is applied to the Umbraco Cloud engine, and **not to the individual projects** - the same goes for the release of new _major_ versions (e.g. **10**.0). For these minor and major versions, there will be an option on your left-most mainline environment to apply the upgrade. The Umbraco Cloud engine will take care of the entire process, and you only need to make sure everything works after the upgrade has been applied.
 
 We always recommend using the automatic and _semi-automatic_ upgrade options provided to you as part of your Umbraco Cloud project. With that said, it's also possible to upgrade your Umbraco Cloud project manually - this can be done with both patches and minor and major versions.
 

umbraco-cloud/product-upgrades/manual-upgrades/manual-cms-upgrade.md

@@ -14,7 +14,7 @@ This article will give you a step-by-step on how to manually upgrade your Umbrac
 
 ## Prepare for the upgrade
 
-* When upgrading a Umbraco Cloud project manually, the very first step is to either [clone down your Cloud Development environment to your local machine](../../set-up/working-locally.md) or pull down the latest changes for your development environment.
+* When upgrading a Umbraco Cloud project manually, the very first step is to either [clone down left-most mainline environment to your local machine](../../set-up/working-locally.md) or pull down the latest changes for your left-most mainline environment.
 * Navigate to the `/src/UmbracoProject/` folder to find the `.csproj` file.
 * Make sure you can run your Cloud project locally and restore content and media. It's important that you check that everything works once the upgrade has been applied and for this, you need to have a clone locally that resembles the Cloud environment as much as possible.
 
@@ -203,7 +203,7 @@ When you've upgraded everything locally, and made sure that everything runs with
 * Stage and commit all changes in Git
 * Push the changes to the Cloud environment
 * When everything is pushed, head on over to the Umbraco Cloud Portal
-* Access the backoffice of the Cloud environment you pushed the upgrade to - Development or Live
+* Access the backoffice of the Cloud environment you pushed the upgrade
 * You will again be prompted to log in to complete the database upgrade
 * You will be sent to the backoffice once the upgrade is complete
 

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

@@ -21,15 +21,15 @@ You also need to make sure that the packages that you are using are available on
 ## Prerequisites
 
 * A Umbraco 8 Cloud project running **the latest version of Umbraco 8**.
-* A clean Cloud project running the latest version of Umbraco with **at least 2 environments**.
+* 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 **2 environments** on the new Umbraco project.
+We strongly recommend having 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)
 
-Should something fail during the migration, the Development environment can be removed and re-added to start over on a clean slate.
+Should something fail during the migration, the left-most environment can be removed and re-added to start over on a clean slate.
 {% endhint %}
 
 ## Video Tutorial
@@ -47,7 +47,7 @@ If you use Umbraco Forms, make sure to have [`StoreUmbracoFormsInDbset`](https:/
 1. Create a backup of the database from your Umbraco 8 project using the [database backup guide](../../databases/backups.md).
    * Alternatively, you can clone the environment down and take a backup of the local Database after restoring. Make sure to restore both content and media from your Cloud environment after cloning it down.
 2. Import the database backup into SQL Server Management Studio.
-3. Clone down the **Development** environment from the **new** Cloud project.
+3. Clone down the **left-most** mainline environment from the **new** Cloud project.
 4. Test the project and make sure to log in to the backoffice.
 
 {% hint style="info" %}
@@ -122,31 +122,31 @@ 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 **Development** environment.
+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.
 
-1. Push the migration and changes to the Umbraco Cloud **Development** environment.
+1. Push the migration and changes to the Umbraco Cloud **left-most** mainline environment.
 
 {% hint style="info" %}
 The deployment might take a bit longer than normal as a lot of changes have been made.
 {% endhint %}
 
-2. Go to the backoffice of the **Development** environment once everything has been pushed.
+2. Go to the backoffice of the **left-most** mainline environment once everything has been pushed.
 3. Go to **Settings** and open the **Deploy** Dashboard.
 4. Click on `Export Schema to Data Files` in the **Deploy Operations** section.
    * The deployment will result in either of the two:
      * `Last deployment operation failed` - something failed during the check.
        * Select `Clear Signatures` from the **Deploy Operations** section.
        * Select `Update Umbraco Schema` from the **Deploy Operations** section to clear up the error.
      * `Last deployment operation completed`
-       * Everything checks out: The Development environment has been upgraded.
-5. Transfer Content and Media from the local clone to the **Development** environment.
+       * Everything checks out: The left-most environment has been upgraded.
+5. Transfer Content and Media from the local clone to the **left-most** mainline environment.
    * To transfer members make sure that the following Deploy settings are configured in the `appsettings.json`: [`AllowMembersDeploymentOperations` and `TransferMemberGroupsAsContent`](https://docs.umbraco.com/umbraco-deploy/deploy-settings#allowmembersdeploymentoperations-and-transfermembergroupsascontent).
-6. Test **everything** in the **Development** environment.
+6. Test **everything** in the **left-most** mainline environment.
 7. Deploy to the **Live** environment.
 
 ## Step 5: Going live
 
-1. Test **everything** in the **Development** environment until it runs without any errors.
+1. Test **everything** in the **left-most** mainline environment until it runs without any errors.
 2. Setup rewrites on the new Cloud project if relevant.
 3. Assign hostnames to the project if relevant.
 

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

@@ -26,15 +26,15 @@ If you want to do a transform on your `Web.config` file for the Live environment
 
 `Web.Production.config`
 
-The `{environment}` part needs to be replaced with the target environment, for which there are currently 3 possibilities for each project:
+The `{environment}` part needs to be replaced with the target environment, for which there are currently three possibilities for each project:
 
 1. `Production`
 2. `Staging`
 3. `Development`
 
 This file needs to be created on a local clone of your project, as this will ensure that the file is added to the project repository.
 
-When the file is deployed to the Live environment, the transforms will be applied to the `Web.config` file in the `Root` of your project. In the case that you also have a Development and/or Staging environment, the `Web.Production.config` will **only** transform the `Web.config` on the Live environment.
+When the file is deployed to the Live environment, the transforms will be applied to the `Web.config` file in the `Root` of your project. In the case that you have mutliple mainline environments, the `Web.Production.config` will **only** transform the `Web.config` on the Live environment.
 
 For each deployment, the Umbraco Cloud engine searches for all of the `.{environment}.config` files in your site and apply the transforms.
 
@@ -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 your Development and/or Staging 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, you can create a transform file to apply the rewrite rules to your Live environment only.
 
 Here is an example of how that config transform would look: