Clean up cloud articles

Author: eshanrnh

umbraco-cloud/go-live/manage-hostnames/README.md

@@ -74,9 +74,11 @@ The following Records will become obsolete in the future. Refrain from using the
 </details>
 
 {% hint style="info" %}
-Once you have updated your DNS records, you must remove the hostname and re-add it from Umbraco Cloud to re-validate the certificate with Cloudflare.
+
+Once you have updated your DNS records, remove the hostname and re-add it from Umbraco Cloud to re-validate the certificate with Cloudflare.
 
 You can also check the DNS propagation using a site like [What is my DNS?](https://www.whatsmydns.net/).
+
 {% endhint %}
 
 Check with your DNS host or hostname registrar regarding configuration details for your Hostnames.
@@ -124,9 +126,9 @@ When adding a hostname to your project hosted on Umbraco Cloud, using your own C
 
 The above is primarily relevant when you need to use specific Cloudflare services like Page Rules, Workers, and so on.
 
-### Using Certificate Authority Authorization (CAA) for your domain?
+### Using Certification Authority Authorization (CAA) for your domain?
 
-CAA is a [DNS resource record ](https://tools.ietf.org/html/rfc6844)defined in RFC 6844 allowing domain owners to indicate which Certificate Authorities (CA) allow to issue certificates for them. If you use CAA records on your domain, you will either need to remove CAA entirely or add the following through your DNS provider:
+CAA is a [DNS resource record](https://tools.ietf.org/html/rfc6844) defined in Resource Record (RFC) 6844. It allows domain owners to specify which Certification Authorities (CAs) can issue certificates for their domains. If you use CAA records on your domain, you will either need to remove CAA entirely or add the following through your DNS provider:
 
 ```sql
 example.com. IN CAA 0 issue "pki.goog"

umbraco-cloud/go-live/manage-hostnames/ca-record-migration.md

@@ -1,6 +1,6 @@
-# Migrate to new Certificate Authority for custom hostnames
+# Migrate to new Certification Authority Authorization (CAA) for custom hostnames
 
-The following changes in Certificate Authority (CA) used to issue certificates for all Umbraco Cloud sites' for new and existing custom hostnames.
+The following changes in CAA used to issue certificates for all Umbraco Cloud sites' for new and existing custom hostnames.
 
 {% hint style="info" %}
 **Not sure if your Cloud project is using a CAA record or not?**
@@ -10,7 +10,7 @@ You can use this [CAA Test](https://caatest.co.uk/) to check whether a CAA recor
 
 ## Certificates for new custom hostnames
 
-From September 26, 2022, certificates are issued using  'Google Trust Services' instead of 'DigiCert', and Certificate validity will be decreased from 1 year to 90 days.
+Starting September 26, 2022, certificates are issued by **Google Trust Services** instead of **DigiCert**. The validity period of certificates has been reduced from one year to 90 days.
 
 ## Certificates for existing custom hostnames
 

umbraco-cloud/go-live/manage-hostnames/rewrites-on-cloud.md

@@ -26,11 +26,11 @@ When setting up rewrite rules on Umbraco Cloud, there are a few important things
 * To continue working locally with your Umbraco Cloud project, you should also add a condition to exclude `localhost`.
 * To serve verification files from the `.well-known` directory (for example, Apple Pay or Google), follow the [Rewrite rule workaround in the CMS documentation](https://docs.umbraco.com/umbraco-cms/reference/routing/iisrewriterules#example-serving-files-from-the-well-known-path).
 
-## Hiding the default umbraco.io URL
+## Hiding the default `umbraco.io` URL
 
-Once you've assigned a hostname to your Live environment, you may want to "hide" the project's default URL (e.g. example.euwest01.umbraco.io) for different reasons. Perhaps for SEO or to make it clear to your users that the site can be accessed using only the primary hostname.
+After assigning a hostname to your live environment, you may want to hide the project's default URL (for example, example.euwest01.umbraco.io). This could be for improving Search Engine Optimization (SEO) or to communicate to your users that the site is accessible only through the primary hostname.
 
-One approach for this is to add a new rewrite rule to the `<system.webServer><rewrite><rules>` section in the `web.config` file. For example, the following rule will redirect all requests for the project example.euwest01.umbraco.io URL to the example.com URL (using HTTPS and including the `www.` prefix) and respond with a permanent redirect status.
+One approach for this is to add a new rewrite rule to the `<system.webServer><rewrite><rules>` section in the `web.config` file. For example, the following rule will redirect all requests for the project `example.euwest01.umbraco.io` to `example.com`. It will use HTTPS and include the `www.` prefix, responding with a permanent redirect status.
 
 ```xml
 <rule name="Redirect umbraco.io to primary hostname" stopProcessing="true">
@@ -49,12 +49,12 @@ One approach for this is to add a new rewrite rule to the `<system.webServer><re
 ```
 
 {% hint style="info" %}
-This will not rewrite anything under the `/umbraco` path so that you can still do content deployments. You don't have to give your editors the umbraco.io URL, and they won't see the umbraco.io URL if you give them the actual hostname. This rule will also not apply to your local copy of the site running on `localhost`.
+This will not rewrite anything under the `/umbraco` path so that you can still do content deployments. You don't have to give your editors the `umbraco.io` URL, and they won't see it if you give them the actual hostname. This rule will also not apply to your local copy of the site running on `localhost`.
 {% endhint %}
 
 ## Running your site on HTTPS only
 
-Once you've applied a certificate to your site, you can make sure that anybody visiting your site will always end up on HTTPS instead of the insecure HTTP.
+Once you've applied a certificate to your site, anybody visiting your site will always end up on HTTPS instead of the insecure HTTP.
 
 To accomplish this, add a rewrite rule to the live environment's `web.config` in the `<system.webServer><rewrite><rules>` section.
 
@@ -104,7 +104,7 @@ For example, the following rule will redirect all requests for `https://example.
 {% hint style="info" %}
 Take note of the negates in the rewrite rule.
 
-It is important to negate the path to files on your site because with the trailing slash added, your media will not show correctly after [your site has been migrated to use Azure Blob Storage](../../build-and-customize-your-solution/handle-deployments-and-environments/media/).
+It is important to negate the file paths on your site. If a trailing slash is added, your media may not display correctly after [migrating to Azure Blob Storage](../../build-and-customize-your-solution/handle-deployments-and-environments/media/).
 {% endhint %}
 
 ## Redirect from non-www to www

umbraco-cloud/optimize-and-maintain-your-site/manage-product-upgrades/product-upgrades/README.md

@@ -25,7 +25,7 @@ When minor upgrades are available, you will need an additional mainline environm
 
 {% hint style="info" %}
 
-Your project will not be auto-upgraded if your environments aren't running the same **minor version**. For example, when trying to upgrade a project to a new minor version where one environment is running 10.6.x and another is running 10.7.x.
+Your project will not be auto-upgraded if your environments aren't running the same **minor version**. For example, when upgrading a project to a new minor version, one environment may be running 10.6.x while another runs 10.7.x.
 
 {% endhint %}
 

umbraco-cloud/optimize-and-maintain-your-site/manage-product-upgrades/product-upgrades/manual-upgrades/README.md

@@ -8,7 +8,7 @@ description: >-
 
 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 **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.
+Umbraco Cloud project uses Umbraco Forms and Umbraco Deploy. This means there are some dependencies you need to consider when upgrading your Umbraco Cloud project manually.
 
 ## Why and when would you do a manual upgrade?
 
@@ -18,17 +18,17 @@ When a new _minor_ version (like 8.**8**) is released, the upgrade is applied to
 
 For 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 ensure everything works when upgrade is complete.
 
-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.
+It is recommended to use the automatic and _semi-automatic_ upgrade options provided to you as part of your Umbraco Cloud project. It's also possible to upgrade your Umbraco Cloud project manually. This can be done with both patches and minor and major versions.
 
-A reason for doing a manual upgrade of your Cloud project could be if you want to test out new features and functionality on your local machine before they are applied to your Cloud environments.
+Manually upgrading your Cloud project allows you to test out new features and functionality on your local machine before applying them to your Cloud environments.
 
 ## Product dependencies
 
-When you are manually upgrading a Umbraco Cloud project it's important that you take into account the dependencies that exist between the products on Umbraco Cloud. To continue reaping the full benefits of Umbraco Cloud make sure to check for dependencies when you upgrade to a new minor or major version of Umbraco CMS.
+When manually upgrading a Umbraco Cloud project, it is important to consider the dependencies that exist between the  products on Umbraco Cloud. To fully benefit from Umbraco Cloud, be sure to check for these dependencies before upgrading to a new minor or major version of Umbraco CMS.
 
 ## Upgrade order
 
-When you are manually upgrading your Umbraco Cloud project and you need to upgrade two or more products, this is the order you need to follow:
+When you are manually upgrading your Umbraco Cloud project and need to upgrade two or more products, follow this order:
 
 1. Umbraco CMS
 2. Umbraco Forms

umbraco-cloud/optimize-and-maintain-your-site/manage-product-upgrades/product-upgrades/manual-upgrades/manual-cms-upgrade.md

@@ -21,31 +21,29 @@ This article will give you a step-by-step on how to manually upgrade your Umbrac
 ## Get the latest version of Umbraco
 
 {% hint style="info" %}
-If your Cloud project is running **legacy** **Umbraco (version 7 or 8)**, you will need to follow an approach specific to those versions.
 
-Find the steps you need in the [Manual upgrades for legacy Umbraco](manual-cms-upgrade.md#manual-upgrades-for-legacy-umbraco) section.
-{% endhint %}
-
-To get the latest version of Umbraco you will need to upgrade the site using NuGet.
+For Cloud projects using **legacy Umbraco versions (7 or 8)**, follow the specific steps outlined in the [Manual upgrades for legacy Umbraco](manual-cms-upgrade.md#manual-upgrades-for-legacy-umbraco) section.
 
-NuGet installs the latest version of the package when you use the `dotnet add package` command unless you specify a package version:
-
-`dotnet add package Umbraco.Cms --version <VERSION>`
+{% endhint %}
 
-After you have added a package reference to your project by executing the `dotnet add package Umbraco.Cms` command in the directory that contains your project file, run `dotnet restore` to install the package.
+To get the latest version of Umbraco, follow these steps:
 
-Alternatively, you can update the CMS through the `NuGet Package Manager` in Visual Studio:
+1. Run the `dotnet add package Umbraco.Cms` command in the directory that contains your project files. If you want a specific version, run the `dotnet add package Umbraco.Cms --version <VERSION>` command.
 
-![NuGet Package Manager](images/Manage_packages.png)
+2. Run `dotnet restore` to install the package.
 
-When the command completes, open the `.csproj` file to make sure the package reference was updated:
+3. Open your `.csproj` file and confirm that the `Umbraco.Cms` package reference shows the correct version.
 
 ```xml
 <ItemGroup>
   <PackageReference Include="Umbraco.Cms" Version="x.x.x" />
 </ItemGroup>
 ```
 
+Alternatively, you can also update Umbraco via the `NuGet Package Manager` in Visual Studio:
+
+![NuGet Package Manager](images/Manage_packages.png)
+
 <details>
 
 <summary>Manual upgrades for legacy Umbraco</summary>
@@ -60,9 +58,9 @@ When the command completes, open the `.csproj` file to make sure the package ref
 
 **Merge configuration files**
 
-In this step, you need to merge the configuration files containing changes. For this, we recommend using a tool like [WinMerge](http://winmerge.org/) or [DiffMerge](https://sourcegear.com/diffmerge/).
+In this step, you need to merge the configuration files containing changes. For this, it is recommended to use a tool like [WinMerge](http://winmerge.org/) or [DiffMerge](https://sourcegear.com/diffmerge/).
 
-The reason you shouldn't overwrite these files is that this will also overwrite any **custom configuration** you might have as well as **Umbraco Cloud-specific settings**. Read more about which Cloud-specific details you should watch out for in the following sections.
+Avoid overwriting these files, as it will overwrite any **custom configuration** and **Umbraco Cloud-specific settings**. Read more about which Cloud-specific details you should watch out for in the following sections.
 
 **`Web.config`**
 
@@ -178,7 +176,7 @@ This concludes the steps specific to the legacy Umbraco versions. To continue, f
 
 ## Run the upgrade locally
 
-When you are done updating the NuGet packages as mentioned above, follow these steps to complete the upgrade and verify that everything is working as expected before you push the changes to your Umbraco Cloud project
+After updating the NuGet packages, follow these steps to complete the upgrade. Make sure everything is functioning correctly before pushing the changes to your Umbraco Cloud project.
 
 * Run the project locally
 * When the project spins up, you'll be prompted to log in to verify the upgrade

umbraco-cloud/optimize-and-maintain-your-site/manage-product-upgrades/product-upgrades/manual-upgrades/manual-upgrade-deploy.md

@@ -14,27 +14,24 @@ This article will give you a step-by-step on how to manually upgrade the deploym
 
 ## Prepare for the upgrade
 
-When upgrading an Umbraco Cloud project manually, the very first step is to [clone down your Cloud Development environment to your local machine](../../../../build-and-customize-your-solution/handle-deployments-and-environments/working-locally/).
+When upgrading an Umbraco Cloud project manually, the first step is to [clone down your Cloud Development environment to your local machine](../../../../build-and-customize-your-solution/handle-deployments-and-environments/working-locally/).
 
-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.
+Make sure you can run your Cloud project locally and restore content and media. It is important that you check that everything works correctly after the upgrade. To achieve this, you need to have a clone locally that resembles the Cloud environment as much as possible.
 
 ## Get the latest version of Umbraco
 
-To get the latest version of Umbraco Deploy you will need to upgrade the site using NuGet. The main package to install is Umbraco.Deploy.Cloud. This has dependencies on other components of Umbraco Deploy that will be imported automatically.
+To get the latest version of Umbraco Deploy you will need to upgrade the site using NuGet. The main package to install is `Umbraco.Deploy.Cloud`. This has dependencies on other components of Umbraco Deploy that will be imported automatically.
 
-If using Umbraco Forms in your installation, you should also update the Umbraco.Deploy.Forms package reference,
+If using Umbraco Forms in your installation, you should also update the `Umbraco.Deploy.Forms` package reference.
 
-NuGet installs the latest version of the package when you use the dotnet add package command unless you specify a package version:
+1. Run the `dotnet add package Umbraco.Deploy.Cloud` command in the directory that contains your project files. If you want a specific package version, run these commands:
+  
+  - `dotnet add package Umbraco.Deploy.Cloud --version <VERSION>`
+  - `dotnet add package Umbraco.Deploy.Forms --version <VERSION>`
 
-`dotnet add package Umbraco.Deploy.Cloud --version <VERSION>` `dotnet add package Umbraco.Deploy.Forms --version <VERSION>`
+2. Run `dotnet restore` to install the packages.
 
-After you have added a package reference to your project by executing the commands above in the directory that contains your project file, run `dotnet restore` to install the packages.
-
-You can also update the Umbraco Deploy through the NuGet Package Manager in Visual studio:
-
-![NuGet Package Manager](images/Manage_packages.png)
-
-When the command completes, open the `.csproj` file to make sure the package reference was updated:
+3. Open your `.csproj` file to make sure the package reference is updated:
 
 ```xml
 <ItemGroup>
@@ -43,6 +40,10 @@ When the command completes, open the `.csproj` file to make sure the package ref
 </ItemGroup>
 ```
 
+Alternatively, you can also update Umbraco Deploy via the **NuGet Package Manager** in Visual studio:
+
+![NuGet Package Manager](images/Manage_packages.png)
+
 Make sure that everything works on the local clone and that you can **run the project without any errors**.
 
 ## Manually Upgrade Umbraco Deploy Legacy Version 7 and 8

umbraco-cloud/optimize-and-maintain-your-site/manage-product-upgrades/product-upgrades/version-specific-upgrades/migrate-from-8-to-latest.md

@@ -27,15 +27,19 @@ You also need to make sure that the packages that you are using are available on
 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)
+
+If your Umbraco 8 site is using Umbraco Forms, ensure you configure it to save data in the database, before starting this tutorial. For more information on migrating Umbraco Forms data to the database, see the[Umbraco Forms in the Database](https://docs.umbraco.com/umbraco-forms/developer/forms-in-the-database) article.
 
 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
 
 {% embed url="https://www.youtube-nocookie.com/embed/wD9SGeRQR7o" %}
-A video tutorial guiding you through the steps of upgrading from version 8 to the latest version on Umbraco Cloud
+
+A video tutorial guiding you through the steps of upgrading from version 8 to the latest version on Umbraco Cloud.
+
 {% endembed %}
 
 ## Step 1: Content Migration