Merge pull request #7614 from umbraco/remove-please

Removed the word "please"

Author: eshanrnh

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.
 

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 |
 | ------------------------------------------------------------- | ---------------------- | ------ | -------------------------- |

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:
 

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.

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
 

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" %}

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
 

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.
 

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" %}

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.