Acrolinx fixes

Author: FaithOmbongi

concepts/includes/known-issues/authentication.md

@@ -16,7 +16,7 @@ The consent page shows that the command-line app that caters to PowerShell and C
 
 #### Workaround
 
-To remove the "unverified" message, you can do an app registration of your own, on which you can set yourself as the verified publisher. You will need to go through the publisher verification process, and use the app ID on the Microsoft Graph PowerShell SDK, as follows:
+To remove the "unverified" message, you can do an app registration of your own, on which you can set yourself as the verified publisher. You need to go through the publisher verification process, and use the app ID on the Microsoft Graph PowerShell SDK, as follows:
 
 ```powershell
 Connect-MgGraph -AppId "{your-own-app-id}" -Scopes "scope"
@@ -35,14 +35,14 @@ For apps using delegated permissions, when using the app for the first time with
 
 For apps using application permissions, your app can acquire a token, but unexpectedly gets an access denied message when calling Microsoft Graph.
 
-We are working to fix this issue, so that pre-consent will work for all your customer tenants.
+We're working to fix this issue, so that preconsent works for all CSP customer tenants.
 
 #### Workaround
 
 To unblock development and testing, you can use the following workaround.
 
 > [!NOTE]
-> This is not a permanent solution and is only intended to unblock development. This workaround will not be required once the issue is fixed. This workaround does not need to be undone after the fix is in place.
+> This isn't a permanent solution and is only intended to unblock development. This workaround won't be required once the issue is fixed. This workaround doesn't need to be undone after the fix is in place.
 
 1. Open an Azure AD v2 PowerShell session and connect to your customer tenant by entering your admin credentials into the sign-in window. You can download and install Azure AD PowerShell V2 from [here](https://www.powershellgallery.com/packages/AzureAD).
 
@@ -56,11 +56,11 @@ To unblock development and testing, you can use the following workaround.
     New-AzureADServicePrincipal -AppId 00000003-0000-0000-c000-000000000000
     ```
 
-### Azure AD v2.0 endpoint is not supported for CSP apps
+### Azure AD v2.0 endpoint isn't supported for CSP apps
 
 <!-- {
   "ms.author": "sureshja",
   "ms.reviewer": ""
 } -->
 
-Cloud solution provider (CSP) apps must acquire tokens from the Azure AD (v1) endpoints to successfully call Microsoft Graph in their partner-managed customers. Currently, acquiring a token through the newer Azure AD v2.0 endpoint is not supported.
+Cloud solution provider (CSP) apps must acquire tokens from the Azure AD (v1) endpoints to successfully call Microsoft Graph in their partner-managed customers. Currently, acquiring a token through the newer Azure AD v2.0 endpoint isn't supported.

concepts/includes/known-issues/change-notifications.md

@@ -1,22 +1,22 @@
 ---
 author: ombongifaith
 ms.topic: include
-ms.date: 02/06/2026
+ms.date: 02/25/2026
 ms.localizationpriority: medium
 ---
 
-### Upgrade events for Teams app installation change notifications in chat scope are not delivered
+### Upgrade events for Teams app installation change notifications in chat scope aren't delivered
 
 <!-- {
   "ms.author": "",
   "ms.reviewer": ""
 } -->
 
-When a subscription for a Teams app installation change notification is created, if the scope is specific to or includes chats, upgrade events/notifications will not be delivered to the subscriber.
+When a subscription for a Teams app installation change notification is created, if the scope is specific to or includes chats, upgrade events/notifications aren't delivered to the subscriber.
 
-For example: If a customer subscribes to `/appCatalogs/teamsApps/{teams-app-id}/installations?$filter=(scopeInfo/scope eq 'groupChat')`, they will not receive notifications for upgrade/update events. However, they will receive other notifications regarding installations and deletions.
+For example: If a customer subscribes to `/appCatalogs/teamsApps/{teams-app-id}/installations?$filter=(scopeInfo/scope eq 'groupChat')`, they won't receive notifications for upgrade/update events. However, they receive other notifications regarding installations and deletions.
 
-Another example: If a customer subscribes to `/appCatalogs/teamsApps/{teams-app-id}/installations`, they will not receive notifications for upgrade/update events occurring specifically within chats. However, they will receive all other forms of notifications in teams and user's personal scope. But, in chats, they will only receive installation and deletion notifications.
+Another example: If a customer subscribes to `/appCatalogs/teamsApps/{teams-app-id}/installations`, they won't receive notifications for upgrade/update events occurring specifically within chats. However, they receive all other forms of notifications in teams and user's personal scope. But, in chats, they only receive installation and deletion notifications.
 
 #### Workaround
 

