Fixed vale errors

Author: eshanrnh

.github/styles/UmbracoDocs/Acronyms.yml

@@ -36,6 +36,7 @@ exceptions:
   - DELETE   # HTTP DELETE method
   - DHL      # International Shipping brand
   - DIBS     # DIBS by Nets
+  - DLL      # Dynamic-Link Library
   - DNS      # Domain Name System
   - DOM      # Document Object Model
   - DXP      # Digital Experience Platform

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

@@ -45,9 +45,9 @@ If too many secrets are added, or if secret values are too large, your environme
 
 It is recommended to:
 
-- Keep secrets small and concise.
-- Store only sensitive values as secrets (for example: API keys, connection strings).
-- Use `appsettings.json` for general configuration values.
+* Keep secrets small and concise.
+* Store only sensitive values as secrets (for example: API keys, connection strings).
+* Use `appsettings.json` for general configuration values.
 {% endhint %}
 
 To add a secret to your environment, follow these steps:
@@ -176,6 +176,4 @@ The following prefixes are allowed for Secrets on Umbraco Cloud:
 
 It is also possible to use Secrets to save API keys, Passwords, and ReChaptcha for all our Umbraco products on Umbraco Cloud.
 
-Do you have an existing or new secret that you want to add to a key vault that conflicts with the name restrictions?
-
-Then please contact Umbraco support, then we will consider it as soon as possible.
+Do you have an existing or new secret that you want to add to a key vault that conflicts with the name restrictions? Contact Umbraco Support and it will be considered as soon as possible.

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

@@ -17,7 +17,7 @@ User Permissions for each environment can be set in the **Edit Team** page avail
 <figure><img src="images/Edit-Team.png" alt=""><figcaption></figcaption></figure>
 
 * **Admin**: Has access to everything on a project. An admin can delete a project and edit the team. An admin can deploy changes between environments in the Project Portal and has access to git, as well as the Power Tools Kudu.
-* **Read**: A team member with Read permissions can only view the project in the portal as well as the backoffices. They are not able to deploy or change anything on the project itself. They can clone down the project, but cannot push changes they have made locally. By default, they are added as an admin in the backoffice so they can make changes in the backoffice. If you want to change this, see Team Member Permissions in the Umbraco Backoffice below.
+* **Read**: A team member with Read permissions can only view the project in the portal as well as the backoffice. They are not able to deploy or change anything on the project itself. They can clone down the project, but cannot push changes they have made locally. By default, they are added as an admin in the backoffice so they can make changes in the backoffice. If you want to change this, see Team Member Permissions in the Umbraco Backoffice below.
 * **Write**: A team member with Write permissions can do everything on a project except delete it and edit the team. A user with Write permissions can deploy changes between environments through the portal. They have access to the git repositories and can push local changes to the environment.
 * **No Access**: A team member with No access permissions cannot restart the environment, deploy changes between environments, check error logs or log files, or access Kudo in the Project Portal. They can view the project in the portal and access the backoffice.
 

umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/deployment/local-to-cloud.md

@@ -60,4 +60,4 @@ To validate your local site and ensure compatibility with the updated schema, us
 
 Here, you can see the status of ongoing or completed deployment processes. The status will show whether an operation has been triggered and is in progress has been completed, or has failed.
 
-The dashboard will show the status based on the marker files on the disk, eg. `deploy-progress`. From the **Deploy** Dashboard, it is also possible to trigger different processes.
+The dashboard will show the status based on the marker files on the disk, for example, `deploy-progress`. From the **Deploy** Dashboard, it is also possible to trigger different processes.

umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/deployment/restoring-content/README.md

@@ -2,7 +2,7 @@
 
 When you have content on your Cloud environment and clone down your project to your local machine, you need to restore the content. You will also need to use the restore option when setting up new Cloud environments.
 
-The restore option can be used to always ensure you work with the latest content when delevoping new features.
+The restore option can be used to always ensure you work with the latest content when developing new features.
 
 ## How to Restore Content
 

umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/README.md

@@ -26,7 +26,7 @@ Attaching a CI/CD pipeline to a flexible environment is currently not possible.
 
 **Centralized Management**
 
