Merge pull request #7315 from umbraco/cloud/valeCleanup

Cloud Docs cleanup

Author: sofietoft

umbraco-cloud/begin-your-cloud-journey/creating-a-cloud-project/README.md

@@ -20,7 +20,7 @@ Creating a Trial Project
 
 ### Can I convert a Trial Project to a Paid Project?
 
-Yes. If you have started with a Trial project and decide to continue, you can upgrade to a Paid project within the 14 days trial period without losing your work. You can upgrade your trial to a paid plan within the Umbraco Cloud portal.
+Yes. You can upgrade to a paid project within the 14-day trial period without losing your work. You can upgrade your trial to a paid plan within the Umbraco Cloud portal.
 
 Umbraco Cloud provides a seamless transition from a trial to a paid plan. You can adjust your plan or resources as your project evolves.
 

umbraco-cloud/begin-your-cloud-journey/creating-a-cloud-project/baselines.md

@@ -40,7 +40,9 @@ It might take couple of minutes for the project to spin up before your environme
 ![Creating a Baseline child project](images/baseline-creation.gif)
 
 {% hint style="info" %}
-Depending on the size of the project you've chosen as a Baseline project, it might take several minutes before the Child project is ready.
+
+Depending on the size of the project chosen as a Baseline project, it can take a while before the Child project is ready.
+
 {% endhint %}
 
 ### Restore content from the Baseline project
@@ -67,7 +69,7 @@ In this article, you'll find a guide on how to upgrade your Child project with c
 
 ## [Handling configuration files](../../optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/baseline-merge-conflicts/configuration-files.md)
 
-When you are working with Baseline Child projects you might sometimes want to have an individual configuration for each project - this can be handled using config transforms.
+When you are working with Baseline Child projects you might sometimes want to have an individual configuration for each project. This can be handled using config transforms.
 
 ## [Break reference between baseline and child project](../../optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/baseline-merge-conflicts/break-baseline.md)
 

umbraco-cloud/begin-your-cloud-journey/creating-a-cloud-project/migrate-to-umbraco-cloud.md

@@ -149,7 +149,9 @@ The database is uploaded to the Umbraco Cloud project via the Umbraco Cloud Port
 Follow the **Upload Database** and **Restore Database** sections in the [Database Backups](../../build-and-customize-your-solution/set-up-your-project/databases/backups.md) article to complete this step in the migration.
 
 {% hint style="warning" %}
+
 You will not be able to view the front end of the website yet, as the project files have yet to be migrated.
+
 {% endhint %}
 
 The Umbraco Cloud project is now ready for the next step where the two projects will be merged.

umbraco-cloud/begin-your-cloud-journey/project-features/environments.md