concepts/includes/known-issues/groups.md

@@ -5,20 +5,20 @@ ms.date: 02/06/2026
 ms.localizationpriority: medium
 ---
 
-### Non-admin user can't add self as group owner during group creation or update
+### Nonadmin user can't add self as group owner during group creation or update
 
 <!-- {
   "ms.author": "yuhko",
   "ms.reviewer": ""
 } -->
 
-When a non-admin user calls the [Create group](/graph/api/group-post-groups) API, [Update group](/graph/api/group-update) API, or [Upsert group](/graph/api/group-upsert) API and adds their user ID in the request body in the **owners@odata.bind** collection, the request fails with a `400 Bad Request` error code with the message "Request contains a property with duplicate values." A non-admin user can't explicitly add themselves as the group owner.
+When a nonadmin user calls the [Create group](/graph/api/group-post-groups) API, [Update group](/graph/api/group-update) API, or [Upsert group](/graph/api/group-upsert) API and adds their user ID in the request body in the **owners@odata.bind** collection, the request fails with a `400 Bad Request` error code with the message "Request contains a property with duplicate values." A nonadmin user can't explicitly add themselves as the group owner.
 
 #### Workaround
 
-There is no workaround for this error.
+There's no workaround for this error.
 
-By default, a non-admin user who is creating a security or Microsoft 365 group through the [Create group](/graph/api/group-post-groups) API or [Upsert group](/graph/api/group-upsert) API is automatically added to the **owners** collection of the group, if they don't specify any group owners. If they specify others as group owners, the non-admin group creator is still automatically added to the **owners** collection of the security group, but not for the Microsoft 365 group. The user still can't add themselves to the **owners** collection during group update.
+By default, a nonadmin user who is creating a security or Microsoft 365 group through the [Create group](/graph/api/group-post-groups) API or [Upsert group](/graph/api/group-upsert) API is automatically added to the **owners** collection of the group, if they don't specify any group owners. If they specify others as group owners, the nonadmin group creator is still automatically added to the **owners** collection of the security group, but not for the Microsoft 365 group. The user still can't add themselves to the **owners** collection during group update.
 
 ### GET /groups/{id}/members doesn't return service principals in v1.0
 

concepts/includes/known-issues/mail.md

@@ -1,7 +1,7 @@
 ---
 author: ombongifaith
 ms.topic: include
-ms.date: 02/06/2026
+ms.date: 02/25/2026
 ms.localizationpriority: medium
 ---
 
@@ -14,11 +14,11 @@ ms.localizationpriority: medium
 
 When you make `/delta` calls to the messages API using immutable Ids in some cases (for example when a message moves out of a folder and is then moved back in), you might miss some change notifications.
 
-### The comment parameter for creating a draft does not become part of the message body
+### The comment parameter for creating a draft isn't part of the message body
 
 <!-- {
   "ms.author": "abhda",
   "ms.reviewer": ""
 } -->
 
-The **comment** parameter for creating a reply or forward draft ([createReply](/graph/api/message-createreply), [createReplyAll](/graph/api/message-createreplyall), [createForward](/graph/api/message-createforward)) does not become part of the body of the resultant message draft.
+The **comment** parameter for creating a reply or forward draft ([createReply](/graph/api/message-createreply), [createReplyAll](/graph/api/message-createreplyall), [createForward](/graph/api/message-createforward)) isn't part of the body of the response message draft.

concepts/includes/known-issues/query-parameters.md

@@ -1,7 +1,7 @@
 ---
 author: ombongifaith
 ms.topic: include
-ms.date: 02/06/2026
+ms.date: 02/25/2026
 ms.localizationpriority: medium
 ---
 
@@ -20,7 +20,7 @@ GET https://graph.microsoft.com/v1.0/groups?$search="displayName:Hiking%26Recrea
 
 Microsoft Graph currently returns a `400 Bad Request` error code on the v1.0 endpoint on searches that include encoded ampersand (&) characters, with the following error message: `Unrecognized query argument specified: ''.`. The same request succeeds on the beta endpoint.
 
