GITBOOK-16: No subject

Author: Sofie Toft Kristensen

16/umbraco-cms/fundamentals/setup/upgrading/README.md

@@ -17,9 +17,9 @@ You will find instructions on how to upgrade to a new minor or major version as
 
 The following lists a few things to be aware of before initiating an upgrade of your Umbraco CMS project.
 
-* Sometimes there are exceptions to general upgrade guidelines. These are listed in the [**version-specific guide**](version-specific/). Be sure to read this article before moving on.
-* Check if your setup meets the [requirements](../requirements.md) for the new versions you will be upgrading your project to.
-* Things may go wrong for different reasons. Be sure to **ALWAYS** keep a backup of both your site's files and the database. This way you can always return to a version that you know works.
+* Sometimes, there are exceptions to general upgrade guidelines. These are listed in the [**version-specific guide**](version-specific/). Be sure to read this article before moving on.
+* Ensure your setup meets the [requirements](../requirements.md) for the new versions you will be upgrading your project to.
+* Things may go wrong for different reasons. Be sure to **always** keep a backup of both your site's files and the database. This way, you can always return to a version that you know works.
 * Before upgrading to a new major version, check if the packages you're using are compatible with the version you're upgrading to. On the package's download page, in the **Project compatibility** area, click **View details** to check version-specific compatibility.
 
 {% hint style="info" %}
@@ -28,9 +28,9 @@ It is necessary to run the upgrade installer on each environment of your Umbraco
 
 ## Legacy Umbraco
 
-The steps outlined in this article apply to modern Umbraco from version 10 and later versions.
+The steps outlined in this article apply to Umbraco version 10 and later versions.
 
-Are you upgrading to a minor for Umbraco 6, 7, or 8 you can find the appropriate guide below:
+Are you upgrading to a minor version for Umbraco 6, 7, or 8? You can find the appropriate guide below:
 
 {% content-ref url="version-specific/minor-upgrades-for-umbraco-8.md" %}
 [minor-upgrades-for-umbraco-8.md](version-specific/minor-upgrades-for-umbraco-8.md)
@@ -42,12 +42,12 @@ Are you upgrading to a minor for Umbraco 6, 7, or 8 you can find the appropriate
 
 ## Upgrade to a new Major
 
-You can upgrade to a new major of Umbraco CMS directly by using NuGet.
+You can upgrade to a new major version of Umbraco CMS directly by using NuGet.
 