-* With Umbraco CI/CD Flow, you can centralize the management of your deployments, tests, and workflows. This makes it easier to monitor, troubleshoot, and optimize your processes, leading to more efficient and reliable deployments. Automating deployment minimizes the risc for human errors that could have a negative effect on the target environment.
+* With Umbraco CI/CD Flow, you can centralize the management of your deployments, tests, and workflows. This makes it easier to monitor, troubleshoot, and optimize your processes, leading to more efficient and reliable deployments. Automating deployment minimizes the risk for human errors that could have a negative effect on the target environment.
 
 Umbraco CI/CD Flow serves as a bridge between your existing CI/CD pipeline and Umbraco Cloud, enabling a more streamlined and automated deployment process. While it offers a number of advantages, there are also limitations that need to be considered. On the page '[Known Limitations and Considerations](knownlimitationsandconsiderations.md)' you will find a detailed list of the pros and cons of using Umbraco CI/CD Flow.
 

umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/working-locally/legacy-umbraco-visual-studio-setup.md

@@ -145,7 +145,7 @@ To use ModelsBuilder with IntelliSense in Visual Studio, you'll need to make som
 This will make the models of your Document Types available with IntelliSense in Visual Studio. [You can read more about configuring ModelsBuilder here](https://docs.umbraco.com/umbraco-cms/reference/templating/modelsbuilder).
 
 {% hint style="info" %}
-Are using the [Visual Studio Extension for ModelsBuilder](https://marketplace.visualstudio.com/items?itemName=ZpqrtBnk.UmbracoModelsBuilderExtension\&ssr=false) and getting the error message Unauthorized when generating models? You'll need to use or create a backoffice user in your local installation. You then need to supply the credentials for this user in the Visual Studio options. This is necessary because the extension is not able to authenticate against Umbraco Id.
+Are using the [Visual Studio Extension for ModelsBuilder](https://marketplace.visualstudio.com/items?itemName=ZpqrtBnk.UmbracoModelsBuilderExtension\&ssr=false) and getting the error message Unauthorized when generating models? You'll need to use or create a backoffice user in your local installation. You then need to supply the credentials for this user in the Visual Studio options. This is necessary because the extension is not able to authenticate against Umbraco ID.
 {% endhint %}
 
 ### Using Umbraco namespaces in your `*.Core` project

umbraco-cloud/build-and-customize-your-solution/set-up-your-project/databases/backups.md

@@ -90,7 +90,7 @@ When an upload fails, you can click the triangle icon to view more details about
 | ------------------------- | -------------------------------------------- |
 | ImportBackupAborted       | User aborted the upload.                     |
 | ImportBackupFailedUnknown | An unknown error occurred during the upload. |
-| ImportBackupFailed        | Upoload took too long.                       |
+| ImportBackupFailed        | Upload took too long.                       |
 
 ## Restore Database
 

umbraco-cloud/build-and-customize-your-solution/set-up-your-project/databases/cloud-database/README.md

@@ -81,6 +81,6 @@ and in one of these folders for IIS Express:
 
 If you're using Visual Studio 2015+ check this path: `$(solutionDir)\.vs\config\applicationhost.config`
 
-In Visual Studio 2015+ you can also configure which `applicationhost.config` file is used by altering the `<UseGlobalApplicationHostFile>true|false</UseGlobalApplicationHostFile>` setting in the project file (eg: `MyProject.csproj`). Source: Microsoft Developer Network (MSDN) forum.
+In Visual Studio 2015+ you can also configure which `applicationhost.config` file is used by altering the `<UseGlobalApplicationHostFile>true|false</UseGlobalApplicationHostFile>` setting in the project file (for example, `MyProject.csproj`). Source: Microsoft Developer Network (MSDN) forum.
 
 Now that you are all set and ready you can continue to work with your [database locally](local-database.md).

umbraco-cloud/build-and-customize-your-solution/set-up-your-project/project-settings/config-transforms.md

@@ -32,7 +32,7 @@ You can find and manage the value of the `DOTNET_ENVIRONMENT` environment variab
 
 Create the files in your local project clone to ensure it's added to the repository.
 
-When the file is deployed to the Live environment, the transforms will be applied to the `appSettings.json` file in the `Root` of your project. In the case that you have mutliple mainline environments, the `appSettings.Live.json` will **only** transform the `appSettings.json` on the Live environment.
+When the file is deployed to the Live environment, the transforms will be applied to the `appSettings.json` file in the `Root` of your project. In the case that you have multiple mainline environments, the `appSettings.Live.json` will **only** transform the `appSettings.json` on the Live environment.
 
 {% hint style="info" %}
 If you don't have a web.config you will need to create one locally as well.