-Some apps have implemented double-percent encoding on the v1.0 endpoint as a workaround. For example, the double-percent encoded request becomes `/users?$search="displayName:Hiking%2526Recreation group"`. However, this is not the officially recommended workaround.
+Some apps have implemented double-percent encoding on the v1.0 endpoint as a workaround. For example, the double-percent encoded request becomes `/users?$search="displayName:Hiking%2526Recreation group"`. However, this isn't the officially recommended workaround.
 
 #### Workaround
 
@@ -34,11 +34,11 @@ ConsistencyLevel: eventual
 Prefer: legacySearch=false
 ```
 
-In the future, the behavior on the v1.0 endpoint will be corrected, and you will not need to include this header.
+In the future, the behavior on the v1.0 endpoint will be corrected, and you won't need to include this header.
 
 **Workaround 2:**
 
-When the behavior on the v1.0 endpoint is corrected, apps that will have a dependency on the double-percent encoding may experience breaking changes unless they are opted-in to maintain their implementation by including the `Prefer` request header set to `legacySearch=true`. For example:
+When the behavior on the v1.0 endpoint is corrected, apps with dependency on the double-percent encoding may experience breaking changes unless they're opted-in to maintain their implementation by including the `Prefer` request header set to `legacySearch=true`. For example:
 
 ```http
 GET https://graph.microsoft.com/v1.0/groups?$search="displayName:Hiking%2526Recreation group"
@@ -55,25 +55,25 @@ Prefer: legacySearch=true
 
 The following limitations apply to query parameters:
 
-- Multiple namespaces are not supported.
-- GET requests on `$ref` and casting are not supported on users, groups, devices, service principals and applications.
-- `@odata.bind` is not supported. This means that you can't properly set the **acceptedSenders** or **rejectedSenders** navigation property on a group.
-- `@odata.id` is not present on non-containment navigations (like messages) when using minimal metadata.
+- Multiple namespaces aren't supported.
+- GET requests on `$ref` and casting aren't supported on users, groups, devices, service principals, and applications.
+- `@odata.bind` isn't supported. This means that you can't properly set the **acceptedSenders** or **rejectedSenders** navigation property on a group.
+- `@odata.id` isn't present on noncontainment navigations (like messages) when using minimal metadata.
 - `$expand` on relationships of directory objects:
-  - Returns a maximum of 20 objects except for `/users?$expand=registeredDevices` which returns up to 100 objects.
+  - Returns a maximum of 20 objects except for `/users?$expand=registeredDevices`, which returns up to 100 objects.
   - No support for `@odata.nextLink`.
   - No support for more than one level of expand.
   - No support for nesting other query parameters such as `$filter` and `$select` inside an `$expand` query.
 - `$filter`:
-  - `/attachments` endpoint does not support filters. If present, the `$filter` parameter is ignored.
-  - Cross-workload filtering is not supported.
+  - `/attachments` endpoint doesn't support filters. If present, the `$filter` parameter is ignored.
+  - Cross-workload filtering isn't supported.
   - When using the `in` operator, the request is limited to 15 expressions in the filter clause by default OR a URL length of 2,048 characters when using advanced query capabilities.
   - When filtering using the `eq` operator, the maximum limit of the value to match is 120 characters. That is, `$filter=displayName eq 'value-to-match-max-120-char'`. This limitation applies even for properties like **displayName** on directory objects that can be up to 256 characters. When using advanced queries, the limit is applied on the URL length at 2,048 characters instead of the matched value.
 - `$search`:
   - Full-text search is only available for a subset of entities, such as messages.
-  - Cross-workload searching is not supported.
-  - Searching is not supported in Azure AD B2C tenants.
+  - Cross-workload searching isn't supported.
+  - Searching isn't supported in Azure AD B2C tenants.
 - `$count`:
   - Not supported in Azure AD B2C tenants.
-  - When using the `$count=true` query string when querying against directory resources, the `@odata.count` property will be present only on the first page of the paged data.
-- Query parameters specified in a request might fail silently. This can be true for unsupported query parameters as well as for unsupported combinations of query parameters.
+  - When using the `$count=true` query string when querying against directory resources, the `@odata.count` property is present only on the first page of the paged data.
+- Query parameters specified in a request might fail silently. This can be true for unsupported query parameters and for unsupported combinations of query parameters.

concepts/includes/known-issues/sites-lists.md

@@ -5,7 +5,7 @@ ms.date: 02/06/2026
 ms.localizationpriority: medium
 ---
 
-### Follow/unfollow sites is not in sync with SharePoint following
+### Follow/unfollow sites aren't in sync with SharePoint following
 
 <!-- {
   "ms.author": "minc",