From f95bcd727528fef3653c9f3ffd8912e7dda1cf9c Mon Sep 17 00:00:00 2001 From: Esha Noronha Date: Wed, 12 Nov 2025 10:39:44 +0100 Subject: [PATCH] Removed the word "please" --- .../extending/health-check/README.md | 2 +- .../section-trees/trees/tree-actions.md | 2 +- .../block-editor/block-list-editor.md | 2 +- .../design/stylesheets-javascript.md | 2 +- .../angular/services/eventsservice/README.md | 2 +- .../additional-preview-environments-support.md | 2 +- .../custom-property-editors-support.md | 2 +- .../extension-api-for-querying.md | 2 +- .../content-delivery-api/media-delivery-api.md | 4 ++-- .../property-expansion-and-limiting.md | 4 ++-- .../protected-content-in-the-delivery-api.md | 6 +++--- .../reference/management/models/contenttype.md | 2 +- .../reference/management/models/mediatype.md | 2 +- .../reference/searching/examine/indexing.md | 2 +- .../creating-a-basic-website/README.md | 2 +- .../creating-a-custom-dashboard/README.md | 2 +- .../tips-and-tricks/notifications.md | 2 +- 13/umbraco-cms/tutorials/multisite-setup.md | 2 +- .../changelog-archive/Vendr-core.md | 4 ++-- .../handling-cache-refresher-notifications.md | 2 +- 13/umbraco-deploy/troubleshooting.md | 2 +- .../bridging-library-for-google-analytics.md | 4 ++-- 13/umbraco-engage/installation/installation.md | 4 ++-- .../installation/troubleshooting-installs.md | 6 +++--- .../settings/setting-up-goals.md | 4 ++-- .../upgrading/migrate-from-umarketingsuite.md | 10 +++++----- 13/umbraco-forms/developer/ajaxforms.md | 2 +- .../developer/healthchecks/README.md | 2 +- .../developer/prepping-frontend.md | 2 +- .../installation/the-licensing-model.md | 2 +- .../development-flow/typescript-setup.md | 2 +- .../replace-exclude-or-unregister.md | 2 +- .../extension-types/entity-actions.md | 2 +- .../extending/health-check/README.md | 2 +- .../block-editor/block-list-editor.md | 2 +- .../design/stylesheets-javascript.md | 2 +- .../setup/upgrading/version-specific/README.md | 6 +++--- .../additional-preview-environments-support.md | 2 +- .../custom-property-editors-support.md | 2 +- .../extension-api-for-querying.md | 2 +- .../content-delivery-api/media-delivery-api.md | 4 ++-- .../property-expansion-and-limiting.md | 4 ++-- .../README.md | 8 ++++---- .../management-api/external-access.md | 2 +- .../reference/searching/examine/indexing.md | 2 +- .../tips-and-tricks/notifications.md | 2 +- .../changelog-archive/Vendr-core.md | 2 +- .../handling-cache-refresher-notifications.md | 2 +- 15/umbraco-deploy/troubleshooting.md | 2 +- 15/umbraco-forms/developer/ajaxforms.md | 2 +- .../developer/healthchecks/README.md | 2 +- .../developer/prepping-frontend.md | 2 +- .../installation/the-licensing-model.md | 2 +- .../extension-types/entity-actions.md | 2 +- .../extending-overview/extension-types/tree.md | 2 +- .../property-editor-validation.md | 2 +- 16/umbraco-cms/extending/flag-providers.md | 2 +- .../extending/health-check/README.md | 2 +- .../block-editor/block-list-editor.md | 2 +- .../server-setup/running-umbraco-in-docker.md | 2 +- .../setup/upgrading/version-specific/README.md | 6 +++--- .../additional-preview-environments-support.md | 2 +- .../custom-property-editors-support.md | 2 +- .../extension-api-for-querying.md | 2 +- .../content-delivery-api/media-delivery-api.md | 4 ++-- .../property-expansion-and-limiting.md | 4 ++-- .../README.md | 12 ++++++------ .../management-api/external-access.md | 2 +- .../reference/searching/examine/indexing.md | 2 +- .../tips-and-tricks/notifications.md | 2 +- .../changelog-archive/Vendr-core.md | 2 +- .../handling-cache-refresher-notifications.md | 2 +- 16/umbraco-deploy/troubleshooting.md | 2 +- .../bridging-library-for-google-analytics.md | 4 ++-- 16/umbraco-engage/installation/installation.md | 4 ++-- .../installation/troubleshooting-installs.md | 2 +- .../settings/setting-up-goals.md | 4 ++-- .../upgrading/migrate-from-umarketingsuite.md | 10 +++++----- 16/umbraco-forms/developer/ajaxforms.md | 2 +- .../developer/healthchecks/README.md | 2 +- .../installation/the-licensing-model.md | 2 +- .../extension-types/entity-actions.md | 2 +- .../extending-overview/extension-types/tree.md | 2 +- .../property-editor-validation.md | 2 +- 17/umbraco-cms/extending/flag-providers.md | 2 +- .../extending/health-check/README.md | 2 +- .../block-editor/block-list-editor.md | 2 +- .../server-setup/running-umbraco-in-docker.md | 2 +- .../setup/upgrading/version-specific/README.md | 6 +++--- .../custom-property-editors-support.md | 2 +- .../extension-api-for-querying.md | 2 +- .../content-delivery-api/media-delivery-api.md | 4 ++-- .../property-expansion-and-limiting.md | 4 ++-- .../README.md | 8 ++++---- .../management-api/external-access.md | 2 +- .../reference/searching/examine/indexing.md | 2 +- .../tips-and-tricks/notifications.md | 2 +- .../changelog-archive/Vendr-core.md | 2 +- .../handling-cache-refresher-notifications.md | 2 +- .../bridging-library-for-google-analytics.md | 4 ++-- 17/umbraco-engage/installation/installation.md | 4 ++-- .../installation/troubleshooting-installs.md | 2 +- .../settings/setting-up-goals.md | 4 ++-- .../upgrading/migrate-from-umarketingsuite.md | 10 +++++----- 17/umbraco-forms/developer/ajaxforms.md | 2 +- .../developer/healthchecks/README.md | 2 +- .../installation/the-licensing-model.md | 2 +- commerce-add-ons/packages/cart/README.md | 2 +- commerce-add-ons/packages/checkout/README.md | 4 ++-- .../packages/checkout/customize-checkout.md | 6 +++--- commerce-add-ons/packages/deploy/README.md | 4 ++-- .../packages/product-feeds/README.md | 2 +- .../shipping-providers/dhl/README.md | 2 +- .../shipping-providers/easypost/README.md | 2 +- .../shipping-providers/shipmondo/README.md | 2 +- .../documentation/style-guide/README.md | 2 +- contributing/hacktoberfest/contributing.md | 18 +++++++++--------- contributing/umbraco-cms/build.md | 4 ++-- .../umbraco-cms/other-ways-to-contribute.md | 2 +- contributing/umbraco-cms/unwanted-changes.md | 8 ++++---- .../integrations/aprimo.md | 2 +- .../integrations/semrush.md | 4 ++-- .../marketplace/introduction.md | 4 ++-- .../marketplace/listing-your-package.md | 4 ++-- .../marketplace/package-telemetry-data.md | 2 +- .../packages/storage-providers.md | 2 +- .../set-up-your-project/databases/backups.md | 2 +- .../project-settings/upgrade-your-plan.md | 2 +- .../security/managing-transport-security.md | 9 +++++---- .../frequently-asked-questions.md | 2 +- .../migrate-between-regions.md | 2 +- .../overview-2023/2023-02-releasenotes.md | 2 +- .../overview-2023/2023-06-releasenotes.md | 2 +- .../overview-2023/2023-09-releasenotes.md | 2 +- .../overview-2023/2023-10-releasenotes.md | 2 +- .../release-notes/2024-08-releasenotes.md | 2 +- 136 files changed, 210 insertions(+), 209 deletions(-) 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 75867a7e83d..fffc5766f04 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 %} ## Member authorization @@ -352,7 +352,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 @@ -440,7 +440,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. ![Engage section in the Backoffice](../.gitbook/assets/engage-engage-section.png) @@ -22,7 +22,7 @@ When editing a page within Umbraco, you should be able to see the following Cont ![Content Apps on content page](../.gitbook/assets/engage-content-apps.png) -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", "", "", "