@@ -62,7 +62,9 @@ The `EnvironmentAlias` is fetched from the Environment variable named `DOTNET_EN
 The value of the `DOTNET_ENVIRONMENT` environment variable can be managed through the **Advanced** settings in the **Configuration** section of the Cloud Portal.
 
 {% hint style="info" %}
-Make sure that when you start up the Umbraco Application, you load the correct JSON file as per the ASP.NET Configuration in the official [Microsoft documentation](https://learn.microsoft.com/en-us/aspnet/core/fundamentals/configuration/?view=aspnetcore-9.0).
+
+When you start up the Umbraco Application, ensure you load the correct JSON file as per the ASP.NET Configuration in the official [Microsoft documentation](https://learn.microsoft.com/en-us/aspnet/core/fundamentals/configuration/?view=aspnetcore-9.0).
+
 {% endhint %}
 
 ### Team Members

umbraco-cloud/begin-your-cloud-journey/project-features/secrets-management.md

@@ -14,7 +14,9 @@ Environment Secrets are intended to be utilized exclusively within a particular
 Shared Secrets are utilized across all environments and will be seamlessly integrated into any new environment you create. Shared Secrets are particularly well-suited for safeguarding credentials necessary for project development, such as access to private NuGet feeds.
 
 {% hint style="warning" %}
+
 Utilizing environment-specific secrets for private NuGet feeds will result in the unsuccessful creation of new environments due to the unknown status of the secret. In such instances, **Shared Secrets** should be used.
+
 {% endhint %}
 
 Typical secrets are **Private Keys**, **3rd-party API tokens**, **database passwords**, or otherwise **sensitive data** that needs to be kept secret.

umbraco-cloud/begin-your-cloud-journey/project-features/team-members/README.md

@@ -29,10 +29,17 @@ You can view the user group memberships of the project’s backoffice users. Cur
 
 ## Team Members Pending Invitation
 
-You can see the details of your project invitation in the **Member(s) who still needs to accept the project invitation** section of the **Edit Team** page. You can view the team member's name, email, the expiration date of the invitation, the status of the invitation, copy the invitation link, resend the invitation, or delete the invitation.
+Find invitation details in the **Member(s) who still needs to accept the project invitation** section of the **Edit Team** page. You have the following options:
+
+* View the team member's name and email.
+* See the expiration date of the invitation.
+* Check the status of the invitation.
+* Copy the invitation link.
+* Resend the invitation.
+* Delete the invitation.
 
 ![Team Members Pending Invitation](images/Pending-Project-Invites.png)
 
 ## [Technical Contacts](technical-contact.md)
 
-For us to reach the correct person when sending out information about server maintenance, you need to add a technical contact to your Umbraco Cloud project.
+To ensure information about server maintenance reaches the correct person, add/update the technical contact to your Umbraco Cloud project.

umbraco-cloud/begin-your-cloud-journey/project-features/team-members/technical-contact.md

@@ -5,19 +5,23 @@ One of the biggest benefits of having a Umbraco Cloud project is that you do not
 When we do maintenance on our Umbraco Cloud servers, we send out information to all our Umbraco Cloud customers. For us to reach out to the correct person, you need to add a **Technical Contact** to your project.
 
 {% hint style="info" %}
+
 If you have more than one project on Umbraco Cloud, you will need to add a technical contact to each of the projects manually.
+
 {% endhint %}
 
 When you create a **New Project**, the user used to create the project will automatically be added as the technical contact. To update the technical contact or add more than one technical contact, do the following:
 
 1. Go to the Project in the Umbraco Cloud Portal.
 2. Go to **Edit Team** in the Overview menu tab.
-3.  Click Add **Technical Contact** in the **Technical Contact** section.
+3. Click **Add Technical Contact** in the **Technical Contacts** section.
+
+<figure><img src="../../../.gitbook/assets/image (31).png" alt=""><figcaption><p>Add Technical contact</p></figcaption></figure>
+
+4. Enter the **Name**, **Email**, and **Telephone Number** in the **Add New Technical Contact** window.
 
-    <figure><img src="../../../.gitbook/assets/image (31).png" alt=""><figcaption><p>Add Technical contact</p></figcaption></figure>
-4.  Enter the **Name**, **Email**, and **Telephone Number** in the **Add New Technical Contact** window.
+<figure><img src="../../../.gitbook/assets/image (32).png" alt=""><figcaption></figcaption></figure>
 
-    <figure><img src="../../../.gitbook/assets/image (32).png" alt=""><figcaption></figcaption></figure>
 5. Click **Confirm**.
 
 {% embed url="https://www.youtube.com/watch?ab_channel=UmbracoLearningBase&v=BUiiphvcrsE" %}

umbraco-cloud/begin-your-cloud-journey/project-features/users-on-cloud.md

@@ -10,29 +10,31 @@ In this article, we will show how users work, as well as explain the different s
 
 ## Umbraco ID
 
-On Umbraco Cloud project we use Umbraco ID. Umbraco ID is a centralized login for all users on Umbraco Cloud, both team members and Umbraco Backoffice users. It is used when you log in to the Umbraco Cloud Portal, projects, as well as when you clone down a project to your local machine.
+Umbraco ID is a centralized login for all users on Umbraco Cloud, both team members and Umbraco Backoffice users. It is to log in to the Umbraco Cloud Portal, projects, as well as cloning down a project to your local machine.
 
-When working locally the initial login will go through Umbraco ID and the online login flow. After the initial login, you can set a password on your user or create a new login for the backoffice, which can be used for local logins.
+When working locally the initial login will go through Umbraco ID and the online login flow. After the initial login, you can set a password on your user or create a new local login for the backoffice.
 
 ## Adding users on Umbraco Cloud
 
 There are two ways of adding a user to your backoffice on Umbraco Cloud.
 
 You can add them as a [team member](team-members/)) from the project portal on Umbraco Cloud.
 
-By default, when added to the project as a team member, they will be added as users to the backoffice of all the environments as administrators.
+By default, when added as a team member, they are added as users to the backoffice of all the environments as administrators.
 
 Users can also be invited directly from the backoffice of your Umbraco Cloud project, from where you can give them different permissions.
 
 Check out the [Users article](https://docs.umbraco.com/umbraco-cms/fundamentals/data/users) for an in-depth explanation about Umbraco users in general.
 
 {% hint style="info" %}
-Users are environment-specific on Umbraco Cloud. This means that they will not be transferred over when doing a deployment to the next environment they will need to be added to the different environments on Umbraco Cloud.
+
+Users are environment-specific on Umbraco Cloud. This means that users are not transferred over when doing a deployment to the next environment. They need to be added to each environment on Umbraco Cloud where their access is needed.
+
 {% endhint %}
 
 ## Invite User through the Umbraco backoffice
 
-As mentioned it is possible to invite new Users to your Umbraco Cloud project through the backoffice as you would on a normal installation of Umbraco.
+As mentioned, it is possible to invite new Users to your Umbraco Cloud project through the backoffice.
 
 To invite a User you need to do the following:
 
@@ -47,7 +49,7 @@ To invite a User you need to do the following:
 
 Once the User has been invited they will receive an invitation for the project.
 
-If the invited person already has a user on Umbraco Cloud they will be able to see the invitation in the project portal under "Project Invites".
+If the invited person already has a user on Umbraco Cloud they will see the invitation in the project portal under "Project Invites".
 
 If the User being invited does not have a User on Umbraco Cloud, they will receive an email asking them to create one.
 
@@ -67,9 +69,9 @@ On Umbraco Cloud, it is possible to control which users have access to transferr
 
 This can be done when creating a new User Group or when editing an existing group.
 
-You have the option to decide whether a specific User Group has permission to do a restore, partial restore, or queue content for transfer to the next environment.
+You can decide whether a specific User Group has permission to do restores and queue content for transfer to the next environment.
 
-It is also possible to get Granular control on a per-node basis so that you can disable restore and transfer for specific content on your site. This can help avoid mistakes and ensure that the proper workflows are followed.
+It is also possible to get Granular control on a per-node basis to restrict restores and transfers of specific content on your site. This can help avoid mistakes and ensure that the proper workflows are followed.
 
 ### Set up Permissions for transfers and restores
 
@@ -80,13 +82,15 @@ There are two ways that you can set up these permissions:
 
 To create a User Group, go to the **Users** section of the backoffice.
 
-1.  Click on "Groups" in the right corner, from here you are able to either create a new User Group or edit an existing one.
+1. Click on "Groups" in the right corner, from here you are able to either create a new User Group or edit an existing one.
+
+![User Groups](../../build-and-customize-your-solution/set-up-your-project/project-settings/images/Users.png)
 
-    ![User Groups](../../build-and-customize-your-solution/set-up-your-project/project-settings/images/Users.png)
 2. Click "Create group"
-3.  Scroll down and go to the "Content" heading in the "Default permissions" section. Here you can see three options:
+3. Scroll down and go to the "Content" heading in the "Default permissions" section. Here you can see three options:
+
+![User Groups](../../build-and-customize-your-solution/set-up-your-project/project-settings/images/default_permisions-v10.png)
 
-    ![User Groups](../../build-and-customize-your-solution/set-up-your-project/project-settings/images/default_permisions-v10.png)
 4. Decide whether the users in the new User Group can restore items for the whole workspace, restore items for a tree, or partially restore items and click **Save**.
 
 To edit an already existing User Group:
@@ -100,13 +104,15 @@ It is also possible to set Granular permissions for a specific content node on y
 
 You can set the permission when you are creating or editing an existing User Group.
 
-1.  Add the setting for Granular permission for your content nodes at the bottom of the User Group.
+1. Add the setting for Granular permission for your content nodes at the bottom of the User Group.
+
+![Granular permission](../../build-and-customize-your-solution/set-up-your-project/project-settings/images/Granular.png)
 
-    ![Granular permission](../../build-and-customize-your-solution/set-up-your-project/project-settings/images/Granular.png)
 2. Click "Add".
-3.  Choose the content node which you want to set the Granular settings for.
+3. Choose the content node which you want to set the Granular settings for.
+
+![Granular content node](../../build-and-customize-your-solution/set-up-your-project/project-settings/images/Granular_node.png)
 
-    ![Granular content node](../../build-and-customize-your-solution/set-up-your-project/project-settings/images/Granular_node.png)
-4.  Set permissions for restore, partial restore, and queueing content for transfer.
+4. Set permissions for restore, partial restore, and queueing content for transfer.
 
-    ![Granular permission](../../build-and-customize-your-solution/set-up-your-project/project-settings/images/Granular_permission-v10.png)
+![Granular permission](../../build-and-customize-your-solution/set-up-your-project/project-settings/images/Granular_permission-v10.png)