clean up hotfix article

Author: sofietoft

umbraco-cloud/optimize-and-maintain-your-site/manage-product-upgrades/hotfixes/move-files-manually.md

@@ -19,7 +19,7 @@ In this tutorial GitKraken has been used, however, you can use any Git GUI you p
 
 You have an Umbraco Cloud project with two environments, **Development** and **Live**.
 
-You have been working on building the site on a local clone of the Development environment, and now you want to send some but not all changes to the Live environment.
+You have been working on building the site on a local clone of the Development environment. Now, you want to send some but not all changes to the Live environment.
 
 Three commits have been pushed from your local clone to the Development environment. Out of these three commits, you only need the changes from one of the commits in the Live environment.
 
@@ -52,7 +52,7 @@ For the sake of simplicity here's an explanation of the names I'll be using in t
 3. Copy and paste the new and/or updated files from your Development repository to your Live repository.
 4. You can now _Stage_ and _Commit_ these changes to the Live repository in Git.
 
-One of the benefits of having the Live environment cloned down, is that you can test the new changes locally before sending them to the Live environment.
+A benefit of having the Live environment cloned down, is that you can test the new changes locally before sending them to the Live environment.
 
 ### Test changes locally
 
@@ -71,10 +71,12 @@ Once you've checked that everything works locally, you are ready to push to the
 1. Push the committed changes to the Live environment using Git.
 
 {% hint style="info" %}
+
 When changes are pushed directly to a Live environment and you have more than one environment, the changes are not automatically extracted to the site.
+
 {% endhint %}
 
-2\. Run the Deploy operation `Update Umbraco Schema From Data Files`from the Deploy Dashboard
+2. Run the Deploy operation `Update Umbraco Schema From Data Files`from the Deploy Dashboard
 
 You have now applied a hotfix to the Live environment.
 

umbraco-cloud/optimize-and-maintain-your-site/manage-product-upgrades/hotfixes/using-git.md

@@ -7,14 +7,14 @@ In this article, you'll find a step-by-step guide on how to apply a hotfix to a
 {% hint style="info" %}
 You can use whichever Git client or command line interface you prefer.
 
-If you've never worked with cherry-picking before, we recommend that you use a Git client with a UI that gives you a visual overview of your commits.
+If you've never worked with cherry-picking before, we recommend that using a Git client with visual overview of your commits.
 {% endhint %}
 
 ## The scenario
 
 You have an Umbraco Cloud project with two environments, Development and Live.
 
-You have been working on building the site on a local clone of the Development environment, and now you want to send some but not all changes to the Live environment.
+You have been working on building the site on a local clone of the Development environment. Now you want to send some but not all changes to the Live environment.
 
 A set of commits have been pushed from your local clone to the Development environment. Out of these commits, you only need the changes from two of the commits in the Live environment for now.
 
@@ -58,13 +58,15 @@ Before you push the newly created branch to Umbraco Cloud we need to change the
 3. You will be prompted to authenticate - use your Umbraco Cloud credentials.
 4. You will see that the history from the Live repository is visible in the Git history.
 5. Next step; hit **Push**.
-6.  Choose to push to the newly added remote, and write **master** to make sure you are pushing to the master branch on the Live environment.
+6. Choose to push to the newly added remote, and write **master** to make sure you are pushing to the master branch on the Live environment.
 
     ![Choose remote](images/choose-remote.png)
 7. Hit **Submit** and the push will start.
 
 {% hint style="info" %}
+
 When changes are pushed directly to a Live environment and you have more than one environment, the changes are not automatically extracted into the site.
+
 {% endhint %}
 
 Find a guide on how to extract the files in the [Manual Extraction](../../monitor-and-troubleshoot/power-tools/manual-extractions.md) article.