Clean up v15 version

Author: eshanrnh

15/umbraco-cms/tutorials/multisite-setup.md

@@ -1,60 +1,59 @@
 ---
-description: A guide to multisite setup in Umbraco
+description: A guide to setting up a multisite solution in Umbraco
 ---
 
 # Multisite Setup
 
-This tutorial explains how to host multiple sites from one project/installation of Umbraco. For practical reasons, we recommend using [Baselines](https://docs.umbraco.com/umbraco-cloud/getting-started/baselines) on Umbraco Cloud projects.
+This tutorial explains how to host multiple sites from one project or installation of Umbraco. For practical reasons, it is recommended to use [Baselines](https://docs.umbraco.com/umbraco-cloud/getting-started/baselines) on Umbraco Cloud projects.
 
 {% hint style="info" %}
-When using Baselines on Umbraco Cloud for a multisite solution, you would not need to worry about [Usage](https://docs.umbraco.com/umbraco-cloud/set-up/project-settings/usage) limits, and could see better performance compared to having multiple websites in one project.
+When using Baselines on Umbraco Cloud for a multisite solution, you don’t need to worry about [Usage](https://docs.umbraco.com/umbraco-cloud/set-up/project-settings/usage) limits. You may also see better performance compared to hosting multiple websites in one project.
 {% endhint %}
 
-If you are planning to create a multilingual site, please take a look at the [Multilanguage Setup](multilanguage-setup.md) tutorial instead.
+To create a multilingual site, see the [Multilanguage Setup](multilanguage-setup.md) tutorial.
 
 ## Structuring your website
 
-The best way to handle a multisite solution is to have multiple root nodes in the Content section, where each root node would act as a separate website.
+The best way to handle a multisite solution is to create multiple root nodes in the Content section. Each root node acts as a separate website.
 
-All the websites in your solution will use the same schema. In most cases, this would mean that your content pages on website A will use the same properties as on website B.
+All websites in the solution use the same schema. In most cases, content pages on website A use the same properties as on website B.
 
 {% hint style="info" %}
-If your site is hosted on Umbraco Cloud, you will need to map your sites' hostnames to the project.
-
-Before you can map your hostnames to individual websites in the solution, you should add them in the Hostnames page on the Cloud portal to ensure they are secured with TLS.
+On Umbraco Cloud, hostnames must be mapped to the project. Before mapping hostnames to individual websites, add them to the Hostnames page in the Cloud portal. This ensures they are secure with TLS.
 {% endhint %}
 
-![Adding hostnames to the project](../../../10/umbraco-cms/tutorials/images/1-addinghostnames.png)
+![Adding hostnames to the project](images/1-addinghostnames.png)
 
-Keep in mind the [hostnames have to be configured in a specific way.](https://docs.umbraco.com/umbraco-cloud/set-up/project-settings/manage-hostnames)
+Keep in mind that [hostnames must be configured in a specific way](https://docs.umbraco.com/umbraco-cloud/set-up/project-settings/manage-hostnames).
 
 ## Mapping the hostnames to individual websites/root nodes
 
-At this point, you will have multiple root nodes, each acting as a separate website. To map the hostnames to individual root nodes:
+At this point, multiple root nodes exist, each acting as a separate website. To map hostnames to root nodes:
 
 1. Go to the **Content** section.
-2. Click **...** next to the root node you wish to assign the hostname.
+2. Click **...** next to the root node to assign the hostname.
 3. Select **Culture and Hostnames**.
 
     ![Culture and hostnames](images/culturehostnames-v14.png)
-4. In the **Domains** pane, click **Add new Domain**.
-5. Enter the domain in the **Domain** field and select the language from the **Language** drop-down list. If you have a multilanguage solution, you can map different hostnames to specific languages.
+4. Click **Add new Domain** in the **Domains** pane.
+5. Enter the domain in the **Domain** field.
+6. Select the language from the **Language** drop-down list. For multilanguage setups, different hostnames can map to specific languages.
 
     ![Domain](images/inherit-domain.png)
 
-6. Click Save.
-7. Repeat steps 2-6 for each root node in the Content structure.
+7. Click **Save**.
+8. Repeat steps 2-7 for each root node in the Content tree.
 
-The sites are now available under the domains you provided.
+The sites are now available under the assigned domains.
 
-![Dolphin site](../../../10/umbraco-cms/tutorials/images/6-dolphins.png) ![SWATO site](../../../10/umbraco-cms/tutorials/images/7-swato.png)
+![Dolphin Website](images/6-dolphins.png) ![Swato Website](images/7-swato.png)
 
 ## Best practices
 
-While such a setup might be handy, it also comes with drawbacks. It is important to keep in mind that having multiple sites on one Umbraco project:
+This setup can be useful, but it also has drawbacks. Keep in mind that having multiple sites in one Umbraco project:
 
 * Might increase resource usage.
-* Could interfere with editors' workflows, especially if there are multiple people working on both websites at once. That is because the solution will still use one database for both websites.
-* Limit your options in regards to developing new features and making schema changes.
+* Could interfere with editors' workflows, especially if multiple people are working on both websites at once. This is because the solution still uses one shared database for both websites.
+* Limits options for developing new features and making schema changes.
 
-On Umbraco Cloud-hosted sites we recommend using the [Baseline](https://docs.umbraco.com/umbraco-cloud/getting-started/baselines) functionality - which comes with added benefits, and offers increased stability compared to the multisite solution in a single project.
+On Umbraco Cloud, using [Baselines](https://docs.umbraco.com/umbraco-cloud/getting-started/baselines) is recommended. Baselines provide added benefits and greater stability compared to hosting multiple sites in one project.