diff --git a/13/umbraco-cms/extending/health-check/README.md b/13/umbraco-cms/extending/health-check/README.md
index e961e261910..b7b89324b43 100644
--- a/13/umbraco-cms/extending/health-check/README.md
+++ b/13/umbraco-cms/extending/health-check/README.md
@@ -279,7 +279,7 @@ Disallow: /umbraco/";
## Custom health check notifications
-Health check notifications can be scheduled to run periodically and notify you of the results. Included with Umbraco is a notification method to deliver the results via email. In a similar manner to how it's possible to create your health checks, you can also create custom notification methods. These methods can send the message summarizing the status of the health checks via other means. Again, for further details on implementing this please refer to the [existing notification methods within the core code base](https://github.com/umbraco/Umbraco-CMS/tree/v10/dev/src/Umbraco.Core/HealthChecks/NotificationMethods).
+Health check notifications can be scheduled to run periodically and notify you of the results. Included with Umbraco is a notification method to deliver the results via email. In a similar manner to how it's possible to create your health checks, you can also create custom notification methods. These methods can send the message summarizing the status of the health checks via other means. Again, for further details on implementing this, refer to the [existing notification methods within the core code base](https://github.com/umbraco/Umbraco-CMS/tree/v10/dev/src/Umbraco.Core/HealthChecks/NotificationMethods).
Each notification method needs to implement the core interface `IHealthCheckNotificationMethod` and, for ease of creation, can inherit from the base class `NotificationMethodBase`, which itself implements the `IHealthCheckNotificationMethod` interface. The class must also be decorated with an instance of the `HealthCheckNotificationMethod` attribute. There's one method to implement - `SendAsync(HealthCheckResults results)`. This method is responsible for taking the results of the health checks and sending them via the mechanism of your choice.
diff --git a/13/umbraco-cms/extending/section-trees/trees/tree-actions.md b/13/umbraco-cms/extending/section-trees/trees/tree-actions.md
index cdd408a351c..3f96e76ef46 100644
--- a/13/umbraco-cms/extending/section-trees/trees/tree-actions.md
+++ b/13/umbraco-cms/extending/section-trees/trees/tree-actions.md
@@ -53,7 +53,7 @@ Here is a list of the tree actions and associated user permission codes shipped
If building a package or adding custom tree actions to your solution, it's important to pick a permission letter that doesn't clash with one of these.
-If you have created a package using a custom tree action, please consider providing an update to this documentation page via a PR to the [documentation repository](https://github.com/umbraco/UmbracoDocs), such that other developers can discover and avoid using the same permission letter.
+If you have created a package using a custom tree action, consider providing an update to this documentation page via a PR to the [documentation repository](https://github.com/umbraco/UmbracoDocs), such that other developers can discover and avoid using the same permission letter.
| Type | Alias | Letter | Can Be Permission Assigned |
| ------------------------------------------------------------- | ---------------------- | ------ | -------------------------- |
diff --git a/13/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/block-editor/block-list-editor.md b/13/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/block-editor/block-list-editor.md
index 99641a24d3d..733facef478 100644
--- a/13/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/block-editor/block-list-editor.md
+++ b/13/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/block-editor/block-list-editor.md
@@ -135,7 +135,7 @@ These partial views must be placed in this folder: `Views/Partials/BlockList/Com
A Partial View will receive the model of `Umbraco.Core.Models.Blocks.BlockListItem`. This gives you the option to access properties of the Content and Settings section of your Block.
-In the following example of a Partial view for a Block Type, please note that the `MyElementTypeAliasOfContent`and `MyElementTypeAliasOfSettings` should correspond with the selected Element Type Alias for the given model in your case.
+In the following example of a Partial view for a Block Type, the `MyElementTypeAliasOfContent`and `MyElementTypeAliasOfSettings` should correspond with the selected Element Type Alias for the given model in your case.
Example:
diff --git a/13/umbraco-cms/fundamentals/design/stylesheets-javascript.md b/13/umbraco-cms/fundamentals/design/stylesheets-javascript.md
index 337bdc38516..b35883f4be4 100644
--- a/13/umbraco-cms/fundamentals/design/stylesheets-javascript.md
+++ b/13/umbraco-cms/fundamentals/design/stylesheets-javascript.md
@@ -48,7 +48,7 @@ or
With the stylesheet referenced, you will be able to style the template file with the rules and classes defined in the stylesheet.
-Your stylesheets can be used in Rich Text Editors (datatype) as well - please see the [Rich Text Editor](../backoffice/property-editors/built-in-umbraco-property-editors/rich-text-editor/#rte-styles) documentation for more information.
+Your stylesheets can be used in Rich Text Editors (datatype) as well. See the [Rich Text Editor](../backoffice/property-editors/built-in-umbraco-property-editors/rich-text-editor/#rte-styles) documentation for more information.
{% hint style="info" %}
If your RTE is styled differently on the frontend of the site, the backoffice styling might be getting overwritten by other stylesheets you have included.
diff --git a/13/umbraco-cms/reference/angular/services/eventsservice/README.md b/13/umbraco-cms/reference/angular/services/eventsservice/README.md
index ba7b39da677..b7205169d0d 100644
--- a/13/umbraco-cms/reference/angular/services/eventsservice/README.md
+++ b/13/umbraco-cms/reference/angular/services/eventsservice/README.md
@@ -76,7 +76,7 @@ Alternatively, we could replace `unsubscribe()` with `eventsService.unsubscribe(
## Events in Umbraco
-Below you'll find a list of events broadcasted by the Umbraco codebase. The list may not be complete, so please help updating the list should you find an event that isn't listed.
+Below you'll find a list of events broadcasted by the Umbraco codebase. The list may not be complete, so kindly help updating the list should you find an event that isn't listed.
### Umbraco application
diff --git a/13/umbraco-cms/reference/content-delivery-api/additional-preview-environments-support.md b/13/umbraco-cms/reference/content-delivery-api/additional-preview-environments-support.md
index d4ab2385c8d..975d1dbdc80 100644
--- a/13/umbraco-cms/reference/content-delivery-api/additional-preview-environments-support.md
+++ b/13/umbraco-cms/reference/content-delivery-api/additional-preview-environments-support.md
@@ -8,7 +8,7 @@ description: >-
With Umbraco, you can save and preview draft content before going live. The preview feature allows you to visualize how a page will look once it is published, directly from within the backoffice. This is also possible for the Content Delivery API data. You can extend the preview functionality in the backoffice by configuring external preview URLs for client libraries consuming the Content Delivery API.
{% hint style="info" %}
-To get familiar with the preview functionality in the Delivery API, please refer to the [Preview concept](https://docs.umbraco.com/umbraco-cms/reference/content-delivery-api#preview) section.
+To get familiar with the preview functionality in the Delivery API, refer to the [Preview concept](https://docs.umbraco.com/umbraco-cms/reference/content-delivery-api#preview) section.
{% endhint %}
{% hint style="info" %}
diff --git a/13/umbraco-cms/reference/content-delivery-api/custom-property-editors-support.md b/13/umbraco-cms/reference/content-delivery-api/custom-property-editors-support.md
index 23e9cad3416..b9905c4600a 100644
--- a/13/umbraco-cms/reference/content-delivery-api/custom-property-editors-support.md
+++ b/13/umbraco-cms/reference/content-delivery-api/custom-property-editors-support.md
@@ -14,7 +14,7 @@ In this article, we'll look into how you can work with the `IDeliveryApiProperty
The examples in this article revolve around the fictional `My.Custom.Picker` property editor. This property editor stores the key of a single content item and is backed by a property value converter.
-We will not dive into the details of creating a custom property editor for Umbraco in this article. If you need guidance on that, please refer to the [Creating a Property Editor](https://docs.umbraco.com/umbraco-cms/tutorials/creating-a-property-editor) and [Property Value Converters](https://docs.umbraco.com/umbraco-cms/extending/property-editors/property-value-converters) articles.
+We will not dive into the details of creating a custom property editor for Umbraco in this article. If you need guidance on that, refer to the [Creating a Property Editor](https://docs.umbraco.com/umbraco-cms/tutorials/creating-a-property-editor) and [Property Value Converters](https://docs.umbraco.com/umbraco-cms/extending/property-editors/property-value-converters) articles.
## Implementation
diff --git a/13/umbraco-cms/reference/content-delivery-api/extension-api-for-querying.md b/13/umbraco-cms/reference/content-delivery-api/extension-api-for-querying.md
index 5c3634ca917..678a51b0fb9 100644
--- a/13/umbraco-cms/reference/content-delivery-api/extension-api-for-querying.md
+++ b/13/umbraco-cms/reference/content-delivery-api/extension-api-for-querying.md
@@ -6,7 +6,7 @@ description: >-
# Extension API for querying
-The Delivery API allows you to retrieve multiple items by utilizing the `/umbraco/delivery/api/v2/content` endpoint. With the built-in query parameters, you have the flexibility to get any number of content nodes based on your needs. For a comprehensive list of supported query options, please refer to the [Endpoints](./#endpoints) section.
+The Delivery API allows you to retrieve multiple items by utilizing the `/umbraco/delivery/api/v2/content` endpoint. With the built-in query parameters, you have the flexibility to get any number of content nodes based on your needs. For a comprehensive list of supported query options, refer to the [Endpoints](./#endpoints) section.
For the query endpoint, we have created a new Examine index (_DeliveryApiContentIndex_) that facilitates fast retrieval of the desired content. This index ensures quick indexing and searching of data, with the possibility for future extensions.
diff --git a/13/umbraco-cms/reference/content-delivery-api/media-delivery-api.md b/13/umbraco-cms/reference/content-delivery-api/media-delivery-api.md
index 383466bfffd..ceba80233e0 100644
--- a/13/umbraco-cms/reference/content-delivery-api/media-delivery-api.md
+++ b/13/umbraco-cms/reference/content-delivery-api/media-delivery-api.md
@@ -4,7 +4,7 @@ description: Using the Media Delivery API.
# Media Delivery API
-The Media Delivery API allows for accessing the Umbraco media items in a headless manner. This API applies many of the same concepts as its content counterpart, although with fewer options. If you haven't already, please familiarize yourself with the [Content Delivery API](https://docs.umbraco.com/umbraco-cms/reference/content-delivery-api) before reading this article.
+The Media Delivery API allows for accessing the Umbraco media items in a headless manner. This API applies many of the same concepts as its content counterpart, although with fewer options. If you haven't already, familiarize yourself with the [Content Delivery API](https://docs.umbraco.com/umbraco-cms/reference/content-delivery-api) before reading this article.
{% hint style="info" %}
The Media Delivery API specification is created to mimic that of the Content Delivery API. However, the default implementation of this specification is limited and does not support the entire specification.
@@ -166,7 +166,7 @@ Returns single or multiple items.
{% swagger-parameter in="query" name="fetch" type="String" required="true" %}
Structural query string option (e.g. `ancestors`, `children`, `descendants`).
-**Please note:** The default API implementation only supports `children`.
+**Note:** The default API implementation only supports `children`.
{% endswagger-parameter %}
{% swagger-parameter in="query" name="filter" type="String Array" required="false" %}
diff --git a/13/umbraco-cms/reference/content-delivery-api/property-expansion-and-limiting.md b/13/umbraco-cms/reference/content-delivery-api/property-expansion-and-limiting.md
index 21bb3108cd3..7a0cab6dda9 100644
--- a/13/umbraco-cms/reference/content-delivery-api/property-expansion-and-limiting.md
+++ b/13/umbraco-cms/reference/content-delivery-api/property-expansion-and-limiting.md
@@ -5,7 +5,7 @@ description: Using property expansion and limiting to shape the Delivery API out
# Property expansion and limiting
{% hint style="info" %}
-This article explains the mechanics of property expansion and limiting in depth. If you haven't already, please read the [Getting started](https://docs.umbraco.com/umbraco-cms/reference/content-delivery-api) article first - in particular the "Concepts" section.
+This article explains the mechanics of property expansion and limiting in depth. If you haven't already, read the [Getting started](https://docs.umbraco.com/umbraco-cms/reference/content-delivery-api) article first - in particular the "Concepts" section.
{% endhint %}
Property expansion and limiting applies only to select property editors. The following built-in property editors in Umbraco support expansion and limiting:
@@ -537,7 +537,7 @@ Start-Item: posts
## Working with block-based editors
{% hint style="info" %}
-If you are not familiar with block-based editors, please refer to [this article](https://docs.umbraco.com/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/block-editor) for the general concepts of these.
+If you are not familiar with block-based editors, refer to [this article](https://docs.umbraco.com/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/block-editor) for the general concepts of these.
{% endhint %}
In the API output, a block has little value without its contained properties. Therefore, the content and settings properties of blocks are always included in the output. However, these properties are not expanded. As such, we can apply expansion and limiting to the contained properties.
diff --git a/13/umbraco-cms/reference/content-delivery-api/protected-content-in-the-delivery-api.md b/13/umbraco-cms/reference/content-delivery-api/protected-content-in-the-delivery-api.md
index 25ac8f73dd5..0793d2d227a 100644
--- a/13/umbraco-cms/reference/content-delivery-api/protected-content-in-the-delivery-api.md
+++ b/13/umbraco-cms/reference/content-delivery-api/protected-content-in-the-delivery-api.md
@@ -13,7 +13,7 @@ Member authorization in the Delivery API was introduced in version 12.3.
{% endhint %}
{% hint style="info" %}
-If you are not familiar with members in Umbraco, please read the [Members](https://docs.umbraco.com/umbraco-cms/fundamentals/data/members) article.
+If you are not familiar with members in Umbraco, read the [Members](https://docs.umbraco.com/umbraco-cms/fundamentals/data/members) article.
{% endhint %}
{% hint style="warning" %}
@@ -358,7 +358,7 @@ Access tokens expire after one hour. Once expired, a new access token must be ob
Refresh tokens provide a means to obtain a new access token without having to go through the authentication flow. A refresh token is issued automatically by the Delivery API when the `offline_access` scope is specified in the authorization request.
{% hint style="info" %}
-Refresh tokens are subject to certain limitations and can result in security issues if not applied correctly. All this is beyond the scope of this article to explain in detail. Please familiarize yourself with the inner workings of refresh tokens before applying them in a solution.
+Refresh tokens are subject to certain limitations and can result in security issues if not applied correctly. All this is beyond the scope of this article to explain in detail. Familiarize yourself with the inner workings of refresh tokens before applying them in a solution.
{% endhint %}
## Logging out members
@@ -446,7 +446,7 @@ Remember to use `umbraco-member` as `client_id` when authorizing. `client_secret
The following samples show how to configure an ASP.NET Core client to utilize member authorization in the Delivery API.
-To put these samples into context, please refer to the article above.
+To put these samples into context, refer to the article above.
### Basic client configuration
diff --git a/13/umbraco-cms/reference/management/models/contenttype.md b/13/umbraco-cms/reference/management/models/contenttype.md
index 9fa7fc0f9a5..e689118d265 100644
--- a/13/umbraco-cms/reference/management/models/contenttype.md
+++ b/13/umbraco-cms/reference/management/models/contenttype.md
@@ -82,7 +82,7 @@ return contentType.AllowedTemplates;
Gets a list of `ContentTypes` as `IContentTypeComposition` objects that make up a composition of PropertyGroups and PropertyTypes for the current ContentType.
-The ContentTypeComposition provides a mixin-type functionality in that you can compose a ContentType of one or more other ContentTypes in a complex structure. But please be aware that the backoffice does not fully support these complex structures yet.
+The ContentTypeComposition provides a mixin-type functionality in that you can compose a ContentType of one or more other ContentTypes in a complex structure. But be aware that the backoffice does not fully support these complex structures yet.
```csharp
// Given a `ContentTypeService` object get ContentType by its Id and return ContentTypeComposition
diff --git a/13/umbraco-cms/reference/management/models/mediatype.md b/13/umbraco-cms/reference/management/models/mediatype.md
index 8a730821652..ba08e55edb5 100644
--- a/13/umbraco-cms/reference/management/models/mediatype.md
+++ b/13/umbraco-cms/reference/management/models/mediatype.md
@@ -66,7 +66,7 @@ return mediaType.AllowedContentTypes;
Gets a list of `MediaTypes` as `IContentTypeComposition` objects that make up a composition of PropertyGroups and PropertyTypes for the current MediaType.
-The `ContentTypeComposition` provides a mixin-type functionality in that you can compose a MediaType of one or more other MediaTypes in a complex structure. But please keep in mind that the backoffice does not fully support these complex structures yet
+The `ContentTypeComposition` provides a mixin-type functionality in that you can compose a MediaType of one or more other MediaTypes in a complex structure. But keep in mind that the backoffice does not fully support these complex structures yet
```csharp
// Given a `MediaTypeService` object get MediaType by its Id and return ContentTypeComposition
diff --git a/13/umbraco-cms/reference/searching/examine/indexing.md b/13/umbraco-cms/reference/searching/examine/indexing.md
index 87ef10c1176..d8869047720 100644
--- a/13/umbraco-cms/reference/searching/examine/indexing.md
+++ b/13/umbraco-cms/reference/searching/examine/indexing.md
@@ -329,7 +329,7 @@ The index will only update its content when you manually trigger an index rebuil
To update your index when content changes, you can use notification handlers.
{% hint style="info" %}
-The following handler class does not automatically update the descendant items of the modified content nodes, such as removing descendants of deleted content. If changes to the parent content item can affect its children or descendant items in your setup, please refer to the [UmbracoContentIndex.PerformDeleteFromIndex() in Umbraco](https://github.com/umbraco/Umbraco-CMS/blob/main/src/Umbraco.Examine.Lucene/UmbracoContentIndex.cs#L124-L153). Such logic should be applied when both removing and reindexing content items of type _product_.
+The following handler class does not automatically update the descendant items of the modified content nodes, such as removing descendants of deleted content. If changes to the parent content item can affect its children or descendant items in your setup, refer to the [UmbracoContentIndex.PerformDeleteFromIndex() in Umbraco](https://github.com/umbraco/Umbraco-CMS/blob/main/src/Umbraco.Examine.Lucene/UmbracoContentIndex.cs#L124-L153). Such logic should be applied when both removing and reindexing content items of type _product_.
{% endhint %}
```csharp
diff --git a/13/umbraco-cms/tutorials/creating-a-basic-website/README.md b/13/umbraco-cms/tutorials/creating-a-basic-website/README.md
index 4e2c531a7f7..020a7ba2499 100644
--- a/13/umbraco-cms/tutorials/creating-a-basic-website/README.md
+++ b/13/umbraco-cms/tutorials/creating-a-basic-website/README.md
@@ -15,7 +15,7 @@ It is recommended that you work through the subsections in the following order.
## [Getting Started](getting-started.md)
-To follow this tutorial please work through this section first.
+To follow this tutorial, work through this section first.
## [Creating Your First Document Type](document-types.md)
diff --git a/13/umbraco-cms/tutorials/creating-a-custom-dashboard/README.md b/13/umbraco-cms/tutorials/creating-a-custom-dashboard/README.md
index 6e7c9ed39a1..809e14337e8 100644
--- a/13/umbraco-cms/tutorials/creating-a-custom-dashboard/README.md
+++ b/13/umbraco-cms/tutorials/creating-a-custom-dashboard/README.md
@@ -37,7 +37,7 @@ At the end of this guide, we should have a friendly welcoming dashboard displayi
```html
Welcome to Umbraco
-
We hope you find the experience of editing your content with Umbraco enjoyable and delightful. If you discover any problems with the site please report them to the support team at support@popularumbracopartner.com
+
We hope you find the experience of editing your content with Umbraco enjoyable and delightful. If you discover any problems with the site, report them to the support team at support@popularumbracopartner.com
You can put anything here...
```
diff --git a/13/umbraco-cms/tutorials/editors-manual/tips-and-tricks/notifications.md b/13/umbraco-cms/tutorials/editors-manual/tips-and-tricks/notifications.md
index 9967e3fe54c..7040d775ec1 100644
--- a/13/umbraco-cms/tutorials/editors-manual/tips-and-tricks/notifications.md
+++ b/13/umbraco-cms/tutorials/editors-manual/tips-and-tricks/notifications.md
@@ -18,5 +18,5 @@ The notification settings apply to the chosen content item as well as any child
{% endhint %}
{% hint style="info" %}
-If the notifications option does not appear, the SMTP settings are probably incorrect. In this case please contact the administrator of your website.
+If the notifications option does not appear, the SMTP settings are probably incorrect. In this case, contact the administrator of your website.
{% endhint %}
diff --git a/13/umbraco-cms/tutorials/multisite-setup.md b/13/umbraco-cms/tutorials/multisite-setup.md
index 1aeb2a9cb77..6efe68988e1 100644
--- a/13/umbraco-cms/tutorials/multisite-setup.md
+++ b/13/umbraco-cms/tutorials/multisite-setup.md
@@ -10,7 +10,7 @@ This tutorial explains how to host multiple sites from one project/installation
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.
{% endhint %}
-If you are planning to create a multilingual site, please take a look at the [Multilanguage Setup](multilanguage-setup.md) tutorial instead.
+If you are planning to create a multilingual site, take a look at the [Multilanguage Setup](multilanguage-setup.md) tutorial instead.
## Structuring your website
diff --git a/13/umbraco-commerce/changelog-archive/Vendr-core.md b/13/umbraco-commerce/changelog-archive/Vendr-core.md
index 2de685aae2f..921b48375ee 100644
--- a/13/umbraco-commerce/changelog-archive/Vendr-core.md
+++ b/13/umbraco-commerce/changelog-archive/Vendr-core.md
@@ -556,10 +556,10 @@ description: Changelog for the Core Vendr product
## v1.4.0
-**Date:** 2020-12-10\
+**Date:** 2020-12-10
**Description:** Major breaking changes release
-For more details on this release, including a recommended upgrade strategy, please see the [Vendr 1.4.0 RC blog post](https://vendr.net/blog/vendr-1-4-0-release-candidate/).
+For more details on this release, including a recommended upgrade strategy, see the [Vendr 1.4.0 RC blog post](https://vendr.net/blog/vendr-1-4-0-release-candidate/).
* Added price adjustments/adjusters.
* Added amount adjustments/adjusters.
diff --git a/13/umbraco-deploy/extending/handling-cache-refresher-notifications.md b/13/umbraco-deploy/extending/handling-cache-refresher-notifications.md
index 4568be36f3a..155c1bdb382 100644
--- a/13/umbraco-deploy/extending/handling-cache-refresher-notifications.md
+++ b/13/umbraco-deploy/extending/handling-cache-refresher-notifications.md
@@ -27,7 +27,7 @@ The following two code samples illustrate how this can be done.
The first handles a content cache refresher, which takes a payload from where the content ID can be extracted. Using that the content can be retrieved in the local Umbraco instance and used as appropriate.
-For more details and further examples, please see the [CMS Cache Refresher Notifications documentation](https://docs.umbraco.com/umbraco-cms/reference/notifications/cacherefresher-notifications).
+For more details and further examples, see the [CMS Cache Refresher Notifications documentation](https://docs.umbraco.com/umbraco-cms/reference/notifications/cacherefresher-notifications).
```csharp
using Umbraco.Cms.Core.Cache;
diff --git a/13/umbraco-deploy/troubleshooting.md b/13/umbraco-deploy/troubleshooting.md
index ab73bb3be04..861c86b0ef2 100644
--- a/13/umbraco-deploy/troubleshooting.md
+++ b/13/umbraco-deploy/troubleshooting.md
@@ -6,7 +6,7 @@ description: The troubleshooting section for Umbraco Deploy
In this troubleshooting section, you can find help to resolve issues that you might run into when using Umbraco Deploy.
-If you are unable to find the issue you are having, then please reach out to our friendly support team at contact@umbraco.com.
+If you are unable to find the issue you are having, then reach out to our friendly support team at contact@umbraco.com.
## Schema mismatches
diff --git a/13/umbraco-engage/developers/analytics/client-side-events-and-additional-javascript-files/bridging-library-for-google-analytics.md b/13/umbraco-engage/developers/analytics/client-side-events-and-additional-javascript-files/bridging-library-for-google-analytics.md
index 2aca9afb5de..bf92135f530 100644
--- a/13/umbraco-engage/developers/analytics/client-side-events-and-additional-javascript-files/bridging-library-for-google-analytics.md
+++ b/13/umbraco-engage/developers/analytics/client-side-events-and-additional-javascript-files/bridging-library-for-google-analytics.md
@@ -65,7 +65,7 @@ The captured GA4 events will appear in Analytics -> Events in the **GA 4 - Bridg
### Using GA4 events in Goals
-If you want to trigger a goal based on a GA4 event please use the following information:
+If you want to trigger a goal based on a GA4 event, use the following information:
-Category: **GA 4 Bridging**\
+Category: **GA 4 Bridging**
Action: **\**
diff --git a/13/umbraco-engage/installation/installation.md b/13/umbraco-engage/installation/installation.md
index 7f41fbd50f6..6de1d34f87e 100644
--- a/13/umbraco-engage/installation/installation.md
+++ b/13/umbraco-engage/installation/installation.md
@@ -57,7 +57,7 @@ dotnet add package Umbraco.Engage
```
{% hint style="info" %}
-If you have any trouble, please go to [Troubleshooting installs](troubleshooting-installs.md).
+If you have any trouble, go to [Troubleshooting installs](troubleshooting-installs.md).
{% endhint %}
## Next steps
@@ -134,7 +134,7 @@ The following Google Analytics bridging or blocker script loading types are curr
### Cookie consent
-If you need to influence the default [The Umbraco Engage cookie](../marketers-and-editors/introduction/the-umbraco-engage-cookie.md) behaviour please go [here](../security-and-privacy/gdpr/). Or go to an example [implementation using Cookiebot](../security-and-privacy/gdpr/how-to-become-gdpr-compliant-using-cookiebot.md) which can be used as an example for other cookie consent providers.
+If you need to influence the default [The Umbraco Engage cookie](../marketers-and-editors/introduction/the-umbraco-engage-cookie.md) behaviour, go [here](../security-and-privacy/gdpr/). Or go to an example [implementation using Cookiebot](../security-and-privacy/gdpr/how-to-become-gdpr-compliant-using-cookiebot.md) which can be used as an example for other cookie consent providers.
{% hint style="warning" %}
If you [change the default cookie behaviour](../developers/introduction/the-umbraco-engage-cookie/) make sure to perform a **client side reload of the initial page after cookie consent**. If this is not done, visitor referrer and/or campaigns will not be tracked.
diff --git a/13/umbraco-engage/installation/troubleshooting-installs.md b/13/umbraco-engage/installation/troubleshooting-installs.md
index c2d94ed0821..be4243c633e 100644
--- a/13/umbraco-engage/installation/troubleshooting-installs.md
+++ b/13/umbraco-engage/installation/troubleshooting-installs.md
@@ -12,7 +12,7 @@ If you have problems with Umbraco Engage setup or configuration, this checklist
After logging in to Umbraco, you can see the Engage section next to the other main sections in the Umbraco backoffice.
-If you cannot see this, please check if your Umbraco user or user group has access to the Engage section.
+If you cannot see this, check if your Umbraco user or user group has access to the Engage section.

@@ -22,7 +22,7 @@ When editing a page within Umbraco, you should be able to see the following Cont

-If you cannot see this, please check if your Umbraco user or user group has access to the Engage section.
+If you cannot see this, check if your Umbraco user or user group has access to the Engage section.
### 3. Cockpit
@@ -83,7 +83,7 @@ To ensure that Umbraco Engage can interact with the visitor from the first page,
### Still missing analytical data?
-If you have performed all the steps and do not see Analytics data within Umbraco Engage there are a handful of additional steps to take. Please work with a developer to check the following technical steps.
+If you have performed all the steps and do not see Analytics data within Umbraco Engage there are a handful of additional steps to take. Work with a developer to check the following technical steps.
* Open your website in a browser with the browser developer tools open.
* Refresh the page while the developer tools are open.
diff --git a/13/umbraco-engage/marketers-and-editors/settings/setting-up-goals.md b/13/umbraco-engage/marketers-and-editors/settings/setting-up-goals.md
index 62a73648e8d..4c49a071ce1 100644
--- a/13/umbraco-engage/marketers-and-editors/settings/setting-up-goals.md
+++ b/13/umbraco-engage/marketers-and-editors/settings/setting-up-goals.md
@@ -35,9 +35,9 @@ You can specify how the goal will be triggered:
* Via a pageview/set of pages that are visited
* Via a page event that can be triggered
- * If you want to trigger a goal based on a GA4 event please use the following information:
+ * If you want to trigger a goal based on a GA4 event, use the following information:
- Category: **GA 4 Bridging**\
+ Category: **GA 4 Bridging**
Action: **\**
* Via an Umbraco Forms submission
* Via some custom code
diff --git a/13/umbraco-engage/upgrading/migrate-from-umarketingsuite.md b/13/umbraco-engage/upgrading/migrate-from-umarketingsuite.md
index d34aa4a97ff..64f7156870c 100644
--- a/13/umbraco-engage/upgrading/migrate-from-umarketingsuite.md
+++ b/13/umbraco-engage/upgrading/migrate-from-umarketingsuite.md
@@ -49,7 +49,7 @@ Run this script on your locally restored database to prepare for the migration.
3. Verify that the uMarketingSuite table integrity check returns the expected results.
{% hint style="info" %}
-If any of these checks return a failure, please resolve the issue before proceeding with the migration.
+If any of these checks return a failure, resolve the issue before proceeding with the migration.
{% endhint %}
The result should look like this:
@@ -65,7 +65,7 @@ The result should look like this:
---Finished running Pre-Requisite Checks. Please verify if all 5 checks succeeded before proceeding---
```
-If any of these checks return a failure, please resolve the issue before proceeding with the migration.
+If any of these checks return a failure, resolve the issue before proceeding with the migration.
## Step 3: Replace NuGet packages and dependencies
@@ -125,7 +125,7 @@ dotnet add package Umbraco.Engage.Commerce
Based on the [Key Changes](migrate-from-umarketingsuite.md#key-changes) below update all uMarketingSuite references to the new Umbraco Engage alternatives. Ensure you update any Views/Partials that also reference these. This includes the different uMarketingSuite clientside scripts (like the analytics & ga4-bridge) and the Cockpit.
-Please find below an overview of the changes to the default scripts in a uMarketingSuite installation:
+Find below an overview of the changes to the default scripts in a uMarketingSuite installation:
* Rename scripts & Asset Paths containing the `uMarketingSuite` keyword to:
* `Assets/Umbraco.Engage/Scripts/umbracoEngage.analytics.js`
@@ -133,7 +133,7 @@ Please find below an overview of the changes to the default scripts in a uMarket
* `Assets/Umbraco.Engage/Scripts/umbracoEngage.analytics.blockerdetection.js`
* The Cockpit partial view has been moved, and any references should be changed to:
* `Partials/Umbraco.Engage/Cockpit`
-* If you are tracking custom events please make sure to update the calls to the send event method:
+* If you are tracking custom events, make sure to update the calls to the send event method:
* `ums("send", "event", "", "", "")`
is now:
@@ -362,7 +362,7 @@ dotnet add package Umbraco.Engage.Forms
If you are using the uMarketingSuite.Headless package, applications that use the uMarketingSuite API will need to be updated. This needs to happen to be able to use the new Umbraco Engage API, accessible via the `/umbraco/engage/api/` routes.
-The v1 Engage APIs (v13.0.0 of Umbraco Engage) maintain the same functionality as the v1 uMarketingSuite APIs. For more details on the API, please refer to the Swagger documentation provided by Umbraco Engage.
+The v1 Engage APIs (v13.0.0 of Umbraco Engage) maintain the same functionality as the v1 uMarketingSuite APIs. For more details on the API, refer to the Swagger documentation provided by Umbraco Engage.
You can install the Umbraco Engage Headless add-on package using the following command:
diff --git a/13/umbraco-forms/developer/ajaxforms.md b/13/umbraco-forms/developer/ajaxforms.md
index a017fbb5eeb..bc7ab7953c9 100644
--- a/13/umbraco-forms/developer/ajaxforms.md
+++ b/13/umbraco-forms/developer/ajaxforms.md
@@ -538,7 +538,7 @@ With this in place any request to the Forms API will be rejected unless the conf
## Rendering and Submitting forms with JavaScript
-For an illustrative example showing how a form can be rendered, validated and submitted using the API and vanilla JavaScript, please [see this gist](https://gist.github.com/AndyButland/9371175d6acf24a5307b053398f08448).
+For an illustrative example showing how a form can be rendered, validated and submitted using the API and vanilla JavaScript, [see this gist](https://gist.github.com/AndyButland/9371175d6acf24a5307b053398f08448).
Examples demonstrating how to handle a file upload and use reCAPTCHA fields are included.
diff --git a/13/umbraco-forms/developer/healthchecks/README.md b/13/umbraco-forms/developer/healthchecks/README.md
index 5786234aaa3..0154165c70e 100644
--- a/13/umbraco-forms/developer/healthchecks/README.md
+++ b/13/umbraco-forms/developer/healthchecks/README.md
@@ -53,7 +53,7 @@ To support this, we provide the following SQL scripts:
The first of these provides the SQL statements required to apply the schema updates for 8.7.0+ to the common Umbraco Forms tables. The second applies to those tables used for when Forms are stored in the database, and hence only need to be applied if that option is configured.
{% hint style="info" %}
-Before running any scripts or queries, please be sure to have a database backup in place.
+Before running any scripts or queries, be sure to have a database backup in place.
{% endhint %}
To take an example, let's say that via the health check results you can see that the _"Unique constraint on table 'UFForms', column 'Key' is missing."_
diff --git a/13/umbraco-forms/developer/prepping-frontend.md b/13/umbraco-forms/developer/prepping-frontend.md
index a49faddfd31..800fb515943 100644
--- a/13/umbraco-forms/developer/prepping-frontend.md
+++ b/13/umbraco-forms/developer/prepping-frontend.md
@@ -41,7 +41,7 @@ You can use this to apply `async` or `defer` attributes. For example:
@Html.RenderUmbracoFormDependencies(Url, new { @async = "async" })
```
-If using `async`, please make sure to [disable the Forms client-side validation framework check](../developer/configuration/README.md#disableclientsidevalidationdependencycheck). This is necessary as it's not possible to guarantee that the asynchronous script will load in time to be recognized by the check. This can then cause a false positive warning.
+If using `async`, make sure to [disable the Forms client-side validation framework check](../developer/configuration/README.md#disableclientsidevalidationdependencycheck). This is necessary as it's not possible to guarantee that the asynchronous script will load in time to be recognized by the check. This can then cause a false positive warning.
## Validation Using jQuery
diff --git a/13/umbraco-forms/installation/the-licensing-model.md b/13/umbraco-forms/installation/the-licensing-model.md
index 431e8257317..22d437c9c11 100644
--- a/13/umbraco-forms/installation/the-licensing-model.md
+++ b/13/umbraco-forms/installation/the-licensing-model.md
@@ -104,7 +104,7 @@ This will also change the location for other Umbraco-related licenses in this pr
The algorithm used to decrypt Forms licenses is not supported on locked down FIPS compliant environments, such as those used in the defense industry.
-If you are in this situation and unable to resolve it via configuration of the environment, please reach out to Umbraco support.
+If you are in this situation and unable to resolve it via configuration of the environment, reach out to Umbraco Support.
We have the possibility of generating and providing Forms licenses using alternate algorithms.
diff --git a/15/umbraco-cms/customizing/development-flow/typescript-setup.md b/15/umbraco-cms/customizing/development-flow/typescript-setup.md
index 3113b51d9bf..f331c82d85c 100644
--- a/15/umbraco-cms/customizing/development-flow/typescript-setup.md
+++ b/15/umbraco-cms/customizing/development-flow/typescript-setup.md
@@ -1,6 +1,6 @@
# TypeScript setup
-Make sure to configure your TypeScript compiler so it includes the Global Types from the Backoffice. This enables you to utilize the declared Extension Types. If your project is using other Packages that provides their Extension Types then please list these as well.
+Make sure to configure your TypeScript compiler so it includes the Global Types from the Backoffice. This enables you to utilize the declared Extension Types. If your project is using other Packages that provides their Extension Types, kindly list them as well.
In your `tsconfig.json` file. Add the array `types` inside `compilerOptions`, with the entry of `@umbraco-cms/backoffice/extension-types`:
diff --git a/15/umbraco-cms/customizing/extending-overview/extension-registry/replace-exclude-or-unregister.md b/15/umbraco-cms/customizing/extending-overview/extension-registry/replace-exclude-or-unregister.md
index 0fded461712..3c138f8cc90 100644
--- a/15/umbraco-cms/customizing/extending-overview/extension-registry/replace-exclude-or-unregister.md
+++ b/15/umbraco-cms/customizing/extending-overview/extension-registry/replace-exclude-or-unregister.md
@@ -54,7 +54,7 @@ UmbExtensionRegistry.exclude('Umb.WorkspaceAction.Document.SaveAndPreview');
## Unregister
-You can also choose to unregister an extension, this is only preferred if you registered the extension and are in control of the flow. If it's not your Extension please seek to use the `Overwrites` or `Exclude` feature.
+You can also choose to unregister an extension, this is only preferred if you registered the extension and are in control of the flow. If it's not your Extension, seek to use the `Overwrites` or `Exclude` feature.
```typescript
import { umbExtensionsRegistry } from '@umbraco-cms/backoffice/extension-registry';
diff --git a/15/umbraco-cms/customizing/extending-overview/extension-types/entity-actions.md b/15/umbraco-cms/customizing/extending-overview/extension-types/entity-actions.md
index 2554b0a6cac..9408aaad8c4 100644
--- a/15/umbraco-cms/customizing/extending-overview/extension-types/entity-actions.md
+++ b/15/umbraco-cms/customizing/extending-overview/extension-types/entity-actions.md
@@ -147,7 +147,7 @@ Here is a list of the entity actions and associated user permission codes shippe
If you are building a package or adding custom entity actions to your solution, it's important to pick a permission letter. Ensure that it doesn't clash with one of these.
-If you have created a package using a custom entity action, please consider providing an update to this documentation page. You can do this via a PR to the [documentation repository](https://github.com/umbraco/UmbracoDocs). This will allow other developers to discover and avoid using the same permission letter.
+If you have created a package using a custom entity action, consider providing an update to this documentation page. You can do this via a PR to the [documentation repository](https://github.com/umbraco/UmbracoDocs). This will allow other developers to discover and avoid using the same permission letter.
Currently, we allow two extension points on the client for user permissions:
diff --git a/15/umbraco-cms/extending/health-check/README.md b/15/umbraco-cms/extending/health-check/README.md
index 75f784091d4..a0bbadc9b97 100644
--- a/15/umbraco-cms/extending/health-check/README.md
+++ b/15/umbraco-cms/extending/health-check/README.md
@@ -187,7 +187,7 @@ Disallow: /umbraco/";
## Custom health check notifications
-Health check notifications can be scheduled to run periodically and notify you of the results. Included with Umbraco is a notification method to deliver the results via email. In a similar manner to how it's possible to create your health checks, you can also create custom notification methods to send the message summarising the status of the health checks via other means. Again, for further details on implementing this please refer to the [existing notification methods within the core code base](https://github.com/umbraco/Umbraco-CMS/tree/v10/dev/src/Umbraco.Core/HealthChecks/NotificationMethods).
+Health check notifications can be scheduled to run periodically and notify you of the results. Included with Umbraco is a notification method to deliver the results via email. In a similar manner to how it's possible to create your health checks, you can also create custom notification methods to send the message summarising the status of the health checks via other means. Again, for further details on implementing this, refer to the [existing notification methods within the core code base](https://github.com/umbraco/Umbraco-CMS/tree/v10/dev/src/Umbraco.Core/HealthChecks/NotificationMethods).
Each notification method needs to implement the core interface `IHealthCheckNotificationMethod` and, for ease of creation, can inherit from the base class `NotificationMethodBase`, which itself implements the `IHealthCheckNotificationMethod` interface. The class must also be decorated with an instance of the `HealthCheckNotificationMethod` attribute. There's one method to implement - `SendAsync(HealthCheckResults results)` - which is responsible for taking the results of the health checks and sending them via the mechanism of your choice.
diff --git a/15/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/block-editor/block-list-editor.md b/15/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/block-editor/block-list-editor.md
index a89ab54d6ca..1ba245d5469 100644
--- a/15/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/block-editor/block-list-editor.md
+++ b/15/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/block-editor/block-list-editor.md
@@ -139,7 +139,7 @@ These partial views must be placed in this folder: `Views/Partials/BlockList/Com
A Partial View will receive the model of `Umbraco.Core.Models.Blocks.BlockListItem`. This gives you the option to access properties of the Content and Settings section of your Block.
-In the following example of a Partial view for a Block Type, please note that the `MyElementTypeAliasOfContent`and `MyElementTypeAliasOfSettings` should correspond with the selected Element Type Alias for the given model in your case.
+In the following example of a Partial view for a Block Type, the `MyElementTypeAliasOfContent`and `MyElementTypeAliasOfSettings` should correspond with the selected Element Type Alias for the given model in your case.
Example:
diff --git a/15/umbraco-cms/fundamentals/design/stylesheets-javascript.md b/15/umbraco-cms/fundamentals/design/stylesheets-javascript.md
index 2e0594b9635..cb806ea5671 100644
--- a/15/umbraco-cms/fundamentals/design/stylesheets-javascript.md
+++ b/15/umbraco-cms/fundamentals/design/stylesheets-javascript.md
@@ -46,7 +46,7 @@ or
With the stylesheet referenced, you will be able to style the template file with the rules and classes defined in the stylesheet.
-Your stylesheets can be used in Rich Text Editors (datatype) as well - please see the [Rich Text Editor](../backoffice/property-editors/built-in-umbraco-property-editors/rich-text-editor/#rte-styles) documentation for more information.
+Your stylesheets can be used in Rich Text Editors (datatype) as well. See the [Rich Text Editor](../backoffice/property-editors/built-in-umbraco-property-editors/rich-text-editor/#rte-styles) documentation for more information.
{% hint style="info" %}
If your RTE is styled differently on the frontend of the site, the backoffice styling might be getting overwritten by other stylesheets you have included.
diff --git a/15/umbraco-cms/fundamentals/setup/upgrading/version-specific/README.md b/15/umbraco-cms/fundamentals/setup/upgrading/version-specific/README.md
index c6f0289b89b..894fcb24791 100644
--- a/15/umbraco-cms/fundamentals/setup/upgrading/version-specific/README.md
+++ b/15/umbraco-cms/fundamentals/setup/upgrading/version-specific/README.md
@@ -76,7 +76,7 @@ Below you can find the list of breaking changes introduced in Umbraco 14 CMS.
* [**AngularJS removed: A new backoffice built with Web Components, Lit, and fueled by the Umbraco UI Library**](https://github.com/umbraco/Umbraco.CMS.Backoffice)
-This is by far the most impactful update of Umbraco in years. We’ve fundamentally changed the way you extend Umbraco. If you are experienced in developing Web Components you can now use your preferred framework for this. If you are unsure how to proceed, you can implement it with Typescript and the Lit library like we’ve done. In this case, please start with this article on how to [customize the Backoffice](https://docs.umbraco.com/umbraco-cms/customizing/overview).
+This is by far the most impactful update of Umbraco in years. We’ve fundamentally changed the way you extend Umbraco. If you are experienced in developing Web Components you can now use your preferred framework for this. If you are unsure how to proceed, you can implement it with Typescript and the Lit library like we’ve done. In this case, start with this article on how to [customize the Backoffice](https://docs.umbraco.com/umbraco-cms/customizing/overview).
The new Backoffice (Bellissima) is entirely built on the Umbraco UI Library. This means that you might experience some of your components not being rendered on the page because the name has been changed. You should be able to find equivalents to what you were used to. For example, the `umb-button` is now called `uui-button`, and `umb-box` is now `uui-box`. When extending the Backoffice, we encourage you to use our [Umbraco UI Library](https://uui.umbraco.com/) to ensure the same look and feel in your extensions. The UI Library is Open Source and [hosted on GitHub](https://github.com/umbraco/Umbraco.UI), so feel free to contribute with new components or raise issues or discussions.
@@ -100,7 +100,7 @@ Following the implementation of the new Backoffice (Bellissima), Umbraco has now
* **A new way of writing authorized controllers**
-If you have implemented API controllers in Umbraco before, we recommend you update or rewrite these. Please follow the [Documenting your Controllers](https://docs.umbraco.com/umbraco-cms/tutorials/creating-a-backoffice-api/documenting-your-controllers) article, as you’ll then ensure the same cool documentation of your APIs. Notice, that we’ve made a much better separation of concern between controllers and services so that there is no more business logic in controllers.
+If you have implemented API controllers in Umbraco before, we recommend you update or rewrite these. Follow the [Documenting your Controllers](https://docs.umbraco.com/umbraco-cms/tutorials/creating-a-backoffice-api/documenting-your-controllers) article, as you’ll then ensure the same cool documentation of your APIs. Notice, that we’ve made a much better separation of concern between controllers and services so that there is no more business logic in controllers.
* [**Migration from Newtonsoft.Json to the System.Text.Json which removes Nested Content and Grid value converter and so on**](https://github.com/umbraco/Umbraco-CMS/pull/15728)
@@ -133,7 +133,7 @@ The `package.manifest` file is no longer supported and has been replaced with th
It's recommended that you bundle up your Backoffice static assets for instance by a tool called Vite. You can read more about this on the [Vite Package Setup](https://docs.umbraco.com/umbraco-cms/customizing/development-flow/vite-package-setup) article. You can still use libraries like Smidge for frontend static assets by manually installing the package from NuGet.
You can read the [Smidge documentation](https://github.com/Shazwazza/Smidge/wiki) on how to set up a similar setting to RuntimeMinification.
-For sites being upgraded from V13 or below, please remove [these two lines](https://github.com/umbraco/Umbraco-CMS/blob/04ed514a21279ae82d95b34c55cb2ba96545eb39/src/Umbraco.Web.UI/Views/_ViewImports.cshtml#L7-L8) from the `_ViewImports.cshtml` file.
+For sites being upgraded from V13 or below, remove [these two lines](https://github.com/umbraco/Umbraco-CMS/blob/04ed514a21279ae82d95b34c55cb2ba96545eb39/src/Umbraco.Web.UI/Views/_ViewImports.cshtml#L7-L8) from the `_ViewImports.cshtml` file.
* **Base classes for Backoffice controllers have been removed**
diff --git a/15/umbraco-cms/reference/content-delivery-api/additional-preview-environments-support.md b/15/umbraco-cms/reference/content-delivery-api/additional-preview-environments-support.md
index 72363a78aa3..c1809ab24c2 100644
--- a/15/umbraco-cms/reference/content-delivery-api/additional-preview-environments-support.md
+++ b/15/umbraco-cms/reference/content-delivery-api/additional-preview-environments-support.md
@@ -12,7 +12,7 @@ The contents of this article have not yet been verified or updated for Umbraco 1
With Umbraco, you can save and preview draft content before going live. The preview feature allows you to visualize how a page will look once it is published, directly from within the backoffice. This is also possible for the Content Delivery API data. You can extend the preview functionality in the backoffice by configuring external preview URLs for client libraries consuming the Content Delivery API.
{% hint style="info" %}
-To get familiar with the preview functionality in the Delivery API, please refer to the [Preview concept](https://docs.umbraco.com/umbraco-cms/reference/content-delivery-api#preview) section.
+To get familiar with the preview functionality in the Delivery API, refer to the [Preview concept](https://docs.umbraco.com/umbraco-cms/reference/content-delivery-api#preview) section.
{% endhint %}
{% hint style="info" %}
diff --git a/15/umbraco-cms/reference/content-delivery-api/extension-api-for-querying.md b/15/umbraco-cms/reference/content-delivery-api/extension-api-for-querying.md
index 5c3634ca917..678a51b0fb9 100644
--- a/15/umbraco-cms/reference/content-delivery-api/extension-api-for-querying.md
+++ b/15/umbraco-cms/reference/content-delivery-api/extension-api-for-querying.md
@@ -6,7 +6,7 @@ description: >-
# Extension API for querying
-The Delivery API allows you to retrieve multiple items by utilizing the `/umbraco/delivery/api/v2/content` endpoint. With the built-in query parameters, you have the flexibility to get any number of content nodes based on your needs. For a comprehensive list of supported query options, please refer to the [Endpoints](./#endpoints) section.
+The Delivery API allows you to retrieve multiple items by utilizing the `/umbraco/delivery/api/v2/content` endpoint. With the built-in query parameters, you have the flexibility to get any number of content nodes based on your needs. For a comprehensive list of supported query options, refer to the [Endpoints](./#endpoints) section.
For the query endpoint, we have created a new Examine index (_DeliveryApiContentIndex_) that facilitates fast retrieval of the desired content. This index ensures quick indexing and searching of data, with the possibility for future extensions.
diff --git a/15/umbraco-cms/reference/content-delivery-api/media-delivery-api.md b/15/umbraco-cms/reference/content-delivery-api/media-delivery-api.md
index b271bb768ea..c2616fd1ee9 100644
--- a/15/umbraco-cms/reference/content-delivery-api/media-delivery-api.md
+++ b/15/umbraco-cms/reference/content-delivery-api/media-delivery-api.md
@@ -4,7 +4,7 @@ description: Using the Media Delivery API.
# Media Delivery API
-The Media Delivery API allows for accessing the Umbraco media items in a headless manner. This API applies many of the same concepts as its content counterpart, although with fewer options. If you haven't already, please familiarize yourself with the [Content Delivery API](https://docs.umbraco.com/umbraco-cms/reference/content-delivery-api) before reading this article.
+The Media Delivery API allows for accessing the Umbraco media items in a headless manner. This API applies many of the same concepts as its content counterpart, although with fewer options. If you haven't already, familiarize yourself with the [Content Delivery API](https://docs.umbraco.com/umbraco-cms/reference/content-delivery-api) before reading this article.
{% hint style="info" %}
The Media Delivery API specification is created to mimic that of the Content Delivery API. However, the default implementation of this specification is limited and does not support the entire specification.
@@ -168,7 +168,7 @@ Returns single or multiple items.
{% swagger-parameter in="query" name="fetch" type="String" required="true" %}
Structural query string option (e.g. `ancestors`, `children`, `descendants`).
-**Please note:** The default API implementation only supports `children`.
+**Note:** The default API implementation only supports `children`.
{% endswagger-parameter %}
{% swagger-parameter in="query" name="filter" type="String Array" required="false" %}
diff --git a/15/umbraco-cms/reference/content-delivery-api/property-expansion-and-limiting.md b/15/umbraco-cms/reference/content-delivery-api/property-expansion-and-limiting.md
index 21bb3108cd3..07e415b220a 100644
--- a/15/umbraco-cms/reference/content-delivery-api/property-expansion-and-limiting.md
+++ b/15/umbraco-cms/reference/content-delivery-api/property-expansion-and-limiting.md
@@ -5,7 +5,7 @@ description: Using property expansion and limiting to shape the Delivery API out
# Property expansion and limiting
{% hint style="info" %}
-This article explains the mechanics of property expansion and limiting in depth. If you haven't already, please read the [Getting started](https://docs.umbraco.com/umbraco-cms/reference/content-delivery-api) article first - in particular the "Concepts" section.
+This article explains the mechanics of property expansion and limiting in depth. If you haven't already, read the [Getting started](https://docs.umbraco.com/umbraco-cms/reference/content-delivery-api) article first - in particular the "Concepts" section.
{% endhint %}
Property expansion and limiting applies only to select property editors. The following built-in property editors in Umbraco support expansion and limiting:
@@ -537,7 +537,7 @@ Start-Item: posts
## Working with block-based editors
{% hint style="info" %}
-If you are not familiar with block-based editors, please refer to [this article](https://docs.umbraco.com/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/block-editor) for the general concepts of these.
+If you are not familiar with block-based editors, refer to the [Block Editor article](https://docs.umbraco.com/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/block-editor) for the general concepts of these.
{% endhint %}
In the API output, a block has little value without its contained properties. Therefore, the content and settings properties of blocks are always included in the output. However, these properties are not expanded. As such, we can apply expansion and limiting to the contained properties.
diff --git a/15/umbraco-cms/reference/content-delivery-api/protected-content-in-the-delivery-api/README.md b/15/umbraco-cms/reference/content-delivery-api/protected-content-in-the-delivery-api/README.md
index 5f82de6bfcd..7a9c89acb95 100644
--- a/15/umbraco-cms/reference/content-delivery-api/protected-content-in-the-delivery-api/README.md
+++ b/15/umbraco-cms/reference/content-delivery-api/protected-content-in-the-delivery-api/README.md
@@ -10,12 +10,12 @@ Umbraco allows for restricting access to content. Using the "Public access" feat
By default, protected content is ignored by the Delivery API, and is never exposed through any API endpoints. However, by enabling member authorization in the Delivery API, protected content can be accessed by means of access tokens.
{% hint style="info" %}
-If you are not familiar with members in Umbraco, please read the [Members](../../../fundamentals/data/members.md) article.
+If you are not familiar with members in Umbraco, read the [Members](../../../fundamentals/data/members.md) article.
{% endhint %}
{% hint style="info" %}
This article describes how to access protected content in a client-to-server context, using an interactive authorization flow.\
-If you are looking to achieve server-to-server access to protected content, please refer to [server-to-server access article](server-to-server-access.md) instead.
+If you are looking to achieve server-to-server access to protected content, refer to [server-to-server access article](server-to-server-access.md) instead.
{% endhint %}
{% hint style="warning" %}
@@ -329,7 +329,7 @@ Access tokens expire after one hour. Once expired, a new access token must be ob
Refresh tokens provide a means to obtain a new access token without having to go through the authentication flow. A refresh token is issued automatically by the Delivery API when the `offline_access` scope is specified in the authorization request.
{% hint style="info" %}
-Refresh tokens are subject to certain limitations and can result in security issues if not applied correctly. All this is beyond the scope of this article to explain in detail. Please familiarize yourself with the inner workings of refresh tokens before applying them in a solution.
+Refresh tokens are subject to certain limitations and can result in security issues if not applied correctly. All this is beyond the scope of this article to explain in detail. Familiarize yourself with the inner workings of refresh tokens before applying them in a solution.
{% endhint %}
## Logging out members
@@ -409,7 +409,7 @@ Remember to use `umbraco-member` as `client_id` when authorizing. `client_secret
## Client configuration samples
The following samples show how to configure an ASP.NET Core client to utilize member authorization in the Delivery API.\
-To put these samples into context, please refer to the article above.
+To put these samples into context, refer to the article above.
### Basic client configuration
diff --git a/15/umbraco-cms/reference/management-api/external-access.md b/15/umbraco-cms/reference/management-api/external-access.md
index 7c7aebc79e0..a1971701717 100644
--- a/15/umbraco-cms/reference/management-api/external-access.md
+++ b/15/umbraco-cms/reference/management-api/external-access.md
@@ -22,7 +22,7 @@ The token endpoint response looks like this:
As shown, the access token should be used as a Bearer token when consuming the Management API.
-Also, notice that access tokens have a fixed expiry. While you can keep issuing new tokens for the Client Credentials, please reuse tokens within their lifespan. This will be more performant and avoid flooding the Umbraco database with tokens.
+Also, notice that access tokens have a fixed expiry. While you can keep issuing new tokens for the Client Credentials, reuse tokens within their lifespan. This will be more performant and avoid flooding the Umbraco database with tokens.
{% hint style="info" %}
The Management API does not support OpenID Connect Discovery. This is reserved for Members accessing protected content via the [Delivery API](../content-delivery-api/protected-content-in-the-delivery-api/README.md).
diff --git a/15/umbraco-cms/reference/searching/examine/indexing.md b/15/umbraco-cms/reference/searching/examine/indexing.md
index 0a5983d2804..a78f41aca60 100644
--- a/15/umbraco-cms/reference/searching/examine/indexing.md
+++ b/15/umbraco-cms/reference/searching/examine/indexing.md
@@ -329,7 +329,7 @@ The index will only update its content when you manually trigger an index rebuil
To update your index when content changes, you can use notification handlers.
{% hint style="info" %}
-The following handler class does not automatically update the descendant items of the modified content nodes, such as removing descendants of deleted content. If changes to the parent content item can affect its children or descendant items in your setup, please refer to the [UmbracoContentIndex.PerformDeleteFromIndex() in Umbraco](https://github.com/umbraco/Umbraco-CMS/blob/main/src/Umbraco.Examine.Lucene/UmbracoContentIndex.cs#L124-L153). Such logic should be applied when both removing and reindexing content items of type _product_.
+The following handler class does not automatically update the descendant items of the modified content nodes, such as removing descendants of deleted content. If changes to the parent content item can affect its children or descendant items in your setup, refer to the [UmbracoContentIndex.PerformDeleteFromIndex() in Umbraco](https://github.com/umbraco/Umbraco-CMS/blob/main/src/Umbraco.Examine.Lucene/UmbracoContentIndex.cs#L124-L153). Such logic should be applied when both removing and reindexing content items of type _product_.
{% endhint %}
```csharp
diff --git a/15/umbraco-cms/tutorials/editors-manual/tips-and-tricks/notifications.md b/15/umbraco-cms/tutorials/editors-manual/tips-and-tricks/notifications.md
index ea2b489d814..7bebc138cf7 100644
--- a/15/umbraco-cms/tutorials/editors-manual/tips-and-tricks/notifications.md
+++ b/15/umbraco-cms/tutorials/editors-manual/tips-and-tricks/notifications.md
@@ -18,5 +18,5 @@ The notification settings apply to the chosen content item as well as any child
{% endhint %}
{% hint style="info" %}
-If the notifications option does not appear, the SMTP settings are probably incorrect. In this case please contact the administrator of your website.
+If the notifications option does not appear, the SMTP settings are probably incorrect. In this case, contact the administrator of your website.
{% endhint %}
diff --git a/15/umbraco-commerce/changelog-archive/Vendr-core.md b/15/umbraco-commerce/changelog-archive/Vendr-core.md
index 2de685aae2f..6f971d0b029 100644
--- a/15/umbraco-commerce/changelog-archive/Vendr-core.md
+++ b/15/umbraco-commerce/changelog-archive/Vendr-core.md
@@ -559,7 +559,7 @@ description: Changelog for the Core Vendr product
**Date:** 2020-12-10\
**Description:** Major breaking changes release
-For more details on this release, including a recommended upgrade strategy, please see the [Vendr 1.4.0 RC blog post](https://vendr.net/blog/vendr-1-4-0-release-candidate/).
+For more details on this release, including a recommended upgrade strategy, see the [Vendr 1.4.0 RC blog post](https://vendr.net/blog/vendr-1-4-0-release-candidate/).
* Added price adjustments/adjusters.
* Added amount adjustments/adjusters.
diff --git a/15/umbraco-deploy/extending/handling-cache-refresher-notifications.md b/15/umbraco-deploy/extending/handling-cache-refresher-notifications.md
index 4568be36f3a..155c1bdb382 100644
--- a/15/umbraco-deploy/extending/handling-cache-refresher-notifications.md
+++ b/15/umbraco-deploy/extending/handling-cache-refresher-notifications.md
@@ -27,7 +27,7 @@ The following two code samples illustrate how this can be done.
The first handles a content cache refresher, which takes a payload from where the content ID can be extracted. Using that the content can be retrieved in the local Umbraco instance and used as appropriate.
-For more details and further examples, please see the [CMS Cache Refresher Notifications documentation](https://docs.umbraco.com/umbraco-cms/reference/notifications/cacherefresher-notifications).
+For more details and further examples, see the [CMS Cache Refresher Notifications documentation](https://docs.umbraco.com/umbraco-cms/reference/notifications/cacherefresher-notifications).
```csharp
using Umbraco.Cms.Core.Cache;
diff --git a/15/umbraco-deploy/troubleshooting.md b/15/umbraco-deploy/troubleshooting.md
index 669d3b751d6..dd8ab79b693 100644
--- a/15/umbraco-deploy/troubleshooting.md
+++ b/15/umbraco-deploy/troubleshooting.md
@@ -6,7 +6,7 @@ description: The troubleshooting section for Umbraco Deploy
In this troubleshooting section, you can find help to resolve issues that you might run into when using Umbraco Deploy.
-If you are unable to find the issue you are having, then please reach out to our friendly support team at contact@umbraco.com.
+If you are unable to find the issue you are having, then reach out to our friendly support team at contact@umbraco.com.
## Schema mismatches
diff --git a/15/umbraco-forms/developer/ajaxforms.md b/15/umbraco-forms/developer/ajaxforms.md
index ba1e678dab6..65ad834a109 100644
--- a/15/umbraco-forms/developer/ajaxforms.md
+++ b/15/umbraco-forms/developer/ajaxforms.md
@@ -538,7 +538,7 @@ With this in place any request to the Forms API will be rejected unless the conf
## Rendering and Submitting forms with JavaScript
-For an illustrative example showing how a form can be rendered, validated and submitted using the API and vanilla JavaScript, please [see this gist](https://gist.github.com/AndyButland/9371175d6acf24a5307b053398f08448).
+For an illustrative example showing how a form can be rendered, validated and submitted using the API and vanilla JavaScript, [see this gist](https://gist.github.com/AndyButland/9371175d6acf24a5307b053398f08448).
Examples demonstrating how to handle a file upload and use reCAPTCHA fields are included.
diff --git a/15/umbraco-forms/developer/healthchecks/README.md b/15/umbraco-forms/developer/healthchecks/README.md
index d9b34c2e10b..1caffa0ba07 100644
--- a/15/umbraco-forms/developer/healthchecks/README.md
+++ b/15/umbraco-forms/developer/healthchecks/README.md
@@ -53,7 +53,7 @@ To support this, we provide the following SQL scripts:
The first of these provides the SQL statements required to apply the schema updates for 8.7.0+ to the common Umbraco Forms tables. The second applies to those tables used for when Forms are stored in the database, and hence only need to be applied if that option is configured.
{% hint style="info" %}
-Before running any scripts or queries, please be sure to have a database backup in place.
+Before running any scripts or queries, be sure to have a database backup in place.
{% endhint %}
To take an example, let's say that via the health check results you can see that the _"Unique constraint on table 'UFForms', column 'Key' is missing."_
diff --git a/15/umbraco-forms/developer/prepping-frontend.md b/15/umbraco-forms/developer/prepping-frontend.md
index f0b644751f5..366426ea8aa 100644
--- a/15/umbraco-forms/developer/prepping-frontend.md
+++ b/15/umbraco-forms/developer/prepping-frontend.md
@@ -38,7 +38,7 @@ You can use this to apply `async` or `defer` attributes. For example:
@Html.RenderUmbracoFormDependencies(Url, new { @async = "async" })
```
-If using `async`, please make sure to [disable the Forms client-side validation framework check](../developer/configuration/README.md#disableclientsidevalidationdependencycheck). This is necessary as it's not possible to guarantee that the asynchronous script will load in time to be recognized by the check. This can then cause a false positive warning.
+If using `async`, make sure to [disable the Forms client-side validation framework check](../developer/configuration/README.md#disableclientsidevalidationdependencycheck). This is necessary as it's not possible to guarantee that the asynchronous script will load in time to be recognized by the check. This can then cause a false positive warning.
## Validation Using jQuery
diff --git a/15/umbraco-forms/installation/the-licensing-model.md b/15/umbraco-forms/installation/the-licensing-model.md
index 8909e5e9d1d..fdd7dbbae87 100644
--- a/15/umbraco-forms/installation/the-licensing-model.md
+++ b/15/umbraco-forms/installation/the-licensing-model.md
@@ -114,7 +114,7 @@ This will also change the location for other Umbraco-related licenses in this pr
The algorithm used to decrypt Forms licenses is not supported on locked down FIPS compliant environments, such as those used in the defense industry.
-If you are in this situation and unable to resolve it via configuration of the environment, please reach out to Umbraco support.
+If you are in this situation and unable to resolve it via configuration of the environment, reach out to Umbraco Support.
We have the possibility of generating and providing Forms licenses using alternate algorithms.
diff --git a/16/umbraco-cms/customizing/extending-overview/extension-types/entity-actions.md b/16/umbraco-cms/customizing/extending-overview/extension-types/entity-actions.md
index 2554b0a6cac..9408aaad8c4 100644
--- a/16/umbraco-cms/customizing/extending-overview/extension-types/entity-actions.md
+++ b/16/umbraco-cms/customizing/extending-overview/extension-types/entity-actions.md
@@ -147,7 +147,7 @@ Here is a list of the entity actions and associated user permission codes shippe
If you are building a package or adding custom entity actions to your solution, it's important to pick a permission letter. Ensure that it doesn't clash with one of these.
-If you have created a package using a custom entity action, please consider providing an update to this documentation page. You can do this via a PR to the [documentation repository](https://github.com/umbraco/UmbracoDocs). This will allow other developers to discover and avoid using the same permission letter.
+If you have created a package using a custom entity action, consider providing an update to this documentation page. You can do this via a PR to the [documentation repository](https://github.com/umbraco/UmbracoDocs). This will allow other developers to discover and avoid using the same permission letter.
Currently, we allow two extension points on the client for user permissions:
diff --git a/16/umbraco-cms/customizing/extending-overview/extension-types/tree.md b/16/umbraco-cms/customizing/extending-overview/extension-types/tree.md
index a7da343a01c..f4b813dc8b1 100644
--- a/16/umbraco-cms/customizing/extending-overview/extension-types/tree.md
+++ b/16/umbraco-cms/customizing/extending-overview/extension-types/tree.md
@@ -7,7 +7,7 @@ description: A guide to creating a custom tree in Umbraco
The tree is a hierarchical structure of nodes and is registered in the Backoffice extension registry. A tree can be rendered anywhere in the Backoffice with the help of the ` ` element.
{% hint style="info" %}
-To see how to register a tree as a menu in a section, please refer to the [Section Sidebar](./sections/section-sidebar.md) article.
+To see how to register a tree as a menu in a section, refer to the [Section Sidebar](./sections/section-sidebar.md) article.
{% endhint %}
## Creating trees
diff --git a/16/umbraco-cms/customizing/property-editors/property-editor-validation.md b/16/umbraco-cms/customizing/property-editors/property-editor-validation.md
index b78c8af6085..7ad6b7be7ae 100644
--- a/16/umbraco-cms/customizing/property-editors/property-editor-validation.md
+++ b/16/umbraco-cms/customizing/property-editors/property-editor-validation.md
@@ -68,7 +68,7 @@ The third argument is the Validator check, which is executed every time there is
If you're looking to make server requests as part of your check, then it is recommended to avoid calling the server more often than needed. Do only ask the server if there is a value, and only ask the server again if the value is different from last time.
{% endhint %}
-Notice that `value` is already defined in the FormControlMixin, and ideally, you do not overwrite it. If so, then please make sure to still set the value property of the Mixin. As that will trigger a validation update.
+Notice that `value` is already defined in the `FormControlMixin`, and ideally, you do not overwrite it. If so, then make sure to still set the value property of the Mixin. As that will trigger a validation update.
```typescript
@property({ type: String })
diff --git a/16/umbraco-cms/extending/flag-providers.md b/16/umbraco-cms/extending/flag-providers.md
index 172e27306d2..c8e42982fea 100644
--- a/16/umbraco-cms/extending/flag-providers.md
+++ b/16/umbraco-cms/extending/flag-providers.md
@@ -80,7 +80,7 @@ The flag provider needs to be registered with Umbraco in a composer or applicati
For some flags, there may be sufficient information on the view models to map whether a flag should be created.
-For an example of this, please see the core flag provider `IsProtectedFlagProvider` whose [source code can be found here](https://github.com/umbraco/Umbraco-CMS/blob/main/src/Umbraco.Cms.Api.Management/Services/Flags/IsProtectedFlagProvider.cs).
+For an example of this, see the core flag provider `IsProtectedFlagProvider` whose [source code can be found here](https://github.com/umbraco/Umbraco-CMS/blob/main/src/Umbraco.Cms.Api.Management/Services/Flags/IsProtectedFlagProvider.cs).
More complex flags will require additional information, using the identifiers of the view models to retrieve the necessary data. It's important to avoid "N+1" issues. The aim should be to retrieve all the data needed to populate the flags for the whole collection in one step.
diff --git a/16/umbraco-cms/extending/health-check/README.md b/16/umbraco-cms/extending/health-check/README.md
index 2b03622e5ee..10a319a2086 100644
--- a/16/umbraco-cms/extending/health-check/README.md
+++ b/16/umbraco-cms/extending/health-check/README.md
@@ -188,7 +188,7 @@ Disallow: /umbraco/";
## Custom health check notifications
-Health check notifications can be scheduled to run periodically and notify you of the results. Included with Umbraco is a notification method to deliver the results via email. In a similar manner to how it's possible to create your health checks, you can also create custom notification methods to send the message summarising the status of the health checks via other means. Again, for further details on implementing this please refer to the [existing notification methods within the core code base](https://github.com/umbraco/Umbraco-CMS/tree/v10/dev/src/Umbraco.Core/HealthChecks/NotificationMethods).
+Health check notifications can be scheduled to run periodically and notify you of the results. Included with Umbraco is a notification method to deliver the results via email. In a similar manner to how it's possible to create your health checks, you can also create custom notification methods to send the message summarising the status of the health checks via other means. Again, for further details on implementing this, refer to the [existing notification methods within the core code base](https://github.com/umbraco/Umbraco-CMS/tree/v10/dev/src/Umbraco.Core/HealthChecks/NotificationMethods).
Each notification method needs to implement the core interface `IHealthCheckNotificationMethod` and, for ease of creation, can inherit from the base class `NotificationMethodBase`, which itself implements the `IHealthCheckNotificationMethod` interface. The class must also be decorated with an instance of the `HealthCheckNotificationMethod` attribute. There's one method to implement - `SendAsync(HealthCheckResults results)` - which is responsible for taking the results of the health checks and sending them via the mechanism of your choice.
diff --git a/16/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/block-editor/block-list-editor.md b/16/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/block-editor/block-list-editor.md
index f84ccd829d5..b45846b8e66 100644
--- a/16/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/block-editor/block-list-editor.md
+++ b/16/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/block-editor/block-list-editor.md
@@ -139,7 +139,7 @@ These partial views must be placed in this folder: `Views/Partials/BlockList/Com
A Partial View will receive the model of `Umbraco.Core.Models.Blocks.BlockListItem`. This gives you the option to access properties of the Content and Settings section of your Block.
-In the following example of a Partial view for a Block Type, please note that the `MyElementTypeAliasOfContent`and `MyElementTypeAliasOfSettings` should correspond with the selected Element Type Alias for the given model in your case.
+In the following example of a Partial view for a Block Type, the `MyElementTypeAliasOfContent`and `MyElementTypeAliasOfSettings` should correspond with the selected Element Type Alias for the given model.
Example:
diff --git a/16/umbraco-cms/fundamentals/setup/server-setup/running-umbraco-in-docker.md b/16/umbraco-cms/fundamentals/setup/server-setup/running-umbraco-in-docker.md
index 928204cfc13..18256c7e011 100644
--- a/16/umbraco-cms/fundamentals/setup/server-setup/running-umbraco-in-docker.md
+++ b/16/umbraco-cms/fundamentals/setup/server-setup/running-umbraco-in-docker.md
@@ -35,7 +35,7 @@ You may prefer to avoid writing to disk for logs when hosting in containers. If
You can also provide an alternative implementation of a common abstraction for the log viewer. In this way you can read logs from the location where you have configured them to be written.
-For more on this please read the article on Umbraco's [log viewer](../../backoffice/logviewer.md).
+For more details, read the article on Umbraco's [log viewer](../../backoffice/logviewer.md).
### Data
diff --git a/16/umbraco-cms/fundamentals/setup/upgrading/version-specific/README.md b/16/umbraco-cms/fundamentals/setup/upgrading/version-specific/README.md
index c4574ee887d..217de8d114d 100644
--- a/16/umbraco-cms/fundamentals/setup/upgrading/version-specific/README.md
+++ b/16/umbraco-cms/fundamentals/setup/upgrading/version-specific/README.md
@@ -123,7 +123,7 @@ Below you can find the list of breaking changes introduced in Umbraco 14 CMS.
* [**AngularJS removed: A new backoffice built with Web Components, Lit, and fueled by the Umbraco UI Library**](https://github.com/umbraco/Umbraco.CMS.Backoffice)
-This is by far the most impactful update of Umbraco in years. We’ve fundamentally changed the way you extend Umbraco. If you are experienced in developing Web Components you can now use your preferred framework for this. If you are unsure how to proceed, you can implement it with Typescript and the Lit library like we’ve done. In this case, please start with this article on how to [customize the Backoffice](https://docs.umbraco.com/umbraco-cms/customizing/overview).
+This is by far the most impactful update of Umbraco in years. We’ve fundamentally changed the way you extend Umbraco. If you are experienced in developing Web Components you can now use your preferred framework for this. If you are unsure how to proceed, you can implement it with Typescript and the Lit library like we’ve done. In this case, start with this article on how to [customize the Backoffice](https://docs.umbraco.com/umbraco-cms/customizing/overview).
The new Backoffice (Bellissima) is entirely built on the Umbraco UI Library. This means that you might experience some of your components not being rendered on the page because the name has been changed. You should be able to find equivalents to what you were used to. For example, the `umb-button` is now called `uui-button`, and `umb-box` is now `uui-box`. When extending the Backoffice, we encourage you to use our [Umbraco UI Library](https://uui.umbraco.com/) to ensure the same look and feel in your extensions. The UI Library is Open Source and [hosted on GitHub](https://github.com/umbraco/Umbraco.UI), so feel free to contribute with new components or raise issues or discussions.
@@ -147,7 +147,7 @@ Following the implementation of the new Backoffice (Bellissima), Umbraco has now
* **A new way of writing authorized controllers**
-If you have implemented API controllers in Umbraco before, we recommend you update or rewrite these. Please follow the [Documenting your Controllers](https://docs.umbraco.com/umbraco-cms/tutorials/creating-a-backoffice-api/documenting-your-controllers) article, as you’ll then ensure the same cool documentation of your APIs. Notice, that we’ve made a much better separation of concern between controllers and services so that there is no more business logic in controllers.
+If you have implemented API controllers in Umbraco before,it is recommended you update or rewrite these. Follow the [Documenting your Controllers](https://docs.umbraco.com/umbraco-cms/tutorials/creating-a-backoffice-api/documenting-your-controllers) article, as you’ll then ensure the same cool documentation of your APIs. Notice, that we’ve made a much better separation of concern between controllers and services so that there is no more business logic in controllers.
* [**Migration from Newtonsoft.Json to the System.Text.Json which removes Nested Content and Grid value converter and so on**](https://github.com/umbraco/Umbraco-CMS/pull/15728)
@@ -180,7 +180,7 @@ The `package.manifest` file is no longer supported and has been replaced with th
It's recommended that you bundle up your Backoffice static assets for instance by a tool called Vite. You can read more about this on the [Vite Package Setup](https://docs.umbraco.com/umbraco-cms/customizing/development-flow/vite-package-setup) article. You can still use libraries like Smidge for frontend static assets by manually installing the package from NuGet.
You can read the [Smidge documentation](https://github.com/Shazwazza/Smidge/wiki) on how to set up a similar setting to RuntimeMinification.
-For sites being upgraded from V13 or below, please remove [these two lines](https://github.com/umbraco/Umbraco-CMS/blob/04ed514a21279ae82d95b34c55cb2ba96545eb39/src/Umbraco.Web.UI/Views/_ViewImports.cshtml#L7-L8) from the `_ViewImports.cshtml` file.
+For sites being upgraded from V13 or below, remove [these two lines](https://github.com/umbraco/Umbraco-CMS/blob/04ed514a21279ae82d95b34c55cb2ba96545eb39/src/Umbraco.Web.UI/Views/_ViewImports.cshtml#L7-L8) from the `_ViewImports.cshtml` file.
* **Base classes for Backoffice controllers have been removed**
diff --git a/16/umbraco-cms/reference/content-delivery-api/additional-preview-environments-support.md b/16/umbraco-cms/reference/content-delivery-api/additional-preview-environments-support.md
index 5982899349b..72e3419c9c7 100644
--- a/16/umbraco-cms/reference/content-delivery-api/additional-preview-environments-support.md
+++ b/16/umbraco-cms/reference/content-delivery-api/additional-preview-environments-support.md
@@ -13,7 +13,7 @@ The way to achieve this beyond Umbraco 14 is to create and register an [Extensio
With Umbraco, you can save and preview draft content before going live. The preview feature allows you to visualize how a page will look like once it is published, directly from within the backoffice. This is also possible for the Content Delivery API data. You can extend the preview functionality in the backoffice by configuring external preview URLs for client libraries consuming the Content Delivery API.
{% hint style="info" %}
-To get introduced to the preview functionality in the Content Delivery API, please refer to the [Preview concept](https://docs.umbraco.com/umbraco-cms/reference/content-delivery-api#preview) section.
+To get introduced to the preview functionality in the Content Delivery API, refer to the [Preview concept](https://docs.umbraco.com/umbraco-cms/reference/content-delivery-api#preview) section.
{% endhint %}
{% hint style="info" %}
diff --git a/16/umbraco-cms/reference/content-delivery-api/extension-api-for-querying.md b/16/umbraco-cms/reference/content-delivery-api/extension-api-for-querying.md
index 5c3634ca917..678a51b0fb9 100644
--- a/16/umbraco-cms/reference/content-delivery-api/extension-api-for-querying.md
+++ b/16/umbraco-cms/reference/content-delivery-api/extension-api-for-querying.md
@@ -6,7 +6,7 @@ description: >-
# Extension API for querying
-The Delivery API allows you to retrieve multiple items by utilizing the `/umbraco/delivery/api/v2/content` endpoint. With the built-in query parameters, you have the flexibility to get any number of content nodes based on your needs. For a comprehensive list of supported query options, please refer to the [Endpoints](./#endpoints) section.
+The Delivery API allows you to retrieve multiple items by utilizing the `/umbraco/delivery/api/v2/content` endpoint. With the built-in query parameters, you have the flexibility to get any number of content nodes based on your needs. For a comprehensive list of supported query options, refer to the [Endpoints](./#endpoints) section.
For the query endpoint, we have created a new Examine index (_DeliveryApiContentIndex_) that facilitates fast retrieval of the desired content. This index ensures quick indexing and searching of data, with the possibility for future extensions.
diff --git a/16/umbraco-cms/reference/content-delivery-api/media-delivery-api.md b/16/umbraco-cms/reference/content-delivery-api/media-delivery-api.md
index b271bb768ea..c2616fd1ee9 100644
--- a/16/umbraco-cms/reference/content-delivery-api/media-delivery-api.md
+++ b/16/umbraco-cms/reference/content-delivery-api/media-delivery-api.md
@@ -4,7 +4,7 @@ description: Using the Media Delivery API.
# Media Delivery API
-The Media Delivery API allows for accessing the Umbraco media items in a headless manner. This API applies many of the same concepts as its content counterpart, although with fewer options. If you haven't already, please familiarize yourself with the [Content Delivery API](https://docs.umbraco.com/umbraco-cms/reference/content-delivery-api) before reading this article.
+The Media Delivery API allows for accessing the Umbraco media items in a headless manner. This API applies many of the same concepts as its content counterpart, although with fewer options. If you haven't already, familiarize yourself with the [Content Delivery API](https://docs.umbraco.com/umbraco-cms/reference/content-delivery-api) before reading this article.
{% hint style="info" %}
The Media Delivery API specification is created to mimic that of the Content Delivery API. However, the default implementation of this specification is limited and does not support the entire specification.
@@ -168,7 +168,7 @@ Returns single or multiple items.
{% swagger-parameter in="query" name="fetch" type="String" required="true" %}
Structural query string option (e.g. `ancestors`, `children`, `descendants`).
-**Please note:** The default API implementation only supports `children`.
+**Note:** The default API implementation only supports `children`.
{% endswagger-parameter %}
{% swagger-parameter in="query" name="filter" type="String Array" required="false" %}
diff --git a/16/umbraco-cms/reference/content-delivery-api/property-expansion-and-limiting.md b/16/umbraco-cms/reference/content-delivery-api/property-expansion-and-limiting.md
index 21bb3108cd3..17e6074c7fe 100644
--- a/16/umbraco-cms/reference/content-delivery-api/property-expansion-and-limiting.md
+++ b/16/umbraco-cms/reference/content-delivery-api/property-expansion-and-limiting.md
@@ -5,7 +5,7 @@ description: Using property expansion and limiting to shape the Delivery API out
# Property expansion and limiting
{% hint style="info" %}
-This article explains the mechanics of property expansion and limiting in depth. If you haven't already, please read the [Getting started](https://docs.umbraco.com/umbraco-cms/reference/content-delivery-api) article first - in particular the "Concepts" section.
+This article explains the mechanics of property expansion and limiting in depth. If you haven't already, read the [Getting started](https://docs.umbraco.com/umbraco-cms/reference/content-delivery-api) article first - in particular the "Concepts" section.
{% endhint %}
Property expansion and limiting applies only to select property editors. The following built-in property editors in Umbraco support expansion and limiting:
@@ -537,7 +537,7 @@ Start-Item: posts
## Working with block-based editors
{% hint style="info" %}
-If you are not familiar with block-based editors, please refer to [this article](https://docs.umbraco.com/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/block-editor) for the general concepts of these.
+If you are not familiar with block-based editors, refer to the [Block Editor article](https://docs.umbraco.com/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/block-editor).
{% endhint %}
In the API output, a block has little value without its contained properties. Therefore, the content and settings properties of blocks are always included in the output. However, these properties are not expanded. As such, we can apply expansion and limiting to the contained properties.
diff --git a/16/umbraco-cms/reference/content-delivery-api/protected-content-in-the-delivery-api/README.md b/16/umbraco-cms/reference/content-delivery-api/protected-content-in-the-delivery-api/README.md
index 5f82de6bfcd..6e4a18d0475 100644
--- a/16/umbraco-cms/reference/content-delivery-api/protected-content-in-the-delivery-api/README.md
+++ b/16/umbraco-cms/reference/content-delivery-api/protected-content-in-the-delivery-api/README.md
@@ -10,12 +10,12 @@ Umbraco allows for restricting access to content. Using the "Public access" feat
By default, protected content is ignored by the Delivery API, and is never exposed through any API endpoints. However, by enabling member authorization in the Delivery API, protected content can be accessed by means of access tokens.
{% hint style="info" %}
-If you are not familiar with members in Umbraco, please read the [Members](../../../fundamentals/data/members.md) article.
+If you are not familiar with members in Umbraco, read the [Members](../../../fundamentals/data/members.md) article.
{% endhint %}
{% hint style="info" %}
-This article describes how to access protected content in a client-to-server context, using an interactive authorization flow.\
-If you are looking to achieve server-to-server access to protected content, please refer to [server-to-server access article](server-to-server-access.md) instead.
+This article describes how to access protected content in a client-to-server context, using an interactive authorization flow.
+If you are looking to achieve server-to-server access to protected content, refer to [server-to-server access article](server-to-server-access.md) instead.
{% endhint %}
{% hint style="warning" %}
@@ -329,7 +329,7 @@ Access tokens expire after one hour. Once expired, a new access token must be ob
Refresh tokens provide a means to obtain a new access token without having to go through the authentication flow. A refresh token is issued automatically by the Delivery API when the `offline_access` scope is specified in the authorization request.
{% hint style="info" %}
-Refresh tokens are subject to certain limitations and can result in security issues if not applied correctly. All this is beyond the scope of this article to explain in detail. Please familiarize yourself with the inner workings of refresh tokens before applying them in a solution.
+Refresh tokens are subject to certain limitations and can result in security issues if not applied correctly. All this is beyond the scope of this article to explain in detail. Familiarize yourself with the inner workings of refresh tokens before applying them in a solution.
{% endhint %}
## Logging out members
@@ -408,8 +408,8 @@ Remember to use `umbraco-member` as `client_id` when authorizing. `client_secret
## Client configuration samples
-The following samples show how to configure an ASP.NET Core client to utilize member authorization in the Delivery API.\
-To put these samples into context, please refer to the article above.
+The following samples show how to configure an ASP.NET Core client to utilize member authorization in the Delivery API.
+To put these samples into context, refer to the article above.
### Basic client configuration
diff --git a/16/umbraco-cms/reference/management-api/external-access.md b/16/umbraco-cms/reference/management-api/external-access.md
index 7c7aebc79e0..a1971701717 100644
--- a/16/umbraco-cms/reference/management-api/external-access.md
+++ b/16/umbraco-cms/reference/management-api/external-access.md
@@ -22,7 +22,7 @@ The token endpoint response looks like this:
As shown, the access token should be used as a Bearer token when consuming the Management API.
-Also, notice that access tokens have a fixed expiry. While you can keep issuing new tokens for the Client Credentials, please reuse tokens within their lifespan. This will be more performant and avoid flooding the Umbraco database with tokens.
+Also, notice that access tokens have a fixed expiry. While you can keep issuing new tokens for the Client Credentials, reuse tokens within their lifespan. This will be more performant and avoid flooding the Umbraco database with tokens.
{% hint style="info" %}
The Management API does not support OpenID Connect Discovery. This is reserved for Members accessing protected content via the [Delivery API](../content-delivery-api/protected-content-in-the-delivery-api/README.md).
diff --git a/16/umbraco-cms/reference/searching/examine/indexing.md b/16/umbraco-cms/reference/searching/examine/indexing.md
index cb8b4fdd099..d97b0125c8a 100644
--- a/16/umbraco-cms/reference/searching/examine/indexing.md
+++ b/16/umbraco-cms/reference/searching/examine/indexing.md
@@ -335,7 +335,7 @@ The index will only update its content when you manually trigger an index rebuil
To update your index when content changes, you can use notification handlers.
{% hint style="info" %}
-The following handler class does not automatically update the descendant items of the modified content nodes, such as removing descendants of deleted content. If changes to the parent content item can affect its children or descendant items in your setup, please refer to the [UmbracoContentIndex.PerformDeleteFromIndex() in Umbraco](https://github.com/umbraco/Umbraco-CMS/blob/main/src/Umbraco.Examine.Lucene/UmbracoContentIndex.cs#L124-L153). Such logic should be applied when both removing and reindexing content items of type _product_.
+The following handler class does not automatically update the descendant items of the modified content nodes, such as removing descendants of deleted content. If changes to the parent content item can affect its children or descendant items in your setup, refer to the [UmbracoContentIndex.PerformDeleteFromIndex() in Umbraco](https://github.com/umbraco/Umbraco-CMS/blob/main/src/Umbraco.Examine.Lucene/UmbracoContentIndex.cs#L124-L153). Such logic should be applied when both removing and reindexing content items of type _product_.
{% endhint %}
```csharp
diff --git a/16/umbraco-cms/tutorials/editors-manual/tips-and-tricks/notifications.md b/16/umbraco-cms/tutorials/editors-manual/tips-and-tricks/notifications.md
index bdbe47bbc58..224f2a514a3 100644
--- a/16/umbraco-cms/tutorials/editors-manual/tips-and-tricks/notifications.md
+++ b/16/umbraco-cms/tutorials/editors-manual/tips-and-tricks/notifications.md
@@ -18,5 +18,5 @@ The notification settings apply to the chosen content item as well as any child
{% endhint %}
{% hint style="info" %}
-If the notifications option does not appear, the SMTP settings are probably incorrect. In this case please contact the administrator of your website.
+If the notifications option does not appear, the SMTP settings are probably incorrect. In this case, contact the administrator of your website.
{% endhint %}
diff --git a/16/umbraco-commerce/changelog-archive/Vendr-core.md b/16/umbraco-commerce/changelog-archive/Vendr-core.md
index 2de685aae2f..6f971d0b029 100644
--- a/16/umbraco-commerce/changelog-archive/Vendr-core.md
+++ b/16/umbraco-commerce/changelog-archive/Vendr-core.md
@@ -559,7 +559,7 @@ description: Changelog for the Core Vendr product
**Date:** 2020-12-10\
**Description:** Major breaking changes release
-For more details on this release, including a recommended upgrade strategy, please see the [Vendr 1.4.0 RC blog post](https://vendr.net/blog/vendr-1-4-0-release-candidate/).
+For more details on this release, including a recommended upgrade strategy, see the [Vendr 1.4.0 RC blog post](https://vendr.net/blog/vendr-1-4-0-release-candidate/).
* Added price adjustments/adjusters.
* Added amount adjustments/adjusters.
diff --git a/16/umbraco-deploy/extending/handling-cache-refresher-notifications.md b/16/umbraco-deploy/extending/handling-cache-refresher-notifications.md
index 4568be36f3a..155c1bdb382 100644
--- a/16/umbraco-deploy/extending/handling-cache-refresher-notifications.md
+++ b/16/umbraco-deploy/extending/handling-cache-refresher-notifications.md
@@ -27,7 +27,7 @@ The following two code samples illustrate how this can be done.
The first handles a content cache refresher, which takes a payload from where the content ID can be extracted. Using that the content can be retrieved in the local Umbraco instance and used as appropriate.
-For more details and further examples, please see the [CMS Cache Refresher Notifications documentation](https://docs.umbraco.com/umbraco-cms/reference/notifications/cacherefresher-notifications).
+For more details and further examples, see the [CMS Cache Refresher Notifications documentation](https://docs.umbraco.com/umbraco-cms/reference/notifications/cacherefresher-notifications).
```csharp
using Umbraco.Cms.Core.Cache;
diff --git a/16/umbraco-deploy/troubleshooting.md b/16/umbraco-deploy/troubleshooting.md
index 669d3b751d6..dd8ab79b693 100644
--- a/16/umbraco-deploy/troubleshooting.md
+++ b/16/umbraco-deploy/troubleshooting.md
@@ -6,7 +6,7 @@ description: The troubleshooting section for Umbraco Deploy
In this troubleshooting section, you can find help to resolve issues that you might run into when using Umbraco Deploy.
-If you are unable to find the issue you are having, then please reach out to our friendly support team at contact@umbraco.com.
+If you are unable to find the issue you are having, then reach out to our friendly support team at contact@umbraco.com.
## Schema mismatches
diff --git a/16/umbraco-engage/developers/analytics/client-side-events-and-additional-javascript-files/bridging-library-for-google-analytics.md b/16/umbraco-engage/developers/analytics/client-side-events-and-additional-javascript-files/bridging-library-for-google-analytics.md
index 2aca9afb5de..bf92135f530 100644
--- a/16/umbraco-engage/developers/analytics/client-side-events-and-additional-javascript-files/bridging-library-for-google-analytics.md
+++ b/16/umbraco-engage/developers/analytics/client-side-events-and-additional-javascript-files/bridging-library-for-google-analytics.md
@@ -65,7 +65,7 @@ The captured GA4 events will appear in Analytics -> Events in the **GA 4 - Bridg
### Using GA4 events in Goals
-If you want to trigger a goal based on a GA4 event please use the following information:
+If you want to trigger a goal based on a GA4 event, use the following information:
-Category: **GA 4 Bridging**\
+Category: **GA 4 Bridging**
Action: **\**
diff --git a/16/umbraco-engage/installation/installation.md b/16/umbraco-engage/installation/installation.md
index e28d8d50145..63b52e5efe3 100644
--- a/16/umbraco-engage/installation/installation.md
+++ b/16/umbraco-engage/installation/installation.md
@@ -52,7 +52,7 @@ dotnet add package Umbraco.Engage
```
{% hint style="info" %}
-If you have any trouble, please go to [Troubleshooting installs](troubleshooting-installs.md).
+If you have any trouble, go to [Troubleshooting installs](troubleshooting-installs.md).
{% endhint %}
## Next steps
@@ -137,7 +137,7 @@ If you [change the default cookie behavior](../developers/introduction/the-umbra
### Load balancing and CM / CD environments
-Are you using a load-balanced setup or separate CM and CD environments? [Please check our documentation about this topic](../getting-started/for-developers/loadbalancing-and-cm-cd-environments.md).
+Are you using a load-balanced setup or separate CM and CD environments? [Check our documentation about this topic](../getting-started/for-developers/loadbalancing-and-cm-cd-environments.md).
### The first run
diff --git a/16/umbraco-engage/installation/troubleshooting-installs.md b/16/umbraco-engage/installation/troubleshooting-installs.md
index 2c7fc0f5658..e71cb8d74df 100644
--- a/16/umbraco-engage/installation/troubleshooting-installs.md
+++ b/16/umbraco-engage/installation/troubleshooting-installs.md
@@ -12,7 +12,7 @@ If you have problems with Umbraco Engage setup or configuration, this checklist
After logging in to Umbraco, you can see the Engage section next to the other main sections in the Umbraco backoffice.
-If you cannot see this, please check if your Umbraco user or user group has access to the Engage section.
+If you cannot see this, check if your Umbraco user or user group has access to the Engage section.

diff --git a/16/umbraco-engage/marketers-and-editors/settings/setting-up-goals.md b/16/umbraco-engage/marketers-and-editors/settings/setting-up-goals.md
index 924a0d1d497..c85a436440c 100644
--- a/16/umbraco-engage/marketers-and-editors/settings/setting-up-goals.md
+++ b/16/umbraco-engage/marketers-and-editors/settings/setting-up-goals.md
@@ -35,9 +35,9 @@ You can specify how the goal will be triggered:
* Via a pageview/set of pages that are visited
* Via a page event that can be triggered
- * If you want to trigger a goal based on a GA4 event please use the following information:
+ * If you want to trigger a goal based on a GA4 event, use the following information:
- Category: **GA 4 Bridging**\
+ Category: **GA 4 Bridging**
Action: **\**
* Via an Umbraco Forms submission
* Via some custom code
diff --git a/16/umbraco-engage/upgrading/migrate-from-umarketingsuite.md b/16/umbraco-engage/upgrading/migrate-from-umarketingsuite.md
index 6ede83b170a..665a78eaa58 100644
--- a/16/umbraco-engage/upgrading/migrate-from-umarketingsuite.md
+++ b/16/umbraco-engage/upgrading/migrate-from-umarketingsuite.md
@@ -63,7 +63,7 @@ Run this script on your locally restored database to prepare for the migration.
3. Verify that the uMarketingSuite table integrity check returns the expected results.
{% hint style="info" %}
-If any of these checks return a failure, please resolve the issue before proceeding with the migration.
+If any of these checks return a failure, resolve the issue before proceeding with the migration.
{% endhint %}
The result should look like this:
@@ -79,7 +79,7 @@ The result should look like this:
---Finished running Pre-Requisite Checks. Please verify if all 5 checks succeeded before proceeding---
```
-If any of these checks return a failure, please resolve the issue before proceeding with the migration.
+If any of these checks return a failure, resolve the issue before proceeding with the migration.
## Step 3: Replace NuGet packages and dependencies
@@ -139,7 +139,7 @@ dotnet add package Umbraco.Engage.Commerce
Based on the [Key Changes](migrate-from-umarketingsuite.md#key-changes) below update all uMarketingSuite references to the new Umbraco Engage alternatives. Ensure you update any Views/Partials that also reference these. This includes the different uMarketingSuite clientside scripts (like the analytics & ga4-bridge) and the Cockpit.
-Please find below an overview of the changes to the default scripts in a uMarketingSuite installation:
+Find below an overview of the changes to the default scripts in a uMarketingSuite installation:
* Rename scripts & Asset Paths containing the `uMarketingSuite` keyword to:
* `Assets/Umbraco.Engage/Scripts/umbracoEngage.analytics.js`
@@ -147,7 +147,7 @@ Please find below an overview of the changes to the default scripts in a uMarket
* `Assets/Umbraco.Engage/Scripts/umbracoEngage.analytics.blockerdetection.js`
* The Cockpit partial view has been moved, and any references should be changed to:
* `Partials/Umbraco.Engage/Cockpit`
-* If you are tracking custom events please make sure to update the calls to the send event method:
+* If you are tracking custom events make sure to update the calls to the send event method:
* `ums("send", "event", "", "", "")`
is now:
@@ -376,7 +376,7 @@ dotnet add package Umbraco.Engage.Forms
If you are using the uMarketingSuite.Headless package, applications that use the uMarketingSuite API will need to be updated. This needs to happen to be able to use the new Umbraco Engage API, accessible via the `/umbraco/engage/api/` routes.
-The v1 Engage APIs (v13.0.0 of Umbraco Engage) maintain the same functionality as the v1 uMarketingSuite APIs. For more details on the API, please refer to the Swagger documentation provided by Umbraco Engage.
+The v1 Engage APIs (v13.0.0 of Umbraco Engage) maintain the same functionality as the v1 uMarketingSuite APIs. For more details on the API, refer to the Swagger documentation provided by Umbraco Engage.
You can install the Umbraco Engage Headless add-on package using the following command:
diff --git a/16/umbraco-forms/developer/ajaxforms.md b/16/umbraco-forms/developer/ajaxforms.md
index d6cccd7def0..8e543a49e1c 100644
--- a/16/umbraco-forms/developer/ajaxforms.md
+++ b/16/umbraco-forms/developer/ajaxforms.md
@@ -538,7 +538,7 @@ With this in place any request to the Forms API will be rejected unless the conf
## Rendering and Submitting forms with JavaScript
-For an illustrative example showing how a form can be rendered, validated and submitted using the API and vanilla JavaScript, please [see this gist](https://gist.github.com/AndyButland/9371175d6acf24a5307b053398f08448).
+For an illustrative example showing how a form can be rendered, validated and submitted using the API and vanilla JavaScript, [see this gist](https://gist.github.com/AndyButland/9371175d6acf24a5307b053398f08448).
Examples demonstrating how to handle a file upload and use reCAPTCHA fields are included.
diff --git a/16/umbraco-forms/developer/healthchecks/README.md b/16/umbraco-forms/developer/healthchecks/README.md
index d9b34c2e10b..1caffa0ba07 100644
--- a/16/umbraco-forms/developer/healthchecks/README.md
+++ b/16/umbraco-forms/developer/healthchecks/README.md
@@ -53,7 +53,7 @@ To support this, we provide the following SQL scripts:
The first of these provides the SQL statements required to apply the schema updates for 8.7.0+ to the common Umbraco Forms tables. The second applies to those tables used for when Forms are stored in the database, and hence only need to be applied if that option is configured.
{% hint style="info" %}
-Before running any scripts or queries, please be sure to have a database backup in place.
+Before running any scripts or queries, be sure to have a database backup in place.
{% endhint %}
To take an example, let's say that via the health check results you can see that the _"Unique constraint on table 'UFForms', column 'Key' is missing."_
diff --git a/16/umbraco-forms/installation/the-licensing-model.md b/16/umbraco-forms/installation/the-licensing-model.md
index f949079441a..9e702f133c1 100644
--- a/16/umbraco-forms/installation/the-licensing-model.md
+++ b/16/umbraco-forms/installation/the-licensing-model.md
@@ -104,7 +104,7 @@ This will also change the location for other Umbraco-related licenses in this pr
The algorithm used to decrypt Forms licenses is not supported on locked down FIPS compliant environments, such as those used in the defense industry.
-If you are in this situation and unable to resolve it via configuration of the environment, please reach out to Umbraco support.
+If you are in this situation and unable to resolve it via configuration of the environment, reach out to Umbraco Support.
We have the possibility of generating and providing Forms licenses using alternate algorithms.
diff --git a/17/umbraco-cms/customizing/extending-overview/extension-types/entity-actions.md b/17/umbraco-cms/customizing/extending-overview/extension-types/entity-actions.md
index 2554b0a6cac..9408aaad8c4 100644
--- a/17/umbraco-cms/customizing/extending-overview/extension-types/entity-actions.md
+++ b/17/umbraco-cms/customizing/extending-overview/extension-types/entity-actions.md
@@ -147,7 +147,7 @@ Here is a list of the entity actions and associated user permission codes shippe
If you are building a package or adding custom entity actions to your solution, it's important to pick a permission letter. Ensure that it doesn't clash with one of these.
-If you have created a package using a custom entity action, please consider providing an update to this documentation page. You can do this via a PR to the [documentation repository](https://github.com/umbraco/UmbracoDocs). This will allow other developers to discover and avoid using the same permission letter.
+If you have created a package using a custom entity action, consider providing an update to this documentation page. You can do this via a PR to the [documentation repository](https://github.com/umbraco/UmbracoDocs). This will allow other developers to discover and avoid using the same permission letter.
Currently, we allow two extension points on the client for user permissions:
diff --git a/17/umbraco-cms/customizing/extending-overview/extension-types/tree.md b/17/umbraco-cms/customizing/extending-overview/extension-types/tree.md
index a7da343a01c..f4b813dc8b1 100644
--- a/17/umbraco-cms/customizing/extending-overview/extension-types/tree.md
+++ b/17/umbraco-cms/customizing/extending-overview/extension-types/tree.md
@@ -7,7 +7,7 @@ description: A guide to creating a custom tree in Umbraco
The tree is a hierarchical structure of nodes and is registered in the Backoffice extension registry. A tree can be rendered anywhere in the Backoffice with the help of the ` ` element.
{% hint style="info" %}
-To see how to register a tree as a menu in a section, please refer to the [Section Sidebar](./sections/section-sidebar.md) article.
+To see how to register a tree as a menu in a section, refer to the [Section Sidebar](./sections/section-sidebar.md) article.
{% endhint %}
## Creating trees
diff --git a/17/umbraco-cms/customizing/property-editors/property-editor-validation.md b/17/umbraco-cms/customizing/property-editors/property-editor-validation.md
index b78c8af6085..c670a4e4066 100644
--- a/17/umbraco-cms/customizing/property-editors/property-editor-validation.md
+++ b/17/umbraco-cms/customizing/property-editors/property-editor-validation.md
@@ -68,7 +68,7 @@ The third argument is the Validator check, which is executed every time there is
If you're looking to make server requests as part of your check, then it is recommended to avoid calling the server more often than needed. Do only ask the server if there is a value, and only ask the server again if the value is different from last time.
{% endhint %}
-Notice that `value` is already defined in the FormControlMixin, and ideally, you do not overwrite it. If so, then please make sure to still set the value property of the Mixin. As that will trigger a validation update.
+Notice that `value` is already defined in the FormControlMixin, and ideally, you do not overwrite it. If so, then make sure to still set the value property of the Mixin. As that will trigger a validation update.
```typescript
@property({ type: String })
diff --git a/17/umbraco-cms/extending/flag-providers.md b/17/umbraco-cms/extending/flag-providers.md
index ac263b1ba41..0497b50f22f 100644
--- a/17/umbraco-cms/extending/flag-providers.md
+++ b/17/umbraco-cms/extending/flag-providers.md
@@ -84,7 +84,7 @@ The flag provider needs to be registered with Umbraco in a composer or applicati
For some flags, there may be sufficient information on the view models to map whether a flag should be created.
-For an example of this, please see the core flag provider `IsProtectedFlagProvider` whose [source code can be found here](https://github.com/umbraco/Umbraco-CMS/blob/main/src/Umbraco.Cms.Api.Management/Services/Flags/IsProtectedFlagProvider.cs).
+For an example of this, see the core flag provider `IsProtectedFlagProvider` whose [source code can be found here](https://github.com/umbraco/Umbraco-CMS/blob/main/src/Umbraco.Cms.Api.Management/Services/Flags/IsProtectedFlagProvider.cs).
More complex flags will require additional information, using the identifiers of the view models to retrieve the necessary data. It's important to avoid "N+1" issues. The aim should be to retrieve all the data needed to populate the flags for the whole collection in one step.
diff --git a/17/umbraco-cms/extending/health-check/README.md b/17/umbraco-cms/extending/health-check/README.md
index 2b03622e5ee..10a319a2086 100644
--- a/17/umbraco-cms/extending/health-check/README.md
+++ b/17/umbraco-cms/extending/health-check/README.md
@@ -188,7 +188,7 @@ Disallow: /umbraco/";
## Custom health check notifications
-Health check notifications can be scheduled to run periodically and notify you of the results. Included with Umbraco is a notification method to deliver the results via email. In a similar manner to how it's possible to create your health checks, you can also create custom notification methods to send the message summarising the status of the health checks via other means. Again, for further details on implementing this please refer to the [existing notification methods within the core code base](https://github.com/umbraco/Umbraco-CMS/tree/v10/dev/src/Umbraco.Core/HealthChecks/NotificationMethods).
+Health check notifications can be scheduled to run periodically and notify you of the results. Included with Umbraco is a notification method to deliver the results via email. In a similar manner to how it's possible to create your health checks, you can also create custom notification methods to send the message summarising the status of the health checks via other means. Again, for further details on implementing this, refer to the [existing notification methods within the core code base](https://github.com/umbraco/Umbraco-CMS/tree/v10/dev/src/Umbraco.Core/HealthChecks/NotificationMethods).
Each notification method needs to implement the core interface `IHealthCheckNotificationMethod` and, for ease of creation, can inherit from the base class `NotificationMethodBase`, which itself implements the `IHealthCheckNotificationMethod` interface. The class must also be decorated with an instance of the `HealthCheckNotificationMethod` attribute. There's one method to implement - `SendAsync(HealthCheckResults results)` - which is responsible for taking the results of the health checks and sending them via the mechanism of your choice.
diff --git a/17/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/block-editor/block-list-editor.md b/17/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/block-editor/block-list-editor.md
index 9cf61753613..f165d5af418 100644
--- a/17/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/block-editor/block-list-editor.md
+++ b/17/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/block-editor/block-list-editor.md
@@ -139,7 +139,7 @@ These partial views must be placed in this folder: `Views/Partials/BlockList/Com
A Partial View will receive the model of `Umbraco.Core.Models.Blocks.BlockListItem`. This gives you the option to access properties of the Content and Settings section of your Block.
-In the following example of a Partial view for a Block Type, please note that the `MyElementTypeAliasOfContent`and `MyElementTypeAliasOfSettings` should correspond with the selected Element Type Alias for the given model in your case.
+In the following example of a Partial view for a Block Type, the `MyElementTypeAliasOfContent`and `MyElementTypeAliasOfSettings` should correspond with the selected Element Type Alias for the given model in your case.
Example:
diff --git a/17/umbraco-cms/fundamentals/setup/server-setup/running-umbraco-in-docker.md b/17/umbraco-cms/fundamentals/setup/server-setup/running-umbraco-in-docker.md
index 928204cfc13..18256c7e011 100644
--- a/17/umbraco-cms/fundamentals/setup/server-setup/running-umbraco-in-docker.md
+++ b/17/umbraco-cms/fundamentals/setup/server-setup/running-umbraco-in-docker.md
@@ -35,7 +35,7 @@ You may prefer to avoid writing to disk for logs when hosting in containers. If
You can also provide an alternative implementation of a common abstraction for the log viewer. In this way you can read logs from the location where you have configured them to be written.
-For more on this please read the article on Umbraco's [log viewer](../../backoffice/logviewer.md).
+For more details, read the article on Umbraco's [log viewer](../../backoffice/logviewer.md).
### Data
diff --git a/17/umbraco-cms/fundamentals/setup/upgrading/version-specific/README.md b/17/umbraco-cms/fundamentals/setup/upgrading/version-specific/README.md
index 0a3f53b5ee5..0cb88cb46b4 100644
--- a/17/umbraco-cms/fundamentals/setup/upgrading/version-specific/README.md
+++ b/17/umbraco-cms/fundamentals/setup/upgrading/version-specific/README.md
@@ -291,7 +291,7 @@ Below you can find the list of breaking changes introduced in Umbraco 14 CMS.
* [**AngularJS removed: A new backoffice built with Web Components, Lit, and fueled by the Umbraco UI Library**](https://github.com/umbraco/Umbraco.CMS.Backoffice)
-This is by far the most impactful update of Umbraco in years. We’ve fundamentally changed the way you extend Umbraco. If you are experienced in developing Web Components you can now use your preferred framework for this. If you are unsure how to proceed, you can implement it with TypeScript and the Lit library like we’ve done. In this case, please start with this article on how to [customize the Backoffice](https://docs.umbraco.com/umbraco-cms/customizing/overview).
+This is by far the most impactful update of Umbraco in years. We’ve fundamentally changed the way you extend Umbraco. If you are experienced in developing Web Components you can now use your preferred framework for this. If you are unsure how to proceed, you can implement it with TypeScript and the Lit library like we’ve done. In this case, start with this article on how to [customize the Backoffice](https://docs.umbraco.com/umbraco-cms/customizing/overview).
The new Backoffice (Bellissima) is entirely built on the Umbraco UI Library. This means that you might experience some of your components not being rendered on the page because the name has been changed. You should be able to find equivalents to what you were used to. For example, the `umb-button` is now called `uui-button`, and `umb-box` is now `uui-box`. When extending the Backoffice, we encourage you to use our [Umbraco UI Library](https://uui.umbraco.com/) to ensure the same look and feel in your extensions. The UI Library is Open Source and [hosted on GitHub](https://github.com/umbraco/Umbraco.UI), so feel free to contribute with new components or raise issues or discussions.
@@ -315,7 +315,7 @@ Following the implementation of the new Backoffice (Bellissima), Umbraco has now
* **A new way of writing authorized controllers**
-If you have implemented API controllers in Umbraco before, we recommend you update or rewrite these. Please follow the [Documenting your Controllers](https://docs.umbraco.com/umbraco-cms/tutorials/creating-a-backoffice-api/documenting-your-controllers) article, as you’ll then ensure the same cool documentation of your APIs. Notice, that we’ve made a much better separation of concern between controllers and services so that there is no more business logic in controllers.
+If you have implemented API controllers in Umbraco before, we recommend you update or rewrite these. Follow the [Documenting your Controllers](https://docs.umbraco.com/umbraco-cms/tutorials/creating-a-backoffice-api/documenting-your-controllers) article, as you’ll then ensure the same cool documentation of your APIs. Notice, that we’ve made a much better separation of concern between controllers and services so that there is no more business logic in controllers.
* [**Migration from Newtonsoft.Json to the System.Text.Json which removes Nested Content and Grid value converter and so on**](https://github.com/umbraco/Umbraco-CMS/pull/15728)
@@ -348,7 +348,7 @@ The `package.manifest` file is no longer supported and has been replaced with th
It's recommended that you bundle up your Backoffice static assets for instance by a tool called Vite. You can read more about this on the [Vite Package Setup](https://docs.umbraco.com/umbraco-cms/customizing/development-flow/vite-package-setup) article. You can still use libraries like Smidge for frontend static assets by manually installing the package from NuGet.
You can read the [Smidge documentation](https://github.com/Shazwazza/Smidge/wiki) on how to set up a similar setting to RuntimeMinification.
-For sites being upgraded from V13 or below, please remove [these two lines](https://github.com/umbraco/Umbraco-CMS/blob/04ed514a21279ae82d95b34c55cb2ba96545eb39/src/Umbraco.Web.UI/Views/_ViewImports.cshtml#L7-L8) from the `_ViewImports.cshtml` file.
+For sites being upgraded from V13 or below, remove [these two lines](https://github.com/umbraco/Umbraco-CMS/blob/04ed514a21279ae82d95b34c55cb2ba96545eb39/src/Umbraco.Web.UI/Views/_ViewImports.cshtml#L7-L8) from the `_ViewImports.cshtml` file.
* **Base classes for Backoffice controllers have been removed**
diff --git a/17/umbraco-cms/reference/content-delivery-api/extension-api-for-querying.md b/17/umbraco-cms/reference/content-delivery-api/extension-api-for-querying.md
index 5c3634ca917..678a51b0fb9 100644
--- a/17/umbraco-cms/reference/content-delivery-api/extension-api-for-querying.md
+++ b/17/umbraco-cms/reference/content-delivery-api/extension-api-for-querying.md
@@ -6,7 +6,7 @@ description: >-
# Extension API for querying
-The Delivery API allows you to retrieve multiple items by utilizing the `/umbraco/delivery/api/v2/content` endpoint. With the built-in query parameters, you have the flexibility to get any number of content nodes based on your needs. For a comprehensive list of supported query options, please refer to the [Endpoints](./#endpoints) section.
+The Delivery API allows you to retrieve multiple items by utilizing the `/umbraco/delivery/api/v2/content` endpoint. With the built-in query parameters, you have the flexibility to get any number of content nodes based on your needs. For a comprehensive list of supported query options, refer to the [Endpoints](./#endpoints) section.
For the query endpoint, we have created a new Examine index (_DeliveryApiContentIndex_) that facilitates fast retrieval of the desired content. This index ensures quick indexing and searching of data, with the possibility for future extensions.
diff --git a/17/umbraco-cms/reference/content-delivery-api/media-delivery-api.md b/17/umbraco-cms/reference/content-delivery-api/media-delivery-api.md
index b271bb768ea..c2616fd1ee9 100644
--- a/17/umbraco-cms/reference/content-delivery-api/media-delivery-api.md
+++ b/17/umbraco-cms/reference/content-delivery-api/media-delivery-api.md
@@ -4,7 +4,7 @@ description: Using the Media Delivery API.
# Media Delivery API
-The Media Delivery API allows for accessing the Umbraco media items in a headless manner. This API applies many of the same concepts as its content counterpart, although with fewer options. If you haven't already, please familiarize yourself with the [Content Delivery API](https://docs.umbraco.com/umbraco-cms/reference/content-delivery-api) before reading this article.
+The Media Delivery API allows for accessing the Umbraco media items in a headless manner. This API applies many of the same concepts as its content counterpart, although with fewer options. If you haven't already, familiarize yourself with the [Content Delivery API](https://docs.umbraco.com/umbraco-cms/reference/content-delivery-api) before reading this article.
{% hint style="info" %}
The Media Delivery API specification is created to mimic that of the Content Delivery API. However, the default implementation of this specification is limited and does not support the entire specification.
@@ -168,7 +168,7 @@ Returns single or multiple items.
{% swagger-parameter in="query" name="fetch" type="String" required="true" %}
Structural query string option (e.g. `ancestors`, `children`, `descendants`).
-**Please note:** The default API implementation only supports `children`.
+**Note:** The default API implementation only supports `children`.
{% endswagger-parameter %}
{% swagger-parameter in="query" name="filter" type="String Array" required="false" %}
diff --git a/17/umbraco-cms/reference/content-delivery-api/property-expansion-and-limiting.md b/17/umbraco-cms/reference/content-delivery-api/property-expansion-and-limiting.md
index 21bb3108cd3..17e6074c7fe 100644
--- a/17/umbraco-cms/reference/content-delivery-api/property-expansion-and-limiting.md
+++ b/17/umbraco-cms/reference/content-delivery-api/property-expansion-and-limiting.md
@@ -5,7 +5,7 @@ description: Using property expansion and limiting to shape the Delivery API out
# Property expansion and limiting
{% hint style="info" %}
-This article explains the mechanics of property expansion and limiting in depth. If you haven't already, please read the [Getting started](https://docs.umbraco.com/umbraco-cms/reference/content-delivery-api) article first - in particular the "Concepts" section.
+This article explains the mechanics of property expansion and limiting in depth. If you haven't already, read the [Getting started](https://docs.umbraco.com/umbraco-cms/reference/content-delivery-api) article first - in particular the "Concepts" section.
{% endhint %}
Property expansion and limiting applies only to select property editors. The following built-in property editors in Umbraco support expansion and limiting:
@@ -537,7 +537,7 @@ Start-Item: posts
## Working with block-based editors
{% hint style="info" %}
-If you are not familiar with block-based editors, please refer to [this article](https://docs.umbraco.com/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/block-editor) for the general concepts of these.
+If you are not familiar with block-based editors, refer to the [Block Editor article](https://docs.umbraco.com/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/block-editor).
{% endhint %}
In the API output, a block has little value without its contained properties. Therefore, the content and settings properties of blocks are always included in the output. However, these properties are not expanded. As such, we can apply expansion and limiting to the contained properties.
diff --git a/17/umbraco-cms/reference/content-delivery-api/protected-content-in-the-delivery-api/README.md b/17/umbraco-cms/reference/content-delivery-api/protected-content-in-the-delivery-api/README.md
index 15637eb088a..922f558f93b 100644
--- a/17/umbraco-cms/reference/content-delivery-api/protected-content-in-the-delivery-api/README.md
+++ b/17/umbraco-cms/reference/content-delivery-api/protected-content-in-the-delivery-api/README.md
@@ -10,12 +10,12 @@ Umbraco allows for restricting access to content. Using the "Public access" feat
By default, protected content is ignored by the Delivery API, and is never exposed through any API endpoints. However, by enabling member authorization in the Delivery API, protected content can be accessed by means of access tokens.
{% hint style="info" %}
-If you are not familiar with members in Umbraco, please read the [Members](../../../fundamentals/data/members.md) article.
+If you are not familiar with members in Umbraco, read the [Members](../../../fundamentals/data/members.md) article.
{% endhint %}
{% hint style="info" %}
This article describes how to access protected content in a client-to-server context, using an interactive authorization flow.\
-If you are looking to achieve server-to-server access to protected content, please refer to [server-to-server access article](server-to-server-access.md) instead.
+If you are looking to achieve server-to-server access to protected content, refer to [server-to-server access article](server-to-server-access.md) instead.
{% endhint %}
## Member authorization
@@ -329,7 +329,7 @@ Access tokens expire after one hour. Once expired, a new access token must be ob
Refresh tokens provide a means to obtain a new access token without having to go through the authentication flow. A refresh token is issued automatically by the Delivery API when the `offline_access` scope is specified in the authorization request.
{% hint style="info" %}
-Refresh tokens are subject to certain limitations and can result in security issues if not applied correctly. All this is beyond the scope of this article to explain in detail. Please familiarize yourself with the inner workings of refresh tokens before applying them in a solution.
+Refresh tokens are subject to certain limitations and can result in security issues if not applied correctly. All this is beyond the scope of this article to explain in detail. Familiarize yourself with the inner workings of refresh tokens before applying them in a solution.
{% endhint %}
## Logging out members
@@ -409,7 +409,7 @@ Remember to use `umbraco-member` as `client_id` when authorizing. `client_secret
## Client configuration samples
The following samples show how to configure an ASP.NET Core client to utilize member authorization in the Delivery API.\
-To put these samples into context, please refer to the article above.
+To put these samples into context, refer to the article above.
### Basic client configuration
diff --git a/17/umbraco-cms/reference/management-api/external-access.md b/17/umbraco-cms/reference/management-api/external-access.md
index 7c7aebc79e0..a1971701717 100644
--- a/17/umbraco-cms/reference/management-api/external-access.md
+++ b/17/umbraco-cms/reference/management-api/external-access.md
@@ -22,7 +22,7 @@ The token endpoint response looks like this:
As shown, the access token should be used as a Bearer token when consuming the Management API.
-Also, notice that access tokens have a fixed expiry. While you can keep issuing new tokens for the Client Credentials, please reuse tokens within their lifespan. This will be more performant and avoid flooding the Umbraco database with tokens.
+Also, notice that access tokens have a fixed expiry. While you can keep issuing new tokens for the Client Credentials, reuse tokens within their lifespan. This will be more performant and avoid flooding the Umbraco database with tokens.
{% hint style="info" %}
The Management API does not support OpenID Connect Discovery. This is reserved for Members accessing protected content via the [Delivery API](../content-delivery-api/protected-content-in-the-delivery-api/README.md).
diff --git a/17/umbraco-cms/reference/searching/examine/indexing.md b/17/umbraco-cms/reference/searching/examine/indexing.md
index 088c3013f54..96b5d54ed95 100644
--- a/17/umbraco-cms/reference/searching/examine/indexing.md
+++ b/17/umbraco-cms/reference/searching/examine/indexing.md
@@ -335,7 +335,7 @@ The index will only update its content when you manually trigger an index rebuil
To update your index when content changes, you can use notification handlers.
{% hint style="info" %}
-The following handler class does not automatically update the descendant items of the modified content nodes, such as removing descendants of deleted content. If changes to the parent content item can affect its children or descendant items in your setup, please refer to the [UmbracoContentIndex.PerformDeleteFromIndex() in Umbraco](https://github.com/umbraco/Umbraco-CMS/blob/main/src/Umbraco.Examine.Lucene/UmbracoContentIndex.cs#L124-L153). Such logic should be applied when both removing and reindexing content items of type _product_.
+The following handler class does not automatically update the descendant items of the modified content nodes, such as removing descendants of deleted content. If changes to the parent content item can affect its children or descendant items in your setup, refer to the [UmbracoContentIndex.PerformDeleteFromIndex() in Umbraco](https://github.com/umbraco/Umbraco-CMS/blob/main/src/Umbraco.Examine.Lucene/UmbracoContentIndex.cs#L124-L153). Such logic should be applied when both removing and reindexing content items of type _product_.
{% endhint %}
```csharp
diff --git a/17/umbraco-cms/tutorials/editors-manual/tips-and-tricks/notifications.md b/17/umbraco-cms/tutorials/editors-manual/tips-and-tricks/notifications.md
index be32d2bdce6..a6b81f520e0 100644
--- a/17/umbraco-cms/tutorials/editors-manual/tips-and-tricks/notifications.md
+++ b/17/umbraco-cms/tutorials/editors-manual/tips-and-tricks/notifications.md
@@ -18,5 +18,5 @@ The notification settings apply to the chosen content item as well as any child
{% endhint %}
{% hint style="info" %}
-If the notifications option does not appear, the SMTP settings are probably incorrect. In this case please contact the administrator of your website.
+If the notifications option does not appear, the SMTP settings are probably incorrect. In this case, contact the administrator of your website.
{% endhint %}
diff --git a/17/umbraco-commerce/changelog-archive/Vendr-core.md b/17/umbraco-commerce/changelog-archive/Vendr-core.md
index 2de685aae2f..6f971d0b029 100644
--- a/17/umbraco-commerce/changelog-archive/Vendr-core.md
+++ b/17/umbraco-commerce/changelog-archive/Vendr-core.md
@@ -559,7 +559,7 @@ description: Changelog for the Core Vendr product
**Date:** 2020-12-10\
**Description:** Major breaking changes release
-For more details on this release, including a recommended upgrade strategy, please see the [Vendr 1.4.0 RC blog post](https://vendr.net/blog/vendr-1-4-0-release-candidate/).
+For more details on this release, including a recommended upgrade strategy, see the [Vendr 1.4.0 RC blog post](https://vendr.net/blog/vendr-1-4-0-release-candidate/).
* Added price adjustments/adjusters.
* Added amount adjustments/adjusters.
diff --git a/17/umbraco-deploy/extending/handling-cache-refresher-notifications.md b/17/umbraco-deploy/extending/handling-cache-refresher-notifications.md
index 4568be36f3a..155c1bdb382 100644
--- a/17/umbraco-deploy/extending/handling-cache-refresher-notifications.md
+++ b/17/umbraco-deploy/extending/handling-cache-refresher-notifications.md
@@ -27,7 +27,7 @@ The following two code samples illustrate how this can be done.
The first handles a content cache refresher, which takes a payload from where the content ID can be extracted. Using that the content can be retrieved in the local Umbraco instance and used as appropriate.
-For more details and further examples, please see the [CMS Cache Refresher Notifications documentation](https://docs.umbraco.com/umbraco-cms/reference/notifications/cacherefresher-notifications).
+For more details and further examples, see the [CMS Cache Refresher Notifications documentation](https://docs.umbraco.com/umbraco-cms/reference/notifications/cacherefresher-notifications).
```csharp
using Umbraco.Cms.Core.Cache;
diff --git a/17/umbraco-engage/developers/analytics/client-side-events-and-additional-javascript-files/bridging-library-for-google-analytics.md b/17/umbraco-engage/developers/analytics/client-side-events-and-additional-javascript-files/bridging-library-for-google-analytics.md
index 2aca9afb5de..bf92135f530 100644
--- a/17/umbraco-engage/developers/analytics/client-side-events-and-additional-javascript-files/bridging-library-for-google-analytics.md
+++ b/17/umbraco-engage/developers/analytics/client-side-events-and-additional-javascript-files/bridging-library-for-google-analytics.md
@@ -65,7 +65,7 @@ The captured GA4 events will appear in Analytics -> Events in the **GA 4 - Bridg
### Using GA4 events in Goals
-If you want to trigger a goal based on a GA4 event please use the following information:
+If you want to trigger a goal based on a GA4 event, use the following information:
-Category: **GA 4 Bridging**\
+Category: **GA 4 Bridging**
Action: **\**
diff --git a/17/umbraco-engage/installation/installation.md b/17/umbraco-engage/installation/installation.md
index e28d8d50145..63b52e5efe3 100644
--- a/17/umbraco-engage/installation/installation.md
+++ b/17/umbraco-engage/installation/installation.md
@@ -52,7 +52,7 @@ dotnet add package Umbraco.Engage
```
{% hint style="info" %}
-If you have any trouble, please go to [Troubleshooting installs](troubleshooting-installs.md).
+If you have any trouble, go to [Troubleshooting installs](troubleshooting-installs.md).
{% endhint %}
## Next steps
@@ -137,7 +137,7 @@ If you [change the default cookie behavior](../developers/introduction/the-umbra
### Load balancing and CM / CD environments
-Are you using a load-balanced setup or separate CM and CD environments? [Please check our documentation about this topic](../getting-started/for-developers/loadbalancing-and-cm-cd-environments.md).
+Are you using a load-balanced setup or separate CM and CD environments? [Check our documentation about this topic](../getting-started/for-developers/loadbalancing-and-cm-cd-environments.md).
### The first run
diff --git a/17/umbraco-engage/installation/troubleshooting-installs.md b/17/umbraco-engage/installation/troubleshooting-installs.md
index 2c7fc0f5658..e71cb8d74df 100644
--- a/17/umbraco-engage/installation/troubleshooting-installs.md
+++ b/17/umbraco-engage/installation/troubleshooting-installs.md
@@ -12,7 +12,7 @@ If you have problems with Umbraco Engage setup or configuration, this checklist
After logging in to Umbraco, you can see the Engage section next to the other main sections in the Umbraco backoffice.
-If you cannot see this, please check if your Umbraco user or user group has access to the Engage section.
+If you cannot see this, check if your Umbraco user or user group has access to the Engage section.

diff --git a/17/umbraco-engage/marketers-and-editors/settings/setting-up-goals.md b/17/umbraco-engage/marketers-and-editors/settings/setting-up-goals.md
index 924a0d1d497..c85a436440c 100644
--- a/17/umbraco-engage/marketers-and-editors/settings/setting-up-goals.md
+++ b/17/umbraco-engage/marketers-and-editors/settings/setting-up-goals.md
@@ -35,9 +35,9 @@ You can specify how the goal will be triggered:
* Via a pageview/set of pages that are visited
* Via a page event that can be triggered
- * If you want to trigger a goal based on a GA4 event please use the following information:
+ * If you want to trigger a goal based on a GA4 event, use the following information:
- Category: **GA 4 Bridging**\
+ Category: **GA 4 Bridging**
Action: **\**
* Via an Umbraco Forms submission
* Via some custom code
diff --git a/17/umbraco-engage/upgrading/migrate-from-umarketingsuite.md b/17/umbraco-engage/upgrading/migrate-from-umarketingsuite.md
index 6ede83b170a..360d5a512a8 100644
--- a/17/umbraco-engage/upgrading/migrate-from-umarketingsuite.md
+++ b/17/umbraco-engage/upgrading/migrate-from-umarketingsuite.md
@@ -63,7 +63,7 @@ Run this script on your locally restored database to prepare for the migration.
3. Verify that the uMarketingSuite table integrity check returns the expected results.
{% hint style="info" %}
-If any of these checks return a failure, please resolve the issue before proceeding with the migration.
+If any of these checks return a failure, resolve the issue before proceeding with the migration.
{% endhint %}
The result should look like this:
@@ -79,7 +79,7 @@ The result should look like this:
---Finished running Pre-Requisite Checks. Please verify if all 5 checks succeeded before proceeding---
```
-If any of these checks return a failure, please resolve the issue before proceeding with the migration.
+If any of these checks return a failure, resolve the issue before proceeding with the migration.
## Step 3: Replace NuGet packages and dependencies
@@ -139,7 +139,7 @@ dotnet add package Umbraco.Engage.Commerce
Based on the [Key Changes](migrate-from-umarketingsuite.md#key-changes) below update all uMarketingSuite references to the new Umbraco Engage alternatives. Ensure you update any Views/Partials that also reference these. This includes the different uMarketingSuite clientside scripts (like the analytics & ga4-bridge) and the Cockpit.
-Please find below an overview of the changes to the default scripts in a uMarketingSuite installation:
+Find below an overview of the changes to the default scripts in a uMarketingSuite installation:
* Rename scripts & Asset Paths containing the `uMarketingSuite` keyword to:
* `Assets/Umbraco.Engage/Scripts/umbracoEngage.analytics.js`
@@ -147,7 +147,7 @@ Please find below an overview of the changes to the default scripts in a uMarket
* `Assets/Umbraco.Engage/Scripts/umbracoEngage.analytics.blockerdetection.js`
* The Cockpit partial view has been moved, and any references should be changed to:
* `Partials/Umbraco.Engage/Cockpit`
-* If you are tracking custom events please make sure to update the calls to the send event method:
+* If you are tracking custom events, make sure to update the calls to the send event method:
* `ums("send", "event", "", "", "")`
is now:
@@ -376,7 +376,7 @@ dotnet add package Umbraco.Engage.Forms
If you are using the uMarketingSuite.Headless package, applications that use the uMarketingSuite API will need to be updated. This needs to happen to be able to use the new Umbraco Engage API, accessible via the `/umbraco/engage/api/` routes.
-The v1 Engage APIs (v13.0.0 of Umbraco Engage) maintain the same functionality as the v1 uMarketingSuite APIs. For more details on the API, please refer to the Swagger documentation provided by Umbraco Engage.
+The v1 Engage APIs (v13.0.0 of Umbraco Engage) maintain the same functionality as the v1 uMarketingSuite APIs. For more details on the API, refer to the Swagger documentation provided by Umbraco Engage.
You can install the Umbraco Engage Headless add-on package using the following command:
diff --git a/17/umbraco-forms/developer/ajaxforms.md b/17/umbraco-forms/developer/ajaxforms.md
index 7bb2810dcf6..3b0ead12240 100644
--- a/17/umbraco-forms/developer/ajaxforms.md
+++ b/17/umbraco-forms/developer/ajaxforms.md
@@ -538,7 +538,7 @@ With this in place any request to the Forms API will be rejected unless the conf
## Rendering and Submitting forms with JavaScript
-For an illustrative example showing how a form can be rendered, validated and submitted using the API and vanilla JavaScript, please [see this gist](https://gist.github.com/AndyButland/9371175d6acf24a5307b053398f08448).
+For an illustrative example showing how a form can be rendered, validated and submitted using the API and vanilla JavaScript, [see this gist](https://gist.github.com/AndyButland/9371175d6acf24a5307b053398f08448).
Examples demonstrating how to handle a file upload and use reCAPTCHA fields are included.
diff --git a/17/umbraco-forms/developer/healthchecks/README.md b/17/umbraco-forms/developer/healthchecks/README.md
index d9b34c2e10b..1caffa0ba07 100644
--- a/17/umbraco-forms/developer/healthchecks/README.md
+++ b/17/umbraco-forms/developer/healthchecks/README.md
@@ -53,7 +53,7 @@ To support this, we provide the following SQL scripts:
The first of these provides the SQL statements required to apply the schema updates for 8.7.0+ to the common Umbraco Forms tables. The second applies to those tables used for when Forms are stored in the database, and hence only need to be applied if that option is configured.
{% hint style="info" %}
-Before running any scripts or queries, please be sure to have a database backup in place.
+Before running any scripts or queries, be sure to have a database backup in place.
{% endhint %}
To take an example, let's say that via the health check results you can see that the _"Unique constraint on table 'UFForms', column 'Key' is missing."_
diff --git a/17/umbraco-forms/installation/the-licensing-model.md b/17/umbraco-forms/installation/the-licensing-model.md
index b159ebf046d..301aa9fd41e 100644
--- a/17/umbraco-forms/installation/the-licensing-model.md
+++ b/17/umbraco-forms/installation/the-licensing-model.md
@@ -104,7 +104,7 @@ This will also change the location for other Umbraco-related licenses in this pr
The algorithm used to decrypt Forms licenses is not supported on locked down FIPS compliant environments, such as those used in the defense industry.
-If you are in this situation and unable to resolve it via configuration of the environment, please reach out to Umbraco support.
+If you are in this situation and unable to resolve it via configuration of the environment, reach out to Umbraco Support.
We have the possibility of generating and providing Forms licenses using alternate algorithms.
diff --git a/commerce-add-ons/packages/cart/README.md b/commerce-add-ons/packages/cart/README.md
index 178f1b3494d..6624d27650c 100644
--- a/commerce-add-ons/packages/cart/README.md
+++ b/commerce-add-ons/packages/cart/README.md
@@ -12,7 +12,7 @@ Umbraco Commerce Cart allows you to set up your shopping cart with minimal devel
In this section, you will learn the key steps necessary to get started with the Cart package for Umbraco Commerce.
-It is assumed that you already have an Umbraco website configured, Umbraco Commerce installed and a store set up. If you are not at this stage yet, please read the [core Umbraco Commerce documentation](https://docs.umbraco.com/umbraco-commerce/) to learn how to get started.
+It is assumed that you already have an Umbraco website configured, Umbraco Commerce installed and a store set up. If you are not at this stage yet, read the [core Umbraco Commerce documentation](https://docs.umbraco.com/umbraco-commerce/) to learn how to get started.
## Useful links
diff --git a/commerce-add-ons/packages/checkout/README.md b/commerce-add-ons/packages/checkout/README.md
index 29b5e74f3e5..bb056220dda 100644
--- a/commerce-add-ons/packages/checkout/README.md
+++ b/commerce-add-ons/packages/checkout/README.md
@@ -12,11 +12,11 @@ Umbraco Commerce Checkout allows you to set up your checkout flow with minimal c
In this section, we will guide you through the key steps necessary to get you started with the Checkout package for Umbraco Commerce.
-It is assumed that before we begin that you already have an Umbraco website configured and Umbraco Commerce installed and a store set up. If you are not at this stage yet, please read the [core Umbraco Commerce documentation](https://docs.umbraco.com/umbraco-commerce/) to learn how to get started.
+It is assumed that before we begin that you already have an Umbraco website configured and Umbraco Commerce installed and a store set up. If you are not at this stage yet, read the [core Umbraco Commerce documentation](https://docs.umbraco.com/umbraco-commerce/) to learn how to get started.
## Useful links
-As well as the content in these docs, here are a few useful links to learn more about the Umbraco Commerce Checkout package itself.
+As well as the content in these documentation, here are a few useful links to learn more about the Umbraco Commerce Checkout package itself.
* [Umbraco Commerce Checkout source code](https://github.com/umbraco/Umbraco.Commerce.Checkout)
* [Umbraco Commerce Checkout issue tracker](https://github.com/umbraco/Umbraco.Commerce.Checkout/issues)
diff --git a/commerce-add-ons/packages/checkout/customize-checkout.md b/commerce-add-ons/packages/checkout/customize-checkout.md
index c234908645d..ef4af0c4067 100644
--- a/commerce-add-ons/packages/checkout/customize-checkout.md
+++ b/commerce-add-ons/packages/checkout/customize-checkout.md
@@ -4,17 +4,17 @@ description: This documentation shows how to customize the Checkout package for
# Customize Checkout
-It is assumed that you already have an Umbraco website configured Umbraco Commerce installed and a store set up. If you are not at this stage yet, please read the [core Umbraco Commerce documentation](https://docs.umbraco.com/umbraco-commerce/) to learn how to get started.
+It is assumed that you already have an Umbraco website configured Umbraco Commerce installed and a store set up. If you are not at this stage yet, read the [core Umbraco Commerce documentation](https://docs.umbraco.com/umbraco-commerce/) to learn how to get started.
Umbraco Commerce Checkout is a free and open-source add-on package for Umbraco Commerce. It is possible to amend the default behavior to customize the checkout to your needs.
## Setup
-To allow customization you must first 'override' the existing files for the step required to be modified.
+To allow customization you must first 'override' the existing files for the step required to be modified.
To do this follow these steps:
-1. Copy the equivalent [files and partials](https://github.com/umbraco/Umbraco.Commerce.Checkout/tree/main/src/Umbraco.Commerce.Checkout/Views/UmbracoCommerceCheckout).
+1. Copy the equivalent [files and partials](https://github.com/umbraco/Umbraco.Commerce.Checkout/tree/main/src/Umbraco.Commerce.Checkout/Views/UmbracoCommerceCheckout).
2. Add them to `Views/UmbracoCommerceCheckout` in your project directory. It might be necessary to create the folder first.
3. Make a small text change to one of the Views to verify that the files are in use.
4. Verify that the changes are carried out and displayed correctly.
diff --git a/commerce-add-ons/packages/deploy/README.md b/commerce-add-ons/packages/deploy/README.md
index fe05e63dea2..5fe2fcf81e8 100644
--- a/commerce-add-ons/packages/deploy/README.md
+++ b/commerce-add-ons/packages/deploy/README.md
@@ -13,11 +13,11 @@ It is assumed that you already have one of the following setups:
* A Umbraco Cloud site with Umbraco Commerce installed and configured.
* A Umbraco CMS site configured with Umbraco Deploy and Umbraco Commerce installed and configured.
-If you are not at this stage yet, please read the [core Umbraco Commerce documentation](https://docs.umbraco.com/umbraco-commerce/) to learn how to get started.
+If you are not at this stage yet, read the [core Umbraco Commerce documentation](https://docs.umbraco.com/umbraco-commerce/) to learn how to get started.
## Useful links
-As well as the content in these docs, the following links may prove useful when using this package:
+As well as the content in these documentation, the following links may prove useful when using this package:
* [Umbraco Commerce Deploy source code](https://github.com/umbraco/Umbraco.Commerce.Deploy)
* [Umbraco Commerce Deploy issue tracker](https://github.com/umbraco/Umbraco.Commerce.Deploy)
diff --git a/commerce-add-ons/packages/product-feeds/README.md b/commerce-add-ons/packages/product-feeds/README.md
index c926c3443a4..826471225f6 100644
--- a/commerce-add-ons/packages/product-feeds/README.md
+++ b/commerce-add-ons/packages/product-feeds/README.md
@@ -12,7 +12,7 @@ Current supported feed template:
In this section, we will guide you through the key steps necessary to get you started with the Product Feeds package for Umbraco Commerce.
-It is assumed that before we begin you already have an Umbraco website configured and Umbraco Commerce installed and a store set up. If you are not at this stage yet, please read the [core Umbraco Commerce documentation](https://docs.umbraco.com/umbraco-commerce/) to learn how to get started.
+It is assumed that before we begin you already have an Umbraco website configured and Umbraco Commerce installed and a store set up. If you are not at this stage yet, read the [core Umbraco Commerce documentation](https://docs.umbraco.com/umbraco-commerce/) to learn how to get started.
# Useful links
- [Umbraco Commerce Product Feed source code](https://github.com/umbraco/Umbraco.Commerce.ProductFeeds)
- [Umbraco Commerce Product Feed issue tracker](https://github.com/umbraco/Umbraco.Commerce.ProductFeeds/issues)
\ No newline at end of file
diff --git a/commerce-add-ons/shipping-providers/dhl/README.md b/commerce-add-ons/shipping-providers/dhl/README.md
index bb559822a02..45a88a1509e 100644
--- a/commerce-add-ons/shipping-providers/dhl/README.md
+++ b/commerce-add-ons/shipping-providers/dhl/README.md
@@ -12,7 +12,7 @@ The DHL shipping provider adds functionality to ship products via [DHL](https://
In this section, we will guide you through the key steps necessary to get you started with the DHL shipping provider for Umbraco Commerce.
-It is assumed that before we begin you already have an Umbraco website configured and Umbraco Commerce installed. If you are not at this stage yet, please read the [core Umbraco Commerce documentation](https://docs.umbraco.com/umbraco-commerce/) to learn how to get started.
+It is assumed that before we begin you already have an Umbraco website configured and Umbraco Commerce installed. If you are not at this stage yet, read the [core Umbraco Commerce documentation](https://docs.umbraco.com/umbraco-commerce/) to learn how to get started.
## Useful links
diff --git a/commerce-add-ons/shipping-providers/easypost/README.md b/commerce-add-ons/shipping-providers/easypost/README.md
index 53471138a14..265a9a3a403 100644
--- a/commerce-add-ons/shipping-providers/easypost/README.md
+++ b/commerce-add-ons/shipping-providers/easypost/README.md
@@ -12,7 +12,7 @@ The EasyPost shipping provider adds functionality to ship products via [EasyPost
In this section, we will guide you through the key steps necessary to get you started with the EasyPost shipping provider for Umbraco Commerce.
-It is assumed that before we begin you already have an Umbraco website configured and Umbraco Commerce installed. If you are not at this stage yet, please read the [core Umbraco Commerce documentation](https://docs.umbraco.com/umbraco-commerce/) to learn how to get started.
+It is assumed that before we begin you already have an Umbraco website configured and Umbraco Commerce installed. If you are not at this stage yet, read the [core Umbraco Commerce documentation](https://docs.umbraco.com/umbraco-commerce/) to learn how to get started.
## Useful links
diff --git a/commerce-add-ons/shipping-providers/shipmondo/README.md b/commerce-add-ons/shipping-providers/shipmondo/README.md
index f4bd9208d04..32c035cd7a4 100644
--- a/commerce-add-ons/shipping-providers/shipmondo/README.md
+++ b/commerce-add-ons/shipping-providers/shipmondo/README.md
@@ -12,7 +12,7 @@ The Shipmondo shipping provider adds functionality to ship products via [Shipmon
In this section, we will guide you through the key steps necessary to get you started with the Shipmondo shipping provider for Umbraco Commerce.
-It is assumed that before we begin you already have an Umbraco website configured and Umbraco Commerce installed. If you are not at this stage yet, please read the [core Umbraco Commerce documentation](https://docs.umbraco.com/umbraco-commerce/) to learn how to get started.
+It is assumed that before we begin you already have an Umbraco website configured and Umbraco Commerce installed. If you are not at this stage yet, read the [core Umbraco Commerce documentation](https://docs.umbraco.com/umbraco-commerce/) to learn how to get started.
## Useful links
diff --git a/contributing/documentation/style-guide/README.md b/contributing/documentation/style-guide/README.md
index f15745a34f8..22d279b1275 100644
--- a/contributing/documentation/style-guide/README.md
+++ b/contributing/documentation/style-guide/README.md
@@ -100,7 +100,7 @@ This rule flags any use of discouraged terms in the Umbraco Documentation.
**Example**: The term `blacklist` must be avoided and replaced with `deny list`.
-For a full list of terms, please check the [style rule](https://github.com/umbraco/UmbracoDocs/blob/master/.github/styles/UmbracoDocs/Terms.yml).
+For a full list of terms, check the [style rule](https://github.com/umbraco/UmbracoDocs/blob/master/.github/styles/UmbracoDocs/Terms.yml).
### Umbraco Terms
diff --git a/contributing/hacktoberfest/contributing.md b/contributing/hacktoberfest/contributing.md
index 0fb31cf7b78..e2fa9d0cda4 100644
--- a/contributing/hacktoberfest/contributing.md
+++ b/contributing/hacktoberfest/contributing.md
@@ -8,7 +8,7 @@ Specificially for Hacktoberfest, we have a lot more things you can get involved
One of our main focus areas for 2024 is to deeply test out the major new features of Umbraco v15. The [release candidate for the upcoming Umbraco v15 is available now](https://umbraco.com/blog/umbraco-15-release-candidate/) and we encourage you to test the main new features, namely:
-- The new rich text editor (RTE)
+- The new Rich Text Editor (RTE)
- Migrating existing RTEs to the new RTE datatype
- Working with the new RTE
- Extending the new RTE
@@ -18,24 +18,24 @@ One of our main focus areas for 2024 is to deeply test out the major new feature
- Try out the new `ISeedKeyProvider`, `IDocumentServices` and `IDistributedCache`
- Block-level variants
- Making sure all of your existing blocks work after an upgrade
- - If you have a very large block-based site, it is interesting to see if the upgrade doesn't take too long
+ - If you have a large block-based site, it is interesting to see if the upgrade doesn't take too long
- Add variants to your existing or new blocks and start using them: edit, save, publish, etc
-Once you have done a round of thorough testing, please make sure to [report any issues on the tracker](https://github.com/umbraco/Umbraco-CMS/issues/new?assignees=&labels=type/bug&labels=affected/v14&template=01_bug_report.yml&title=v15RC1) as usual.
+Once you have done a round of thorough testing, make sure to [report any issues on the tracker](https://github.com/umbraco/Umbraco-CMS/issues/new?assignees=&labels=type/bug&labels=affected/v14&template=01_bug_report.yml&title=v15RC1) as usual.
### Making it count for Hacktoberfest
-We really appreciate your help in testing this release. Please make sure to describe to us in a bit of detail what you've tried, let us know a bit about the scale of project you're testing on, etc.
+We really appreciate your help in testing this release. Make sure to describe to us in a bit of detail what you've tried, let us know a bit about the scale of project you're testing on, etc.
If everything "just" worked (🤞) then describe that as well! Let us know exactly what you focused on that worked well.
-You can do this by heading to the [HacktoberfestActivityLog](https://github.com/umbraco/HacktoberfestActivityLog) repository and adding your name to the list in the "Low code/no code" section.
+You can do this by heading to the [HacktoberfestActivityLog](https://github.com/umbraco/HacktoberfestActivityLog) repository and adding your name to the list in the "Low code/no code" section.
An example of a participation entry is:
`- 2024-10-04 - Paula Philips - Umbraco 15 Release Candidate testing - Details in the PR description`
-In the description of the pull request to get your name added, please put your test results as described above and link to any issues you've created if things didn't work as expected.
+In the description of the pull request to get your name added, put your test results as described above and link to any issues you've created if things didn't work as expected.
{% hint style="info" %}
This would be a great use of [the `Draft` pull request feature on GitHub](https://github.blog/news-insights/product-news/introducing-draft-pull-requests/), so you can work on testing and keep updating the description with your test results until you're done and ready to submit your final PR.
@@ -53,7 +53,7 @@ Here are some specific details on this:
* Look for the "help wanted" label on the issue tracker associated with the package you want to help out with
* Read much more about how this works, and guidelines on adding your own package repo to [the list on the Umbraco Packages Hacktoberfest homepage](https://github.com/umbraco/Umbraco.Packages/tree/main/Hacktoberfest).
-Please note: Package contributions eligibility for swag differ slightly from those used for all contributions. Read more on the **[Packages Hacktoberfest guidelines](https://github.com/umbraco/Umbraco.Packages/tree/main/Hacktoberfest) to learn more about how a contribution is marked as "swag-eligible"**.
+Note: Package contributions eligibility for swag differ slightly from those used for all contributions. Read more on the **[Packages Hacktoberfest guidelines](https://github.com/umbraco/Umbraco.Packages/tree/main/Hacktoberfest) to learn more about how a contribution is marked as "swag-eligible"**.
### Creating a brand-new package
@@ -80,7 +80,7 @@ Eligible contributions according to [the Hacktoberfest guidelines](https://hackt
We [have set up a special GitHub repository](https://github.com/umbraco/HacktoberfestActivityLog) for you to record your contributions that are not a pull request.
-In order to record your journey of verifying documentation (like related blog post(s) in October, events organized), please edit the README.md file and add your activity at the end in the recommended format and submit that as a pull request. We’ll take it from there!
+In order to record your journey of verifying documentation (like related blog post(s) in October, events organized), edit the README.md file and add your activity at the end in the recommended format and submit that as a pull request. We’ll take it from there!
{% hint style="info" %}
The teams at [Skrift](https://skrift.io/write/) and [24 days in Umbraco](https://24days.in/umbraco-cms/write-for-us/) are always looking for new articles. Finish your application October to make it count! We'll ask the Skrift/24 days teams to verify your application to write an article.
@@ -104,7 +104,7 @@ And the good news is: yes, you will be able to earn Umbraco swag, proportionate
We use [the Hacktoberfest participation rules](https://hacktoberfest.com/participation/) to qualify, so any contributions that do not follow these standards will also not count towards Umbraco swag. These rules are to ensure we get quality contributions and that the right efforts get rewarded 🙌
-If you’re contributing to one of the open-source Umbraco Packages, please check [the Packages Hacktoberfest guidelines](https://github.com/umbraco/Umbraco.Packages/tree/main/Hacktoberfest) to learn more about how a contribution is marked as "swag-eligible".
+If you’re contributing to one of the open-source Umbraco Packages, check [the Packages Hacktoberfest guidelines](https://github.com/umbraco/Umbraco.Packages/tree/main/Hacktoberfest) to learn more about how a contribution is marked as "swag-eligible".
## Any questions?
diff --git a/contributing/umbraco-cms/build.md b/contributing/umbraco-cms/build.md
index 82e4b094f41..79d6aa45416 100644
--- a/contributing/umbraco-cms/build.md
+++ b/contributing/umbraco-cms/build.md
@@ -7,11 +7,11 @@ In order to use Umbraco as a CMS and build your website with it, you should not
* Are you about to [create a pull request for Umbraco](CONTRIBUTING.md)?
* Are you trying to get to the bottom of a problem in your existing Umbraco installation?
-If the answer is yes, please read on. Otherwise, make sure to head on over [to the download page](https://our.umbraco.com/download) and start using Umbraco CMS as intended.
+If the answer is yes, read on. Otherwise, make sure to head on over [to the download page](https://our.umbraco.com/download) and start using Umbraco CMS as intended.
## Getting Started
-To run umbraco, we first need to initialize the client git submodule:
+To run Umbraco, initialize the client git submodule:
* Execute `git submodule update --init` to get the files into `\src\Umbraco.Web.UI.Client` folder.
* This can be executed in the root folder of your cloned repository.
diff --git a/contributing/umbraco-cms/other-ways-to-contribute.md b/contributing/umbraco-cms/other-ways-to-contribute.md
index 773471b8f19..acbe5bea4fd 100644
--- a/contributing/umbraco-cms/other-ways-to-contribute.md
+++ b/contributing/umbraco-cms/other-ways-to-contribute.md
@@ -4,7 +4,7 @@ This document covers contributing to the codebase of the CMS but [the community
If you don't feel you'd like to make code changes here, you can visit our [documentation repository][docs repo] and use your experience to contribute to making the docs we have, even better.
-We also encourage community members to feel free to comment on others' pull requests and issues - the expertise we have is not limited to the Core Collaborators and HQ. So, if you see something on the issue tracker or pull requests you feel you can add to, please don't be shy.
+We also encourage community members to feel free to comment on others' pull requests and issues - the expertise we have is not limited to the Core Collaborators and HQ. So, if you see something on the issue tracker or pull requests you feel you can add to, don't be shy.
[get involved]: https://community.umbraco.com/get-involved/
[docs repo]: https://github.com/umbraco/UmbracoDocs
\ No newline at end of file
diff --git a/contributing/umbraco-cms/unwanted-changes.md b/contributing/umbraco-cms/unwanted-changes.md
index 4f32783bd5e..7c72b9cc1be 100644
--- a/contributing/umbraco-cms/unwanted-changes.md
+++ b/contributing/umbraco-cms/unwanted-changes.md
@@ -1,12 +1,12 @@
# Unwanted changes
-While most changes are welcome, there are certain types of changes that are discouraged and might get your pull request refused. Of course this will depend heavily on the specific change, but please take the following examples in mind.
+While most changes are welcome, there are certain types of changes that are discouraged and might get your pull request refused. This will depend heavily on the specific change, but take the following examples in mind.
-* **Breaking changes (code and/or behavioral) 💥** - sometimes it can be a bit hard to know if a change is breaking or not. Fortunately, if it relates to code, the build will fail and warn you.
+* **Breaking changes (code and/or behavioral) 💥** - sometimes it can be a bit hard to know if a change is breaking or not. If it relates to code, the build will fail and warn you.
* **Large refactors 🤯** - the larger the refactor, the larger the probability of introducing new bugs/issues.
* **Changes to obsolete code and/or property editors ✍️**
-* **Adding new config options 🦾** - while having more flexibility is (most of the times) better, having too many options can also become overwhelming/confusing, especially if there are other (good/simple) ways to achieve it.
-* **Whitespace changes 🫥** - while some of our files might not follow the formatting/whitespace rules (mostly old ones), changing several of them in one go would cause major merge conflicts with open pull requests or other work in progress. Do feel free to fix these when you are working on another issue/feature and end up "touching" those files!
+* **Adding new config options 🦾** - while having more flexibility is (most of the times) better, having too many options can also become overwhelming/confusing, especially if there are other (good/simpler) ways to achieve it.
+* **Whitespace changes 🫥** - while some of our files might not follow the formatting/whitespace rules (old ones), changing many of them in one go would cause major merge conflicts with open pull requests or other work in progress. Do feel free to fix these when you are working on another issue/feature and end up "touching" those files!
* **Adding new extension/helper methods ✋** - keep in mind that more code also means more to maintain, so if a helper is only meaningful for a few, it might not be worth adding it to the core.
* **Adding new dependencies 🔒** - if you are in need of adding a new dependency for Umbraco CMS to take on, this should be discussed first; dependencies need to be updated and can lead to unwanted security issues, so we only take on what is absolutely necessary.
diff --git a/marketplace-and-integrations/integrations/aprimo.md b/marketplace-and-integrations/integrations/aprimo.md
index 1bba7a9aa66..6003b20c2e5 100644
--- a/marketplace-and-integrations/integrations/aprimo.md
+++ b/marketplace-and-integrations/integrations/aprimo.md
@@ -72,7 +72,7 @@ Otherwise, you will be able to select one of the two available options for picki
### Browser information
-Before using the integration with Aprimo, please make sure to use a browser that is supported by Aprimo Cloud. Without one you will not be able to authenticate, nor use the Content Selector.
+Before using the integration with Aprimo, make sure to use a browser that is supported by Aprimo Cloud. Without one you will not be able to authenticate, nor use the Content Selector.
Aprimo currently supports these browsers, but make sure to check [this](https://help.aprimo.com/Content/Marketing_Operations_Help/aprimo_basics/browsers_configuring_concept.html) topic for an updated list:
diff --git a/marketplace-and-integrations/integrations/semrush.md b/marketplace-and-integrations/integrations/semrush.md
index 49cc0aa062e..a8fb9896d64 100644
--- a/marketplace-and-integrations/integrations/semrush.md
+++ b/marketplace-and-integrations/integrations/semrush.md
@@ -28,7 +28,7 @@ A keyword search can be initiated using a content field as a starting point, or
Administrators are provided with additional features for managing the connectivity with their organization's account with Semrush.
-For more detail on the integration, its purpose, and how2 it was built, please see the [accompanying blog post](https://umbraco.com/blog/integrating-umbraco-cms-with-semrush/).
+For more detail on the integration, its purpose, and how2 it was built, see the [accompanying blog post](https://umbraco.com/blog/integrating-umbraco-cms-with-semrush/).
### Self Hosted OAuth Configuration
@@ -95,6 +95,6 @@ Authorization specific methods are exposed by the [`ISemrushAuthorizationService
The used service is provided using the `AuthorizationImplementationFactory` method, depending on the type of authorization selected.
-If you are selecting your own authorization flow that uses the `AuthorizationService`, the redirect URL will be this one: `/umbraco/api/semrushauthorization/oauth`, from [`SemrushAuthorizationController`](https://github.com/umbraco/Umbraco.Cms.Integrations/blob/main/src/Umbraco.Cms.Integrations.SEO.Semrush/Controllers/SemrushAuthorizationController.cs). Please make sure to set to correct URL in the settings of the website and in the configuration of your _Semrush_ app.
+If you are selecting your own authorization flow that uses the `AuthorizationService`, the redirect URL will be this one: `/umbraco/api/semrushauthorization/oauth`, from [`SemrushAuthorizationController`](https://github.com/umbraco/Umbraco.Cms.Integrations/blob/main/src/Umbraco.Cms.Integrations.SEO.Semrush/Controllers/SemrushAuthorizationController.cs). Make sure to set to correct URL in the settings of the website and in the configuration of your _Semrush_ app.
The authorization controller uses the `window.postMessage` interface for cross-window communications when redirecting from the semrush authorization server.
diff --git a/marketplace-and-integrations/marketplace/introduction.md b/marketplace-and-integrations/marketplace/introduction.md
index cdd44df7a8c..217c2d70a9f 100644
--- a/marketplace-and-integrations/marketplace/introduction.md
+++ b/marketplace-and-integrations/marketplace/introduction.md
@@ -18,10 +18,10 @@ We provide links for each package to the NuGet details, and other locations if a
## Listing Your Package
-If you are a package developer wanting to make your work available for Umbraco website developers, please review the [listing your package](listing-your-package.md) article.
+If you are a package developer wanting to make your work available for Umbraco website developers, review the [listing your package](listing-your-package.md) article.
## Package Telemetry Data
Umbraco installations that have opted into providing basic or detailed telemetry data will indicate which packages are installed. We use that information to order packages by "Most Active Installs".
-To understand how to ensure your package is ranking correctly by this measure, please consider the details provided about [package telemetry data usage](package-telemetry-data.md).
+To understand how to ensure your package is ranking correctly by this measure, consider the details provided about [package telemetry data usage](package-telemetry-data.md).
diff --git a/marketplace-and-integrations/marketplace/listing-your-package.md b/marketplace-and-integrations/marketplace/listing-your-package.md
index c7e9307cc28..e6462fbc308 100644
--- a/marketplace-and-integrations/marketplace/listing-your-package.md
+++ b/marketplace-and-integrations/marketplace/listing-your-package.md
@@ -16,7 +16,7 @@ Your package needs to live up to the following requirements to be listed on the
The base package information is then sourced from NuGet, including the package name, icon, authors, description, readme, and project URL.
{% hint style="warning" %}
-Please only tag the installable component of your package. For example, if your package `MyPackage` references `MyPackage.Core`, only tag the former.
+Only tag the installable component of your package. For example, if your package `MyPackage` references `MyPackage.Core`, only tag the former.
{% endhint %}
## Additional Package Information
@@ -254,7 +254,7 @@ This endpoint is throttled such that only one request a minute can be made per p
## Feedback
-If you run into any issues with listing your package, please file an issue on the [Issue Tracker](https://github.com/umbraco/Umbraco.Marketplace.Issues/issues/).
+If you run into any issues with listing your package, file an issue on the [Issue Tracker](https://github.com/umbraco/Umbraco.Marketplace.Issues/issues/).
We will periodically send details of updates made to registered package developers.
diff --git a/marketplace-and-integrations/marketplace/package-telemetry-data.md b/marketplace-and-integrations/marketplace/package-telemetry-data.md
index 54d4319ed5e..c2a926ffdec 100644
--- a/marketplace-and-integrations/marketplace/package-telemetry-data.md
+++ b/marketplace-and-integrations/marketplace/package-telemetry-data.md
@@ -44,7 +44,7 @@ If the package name or folder is used, this may not be the same as the NuGet pac
It's no longer possible to supply this via the `umbraco-marketplace.json` file. The field by which this was supplied has been deprecated in the schema and if provided will no be longer imported. This was due to the risks of two package developers providing the same alternate names.
-Instead we maintain this list at HQ. You may own a package that appears to not rank as expected via the "most active installs" measure. If you suspect it's due to the telemetry data not being correctly allocated, please let us know. We can make the necessary updates such that it's popularity is properly reflected. You can reach us at [packages@umbraco.com](mailto:packages@umbraco.com) and tell us the name used for your package in the package manifest or folder.
+Instead we maintain this list at HQ. You may own a package that appears to not rank as expected via the "most active installs" measure. If you suspect it's due to the telemetry data not being correctly allocated, let us know. We can make the necessary updates such that it's popularity is properly reflected. You can reach us at [packages@umbraco.com](mailto:packages@umbraco.com) and tell us the name used for your package in the package manifest or folder.
### What if I don't have a client-side component?
diff --git a/marketplace-and-integrations/packages/storage-providers.md b/marketplace-and-integrations/packages/storage-providers.md
index 61c545e0c2a..1f4d73cb778 100644
--- a/marketplace-and-integrations/packages/storage-providers.md
+++ b/marketplace-and-integrations/packages/storage-providers.md
@@ -7,4 +7,4 @@ description: >-
`Umbraco.StorageProviders` and `Umbraco.StorageProviders.AzureBlob` are open-source packages supported by Umbraco that allow you to replace the default physical file storage for an alternative. An implementation that uses [Azure Blob Storage](https://azure.microsoft.com/en-us/products/storage/blobs) for media and image caching is provided.
-For details on usage or to review or contribute to the code please see the [Umbraco.StorageProviders repository at GitHub](https://github.com/umbraco/Umbraco.StorageProviders).
\ No newline at end of file
+For details on usage, to review, or contribute to the code, see the [Umbraco.StorageProviders repository at GitHub](https://github.com/umbraco/Umbraco.StorageProviders).
diff --git a/umbraco-cloud/build-and-customize-your-solution/set-up-your-project/databases/backups.md b/umbraco-cloud/build-and-customize-your-solution/set-up-your-project/databases/backups.md
index 10fc5ab275a..d5cf9f2c601 100644
--- a/umbraco-cloud/build-and-customize-your-solution/set-up-your-project/databases/backups.md
+++ b/umbraco-cloud/build-and-customize-your-solution/set-up-your-project/databases/backups.md
@@ -134,5 +134,5 @@ RECONFIGURE;
GO
```
-For reference please see the [Microsoft documentation on the topic](https://learn.microsoft.com/en-us/sql/database-engine/configure-windows/contained-database-authentication-server-configuration-option?view=sql-server-ver16).
+For reference, see the [Microsoft documentation on the topic](https://learn.microsoft.com/en-us/sql/database-engine/configure-windows/contained-database-authentication-server-configuration-option?view=sql-server-ver16).
{% endhint %}
diff --git a/umbraco-cloud/build-and-customize-your-solution/set-up-your-project/project-settings/upgrade-your-plan.md b/umbraco-cloud/build-and-customize-your-solution/set-up-your-project/project-settings/upgrade-your-plan.md
index df72cf97c4b..7505fcf1a29 100644
--- a/umbraco-cloud/build-and-customize-your-solution/set-up-your-project/project-settings/upgrade-your-plan.md
+++ b/umbraco-cloud/build-and-customize-your-solution/set-up-your-project/project-settings/upgrade-your-plan.md
@@ -6,7 +6,7 @@ This article discusses how to upgrade your Umbraco Cloud plan and important cons
Before you decide to upgrade your Umbraco Cloud plan, you need to consider a few things:
-* Changing a plan for a project will change the outgoing IP of the project. If your solution has an external service that requires whitelisting the outgoing IP of the project, please visit the documentation for [external services](../../../expand-your-projects-capabilities/external-services/) prior to the upgrade.
+* Changing a plan for a project will change the outgoing IP of the project. If your solution has an external service that requires whitelisting the outgoing IP of the project, visit the documentation for [external services](../../../expand-your-projects-capabilities/external-services/) prior to the upgrade.
* If you are on the Starter plan, you can either upgrade your plan to a Standard or a Professional plan.
* On the Standard plan, you have the option to upgrade to a professional plan.
* Before upgrading, make sure to check the [price difference](https://umbraco.com/umbraco-cloud-pricing) and the features you get on the new plan.
diff --git a/umbraco-cloud/build-and-customize-your-solution/set-up-your-project/security/managing-transport-security.md b/umbraco-cloud/build-and-customize-your-solution/set-up-your-project/security/managing-transport-security.md
index 5b8522bbb13..fef21d2560a 100644
--- a/umbraco-cloud/build-and-customize-your-solution/set-up-your-project/security/managing-transport-security.md
+++ b/umbraco-cloud/build-and-customize-your-solution/set-up-your-project/security/managing-transport-security.md
@@ -30,16 +30,17 @@ The minimum TLS Version only allows HTTPS connections from visitors that support
## WAF Explained
-A Web Application Firewall (WAF) is a security solution designed to protect web applications by filtering and monitoring HTTP traffic between them and the Internet. Common attacks like cross-site scripting, SQL injection, and file inclusion are mitigated by acting as a shield between the web application and potential threats. For more detailed information, please refer to our [WAF section](web-application-firewall.md).
+A Web Application Firewall (WAF) is a security solution designed to protect web applications by filtering and monitoring HTTP traffic between them and the Internet. Common attacks like cross-site scripting, SQL injection, and file inclusion are mitigated by acting as a shield between the web application and potential threats. For more detailed information, refer to our [WAF section](web-application-firewall.md).
## Web Application Firewall Sensitivity
The Umbraco Cloud WAF supports sensitivity configuration, extending the default [WAF](web-application-firewall.md) protection. The default [WAF](web-application-firewall.md) and WAF sensitivity configuration options don't interact and can be controlled separately. It is recommended to configure WAF sensitivity early in the project and adjust it based on the performance.
### Sensitivity levels
-- **Low** severity configuration will block malicious requests with high confidence - blocks fewer requests.
-- **High** severity configuration will block malicious requests with medium confidence, providing stricter filtering - blocks more requests.
-- **Off** configuration will not block any requests.
+
+* **Low** severity configuration will block malicious requests with high confidence - blocks fewer requests.
+* **High** severity configuration will block malicious requests with medium confidence, providing stricter filtering - blocks more requests.
+* **Off** configuration will not block any requests.
## Managed Challenge
diff --git a/umbraco-cloud/explore-umbraco-cloud/what-is-umbraco-cloud/frequently-asked-questions.md b/umbraco-cloud/explore-umbraco-cloud/what-is-umbraco-cloud/frequently-asked-questions.md
index 2c438974cea..a8da105b183 100644
--- a/umbraco-cloud/explore-umbraco-cloud/what-is-umbraco-cloud/frequently-asked-questions.md
+++ b/umbraco-cloud/explore-umbraco-cloud/what-is-umbraco-cloud/frequently-asked-questions.md
@@ -1021,7 +1021,7 @@ Any default Umbraco files may be overwritten during upgrades. This usually affec
### Can I perform penetration tests on my Umbraco Cloud site?
-Yes, you can conduct penetration tests on your Cloud site. However, please inform Support beforehand so the team can monitor for any unusual activity.
+Yes, you can conduct penetration tests on your Cloud site. However, inform Support beforehand so the team can monitor for any unusual activity.
Test results are welcome to help improve Umbraco's security. Contact Support via the chat button at the bottom right of the [Umbraco Cloud portal](https://www.s1.umbraco.io/).
diff --git a/umbraco-cloud/optimize-and-maintain-your-site/optimize-performance/migrate-between-regions.md b/umbraco-cloud/optimize-and-maintain-your-site/optimize-performance/migrate-between-regions.md
index 74f8f528b5c..50124d7f595 100644
--- a/umbraco-cloud/optimize-and-maintain-your-site/optimize-performance/migrate-between-regions.md
+++ b/umbraco-cloud/optimize-and-maintain-your-site/optimize-performance/migrate-between-regions.md
@@ -138,7 +138,7 @@ The following will need to be reconfigured on the new project after the initial
Once everything has been configured and set up you can safely delete the _EU project_ which will also cancel the running subscription on the project.
-If you need help or have any questions regarding this process, please contact our support using [contact@umbraco.com](mailto:contact@umbraco.com).
+If you need help or have any questions regarding this process, contact our support using [contact@umbraco.com](mailto:contact@umbraco.com).
## Related articles
diff --git a/umbraco-cloud/release-notes/archive/overview-2023/2023-02-releasenotes.md b/umbraco-cloud/release-notes/archive/overview-2023/2023-02-releasenotes.md
index 4dd30459008..8fcac055e0f 100644
--- a/umbraco-cloud/release-notes/archive/overview-2023/2023-02-releasenotes.md
+++ b/umbraco-cloud/release-notes/archive/overview-2023/2023-02-releasenotes.md
@@ -40,7 +40,7 @@ Our updated deployment process facilitates that your website is deployed quickly
Some of the deployment issues reported by users are related to the configuration of the Umbraco Cloud project or schema mismatches between environments. In these scenarios, we strive to provide a helpful text that will guide you in the right direction to solve the issue at hand.
-If you are experiencing a deployment error, a question, or a remark about the deployment feature, please **consult our experienced support team**. Both the Umbraco Support and Cloud Team are dedicated to removing any friction caused by deployments on Umbraco cloud. Our vision is to make the deployment process in Umbraco Cloud as perfect as it can be.
+If you are experiencing a deployment error, a question, or a remark about the deployment feature, **consult our experienced support team**. Both the Umbraco Support and Cloud Team are dedicated to removing any friction caused by deployments on Umbraco cloud. Our vision is to make the deployment process in Umbraco Cloud as perfect as it can be.
## Restore Content Optimization
diff --git a/umbraco-cloud/release-notes/archive/overview-2023/2023-06-releasenotes.md b/umbraco-cloud/release-notes/archive/overview-2023/2023-06-releasenotes.md
index e4b7c5a8c05..337cc261a1c 100644
--- a/umbraco-cloud/release-notes/archive/overview-2023/2023-06-releasenotes.md
+++ b/umbraco-cloud/release-notes/archive/overview-2023/2023-06-releasenotes.md
@@ -38,7 +38,7 @@ The Major Upgrade Guide outlines the necessary steps and best practices to succe

-For more information about the new great version 12 of Umbraco CMS, please read this great [blog post](https://umbraco.com/blog/umbraco-12-release/).
+For more information about the new great version 12 of Umbraco CMS, read this great [blog post](https://umbraco.com/blog/umbraco-12-release/).
It highlights the latest and greatest new improvements in Umbraco CMS such as:
diff --git a/umbraco-cloud/release-notes/archive/overview-2023/2023-09-releasenotes.md b/umbraco-cloud/release-notes/archive/overview-2023/2023-09-releasenotes.md
index 081d7879488..d6c13640471 100644
--- a/umbraco-cloud/release-notes/archive/overview-2023/2023-09-releasenotes.md
+++ b/umbraco-cloud/release-notes/archive/overview-2023/2023-09-releasenotes.md
@@ -21,7 +21,7 @@ The new "Shared Secrets" panel lets you define secrets that are critical during
Besides the new shared secrets, we still have the **Environment Secrets**: For secrets that are specific to individual environments, continue to use the existing "Environment Secrets" panel. These secrets remain locked to the selected environment and won't be accessible by others.
-For more detailed information on how to leverage secrets, please visit our [documentation](https://docs.umbraco.com/umbraco-cloud/set-up/project-settings/secrets-management).
+For more detailed information on how to leverage secrets, visit our [documentation](https://docs.umbraco.com/umbraco-cloud/set-up/project-settings/secrets-management).
## Upgraded "Usage" Page for Custom Plans
diff --git a/umbraco-cloud/release-notes/archive/overview-2023/2023-10-releasenotes.md b/umbraco-cloud/release-notes/archive/overview-2023/2023-10-releasenotes.md
index f93d5120c9c..79e8c83f862 100644
--- a/umbraco-cloud/release-notes/archive/overview-2023/2023-10-releasenotes.md
+++ b/umbraco-cloud/release-notes/archive/overview-2023/2023-10-releasenotes.md
@@ -31,4 +31,4 @@ If you're starting a new Cloud project, the feature will be enabled by default,
With Automatic Minor Upgrades, you can enjoy different benefits. First, you'll save a significant amount of time, allowing you to focus on more important aspects of your project. Second, you'll have access to the latest features and enhancements across all key components. Lastly, the most recent security patches are applied automatically, giving you peace of mind.
-For further details, please consult our Upgrading Documentation where you'll find details regarding the upgrade process. Our support team is also on standby to assist with any queries you may have.
+For further details, consult our Upgrading Documentation where you'll find details regarding the upgrade process. Our support team is also on standby to assist with any queries you may have.
diff --git a/umbraco-heartcore/release-notes/2024-08-releasenotes.md b/umbraco-heartcore/release-notes/2024-08-releasenotes.md
index dd8dca714fb..66d6fa871b1 100644
--- a/umbraco-heartcore/release-notes/2024-08-releasenotes.md
+++ b/umbraco-heartcore/release-notes/2024-08-releasenotes.md
@@ -11,4 +11,4 @@ Aside from the interface, all other aspects of webhooks in Heartcore are unchang
For more information about webhook functionality, both new and old, check out the [updated Webhooks article](../getting-started/webhooks.md).
## Improved Firewall
-A recent roll-out has added additional firewall rules for all Heartcore services. While efforts have been made to tune these, there is always a small possibility of false positives. If you believe your legitimate traffic is affected, please raise a support ticket through the portal.
+A recent roll-out has added additional firewall rules for all Heartcore services. While efforts have been made to tune these, there is always a small possibility of false positives. If you believe your legitimate traffic is affected, raise a support ticket through the portal.