-It is recommended that you upgrade to the closest [Long-term Support (LTS) major](https://umbraco.com/products/knowledge-center/long-term-support-and-end-of-life/) version before upgrading to the latest version. For Umbraco 10, the closest long-term support version is Umbraco 13. Once upgraded to Umbraco 13, you can upgrade to Umbraco 14.
+You must upgrade to the closest [Long-term Support (LTS) major](https://umbraco.com/products/knowledge-center/long-term-support-and-end-of-life/) version before upgrading to the latest version. For Umbraco 10, the closest long-term support version is Umbraco 13. Once the project is on Umbraco 13, you can move on to Umbraco 14.
 
 {% hint style="warning" %}
-Switching to a new major of Umbraco CMS also means switching to a new .NET version. You need to make sure that any packages used on your site are compatible with this version before upgrading.
+Switching to a new major version of Umbraco CMS also means switching to a new .NET version. Ensure that any packages used on your site are compatible with this version before upgrading.
 
 The package compatibility can be checked on the package's download page. Locate the **Project compatibility** area and select **View details** to check version-specific compatibility.
 {% endhint %}
@@ -79,39 +79,37 @@ It's recommended that you upgrade the site offline and test the upgrade fully be
 3. Right-click on the project name in the Solution Explorer and select **Properties**.
 4. Select the **.NET** version from the **Target Framework** drop-down.
 5. Go to **Tools** > **NuGet Package Manager** > **Manage NuGet Packages for Solution...**
-6. Go to the **Installed** tab in the NuGet Package manager.
+6. Go to the **Installed** tab in the NuGet Package Manager.
 7.  Upgrade **Umbraco.Cms**.
 
     a. Select the correct version from the **Version** drop-down.
 
     b. Click **Install** to upgrade your project.
 
 {% hint style="info" %}
-If you have other packages like Umbraco Forms installed, upgrade them before upgrading **Umbraco.CMS**. Consult the [version specific upgrade notes for Umbraco Forms](https://docs.umbraco.com/umbraco-forms/upgrading/version-specific) if relevant.
+If you have other packages like Umbraco Forms installed, upgrade them before upgrading **Umbraco.CMS**. Consult the [version-specific upgrade notes for Umbraco Forms](https://docs.umbraco.com/umbraco-forms/upgrading/version-specific) if relevant.
 {% endhint %}
 
-8. Make sure that your connection string has `TrustServerCertificate=True` in order to complete the upgrade successfully:
+8. Make sure that your connection string has `TrustServerCertificate=True` to complete the upgrade successfully:
 
 {% code title="appsettings.json" %}
-
 ```csharp
 "ConnectionStrings": {
     "umbracoDbDSN": "Server=YourLocalSQLServerHere;Database=NameOfYourDatabaseHere;User Id=NameOfYourUserHere;Password=YourPasswordHere;TrustServerCertificate=True"
 }
 ```
-
 {% endcode %}
 
 9. Restart your site in IIS, then build and run your project to finish the installation.
 
 {% hint style="info" %}
-Umbraco 13 and later versions uses the [Minimal Hosting Model](https://github.com/umbraco/Umbraco-CMS/pull/14656).
+Umbraco 13 and later versions use the [Minimal Hosting Model](https://github.com/umbraco/Umbraco-CMS/pull/14656).
 
 If you have added custom code to the `startup.cs` file, it is recommended to move that code into a Composer after upgrading.
 {% endhint %}
 
 {% hint style="warning" %}
-If your database experiences timeout issues after an upgrade, it might be due to [ASP.NET Core Module's](https://learn.microsoft.com/en-us/aspnet/core/test/troubleshoot-azure-iis?#default-startup-limits) 'startupTimeLimit' configuration.
+If your database experiences timeout issues after an upgrade, it might be due to the [ASP.NET Core Module's](https://learn.microsoft.com/en-us/aspnet/core/test/troubleshoot-azure-iis?#default-startup-limits) `startupTimeLimit` configuration.
 
 To fix the issue, try increasing the [`startupTimeLimit`](https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/web-config?) in the `web.config` file. Additionally, you can set the [`Connection Timeout`](https://learn.microsoft.com/en-us/dotnet/api/system.data.sqlclient.sqlconnection.connectiontimeout?) value in the [`ConnectionString`](https://learn.microsoft.com/en-us/dotnet/api/microsoft.data.sqlclient.sqlconnection.connectionstring?) in the `appsettings.json` file.
 {% endhint %}
@@ -127,19 +125,18 @@ Add a package reference to your project by executing the `dotnet add package Umb
 Run `dotnet restore` to install the package.
 
 {% hint style="warning" %}
-For v9: If you are using SQL CE in your project you will need to run `dotnet add package Umbraco.Cms.SqlCe --version <VERSION>` before running the `dotnet restore` command. From v10, SQL CE has been replaced with SQLite so a `dotnet restore` should be sufficient. If this is not working then you will need to run `dotnet add package Umbraco.Cms.Persistence.Sqlite --version <VERSION>` and then `dotnet restore`.
+**For Umbraco 9**\
+If you are using SQL CE in your project, you need to run `dotnet add package Umbraco.Cms.SqlCe --version <VERSION>` before the `dotnet restore` command. From Umbraco 10, SQL CE has been replaced with SQLite, so a `dotnet restore` should be sufficient. If this is not working, then you need to run `dotnet add package Umbraco.Cms.Persistence.Sqlite --version <VERSION>` , and then `dotnet restore`.
 {% endhint %}
 
-When the command completes, open the **.csproj** file to make sure the package reference was updated:
-
-{% code title=".csproj" %}
+When the command completes, open the `.csproj` file to make sure the package reference was updated:
 
+{% code title="YourProjectName.csproj" %}
 ```xml
 <ItemGroup>
   <PackageReference Include="Umbraco.Cms" Version="x.x.x" />
 </ItemGroup>
 ```
-
 {% endcode %}
 
 ## Run an unattended upgrade
@@ -149,9 +146,9 @@ When upgrading your Umbraco project, it is possible to enable the upgrade to run
 Below you will find the steps you need to take in order to upgrade your project unattended.
 
 {% hint style="info" %}
-Are you running a load balanced setup with multiple servers and environments?
+Are you running a load-balanced setup with multiple servers and environments?
 
-Check out the section about [Unattended upgrades in a load balanced setup](./#unattended-upgrades-in-a-load-balanced-setup).
+Check out the section about [Unattended upgrades in a load-balanced setup](./#unattended-upgrades-in-a-load-balanced-setup).
 {% endhint %}
 
 ### Enable the unattended upgrade feature
@@ -160,7 +157,6 @@ Check out the section about [Unattended upgrades in a load balanced setup](./#un
 2. Set the value of the key to `true`.
 
 {% code title="appsettings.json" %}
-
 ```json
 {
     "Umbraco": {
@@ -172,7 +168,6 @@ Check out the section about [Unattended upgrades in a load balanced setup](./#un
     }
 }
 ```
-
 {% endcode %}
 
 ### Run the upgrade
@@ -181,19 +176,19 @@ With the correct configuration applied, the project will be upgraded on the next
 
 #### Boot order
 
-The Runtime level will use `Run` instead of `Upgrade` to allow the website to continue to boot up directly after the migration is run. This happens instead of initiating the otherwise required restart.
+The Runtime level uses `Run` instead of `Upgrade` to allow the website to continue to boot up directly after the migration is run. This happens instead of initiating the otherwise required restart.
 
 {% hint style="info" %}
-The upgrade is run after Composers but before Components and the `UmbracoApplicationStartingNotification`. This is because the migration requires services that are registered in Composers and Components require that Umbraco and the database are ready.
+The upgrade is run after Composers but before Components, and the `UmbracoApplicationStartingNotification`. This is because the migration requires services that are registered in Composers, and Components require that Umbraco and the database are ready.
 {% endhint %}
 
-### Unattended upgrades in a load balanced setup
+### Unattended upgrades in a load-balanced setup
 
-Follow the steps outlined below to use unattended upgrades in a load balanced setup.
+Follow the steps outlined below to use unattended upgrades in a load-balanced setup.
 
-1. Upgrade Umbraco via NuGet ([see instructions above](./#upgrade-to-a-new-major))
+1. [Upgrade Umbraco via NuGet](./#upgrade-to-a-new-major).
 2. Deploy to all environments.
 3. Set the `Umbraco:CMS:Unattended:UpgradeUnattended` configuration key to `true` for **the Main server only**.
-4. Boot the Main server and the upgrade will run automatically.
+4. Boot the Main server, and the upgrade will run automatically.
 5. Wait for the upgrade to complete.
-6. Boot the Read-Only servers and make sure they do not show the “upgrade required” screen.
+6. Boot the Read-Only servers and ensure they do not show the “upgrade required” screen.