case sensitive edits

Author: cindylay

docs/embedded/concepts/admin-exp/developer-admin/dev-admin.md

@@ -8,34 +8,34 @@ ms.localizationpriority: high
 
 ## Overview
 
-Organizations that create file management applications with the help of SharePoint Embedded are referred to as Developer Ecosystem and the persona responsible for the management of the applications is called the developer administrator. Developer administrators can perform various administrative actions on the SharePoint Embedded applications created and on the container types, the blueprint for the Containers that hold the content of instances of the application. They can also create and manage trial container types to get started with the SharePoint Embedded experience, attach billing profiles to their application, etc. In this article, we describe the enterprise manageability features that are supported and can be performed by the developer administrator.
+Organizations that create file management applications with the help of SharePoint Embedded are referred to as Developer Ecosystem and the persona responsible for the management of the applications is called the developer administrator. Developer administrators can perform various administrative actions on the SharePoint Embedded applications created and on the container types, the blueprint for the containers that hold the content of instances of the application. They can also create and manage trial container types to get started with the SharePoint Embedded experience, attach billing profiles to their application, etc. In this article, we describe the enterprise manageability features that are supported and can be performed by the developer administrator.
 
 ## Developer Admin Role
 
 > [!IMPORTANT]
-> Assign the SharePoint Embedded Administrator role available in M365 Admin Center or Microsoft Entra to execute SharePoint Embedded Container commandlets mentioned in this article.
+> Assign the SharePoint Embedded Administrator role available in M365 Admin Center or Microsoft Entra to execute SharePoint Embedded container commandlets mentioned in this article.
 > 
-> Global Administrators can continue to execute SharePoint Embedded Container cmdlets.
+> Global Administrators can continue to execute SharePoint Embedded container cmdlets.
 > 
 > If you are a SharePoint Administrator, grant yourself the SharePoint Embedded Admin role as well to execute these cmdlets.
 
 
 A Microsoft 365 SharePoint Embedded Administrator serves as the developer admin. Global Administrators in Microsoft 365 can assign users the SharePoint Embedded Administrator. The Global Administrator role already has all the permissions of the SharePoint Embedded Administrator role. A SharePoint Administrator can assign themselves the SharePoint Embedded Administrator role to act as a Developer Admin for SharePoint Embedded. The SharePoint Embedded Role is available in Microsoft Entra and Microsoft 365 Admin Center. For information on [SharePoint Embedded Administrator](../adminrole.md) role.
 
-The following are some of the Container specific commands actions currently supported on PowerShell:
-a)	Creation of container types
-- Creation of Standard container type with standard billing
-- Creation of Standard container type with direct to customer billing
-- Creation of Trial container type
+The following are some of the container specific commands actions currently supported on PowerShell:
+* Creation of container types
+  - Creation of Standard container type with standard billing
+  - Creation of Standard container type with direct to customer billing
+  - Creation of Trial container type
 
-b)	container type management
-- Viewing of container types in the developer tenant
-- Editing properties of a container type in the developer tenant
-- Configuration properties of a container type in the developer tenant
-- Manage billing of applications/ container types for standard billing
+* Container type management
+  - Viewing of container types in the developer tenant
+  - Editing properties of a container type in the developer tenant
+  - Configuration properties of a container type in the developer tenant
+  - Manage billing of applications/ container types for standard billing
 
 
-### Billing responsibilities of Developer admin
+### Billing responsibilities of the developer admin
 
 There are two types of billing models followed: 
 
@@ -101,7 +101,7 @@ Set-SPOContainerType -ContainerTypeId <ContainerTypeId>
                      [-WhatIf] [-Confirm]
 ```
 
-### Container Type Configuration Properties
+### Container type configuration properties
 
 The developer administrator can change container type configuration settings using PowerShell commandlets. The following container type properties can be set:
 

docs/embedded/concepts/content-experiences/office-experience.md

@@ -9,14 +9,6 @@ ms.localizationpriority: high
 
 Office File Experiences for SharePoint Embedded platform will work in a similar manner to Microsoft 365 (Microsoft 365) platform.
 
-<!--
-## In this article:
-
-1. [Opening Office Documents from your apps](#Opening-Office-Documents-from-SharePoint-Embedded-Apps)
-2. [View or Restore Previous Versions](#View-or-Restore-a-Previous-Version-of-Office-Document-from-SharePoint-Embedded-Apps)
-3. [Collaborating on SharePoint Embedded Application Office Documents](#Collaborating-on-Office-Documents-from-SharePoint-Embedded-Apps)
-4. [Breadcrumb Properties of SharePoint Embedded Application Office Documents](#Breadcrumb-properties-of-Office-Documents-from-SharePoint-Embedded-Apps)
--->
 
 ## Opening Office Documents from SharePoint Embedded Apps
 
@@ -72,7 +64,7 @@ Breadcrumb properties are used by Office clients to display breadcrumb-style ele
 > [!NOTE]
 > We recommend specifying 'Current Channel' to take advantage of Breadcrumb patterns and future enhancements to Office Apps. Learn more about [specifying update channels for Office Apps](/deployoffice/updates/overview-update-channels)
 
-Breadcrumb patterns for SharePoint Embedded Application Apps are constructed from Container properties configured for your Apps. The following diagram maps the container properties to breadcrumb presentation in Office clients:
+Breadcrumb patterns for SharePoint Embedded Application Apps are constructed from container properties configured for your Apps. The following diagram maps the container properties to breadcrumb presentation in Office clients:
 
 ![Screenshot of breadcrumb pattern in SharePoint Embedded Applications](../../images/office2.png)
 

docs/embedded/concepts/fluid.md

@@ -19,10 +19,10 @@ Start [building](https://github.com/microsoft/FluidExamples/) in the Fluid [Samp
 
 ### Get started with SharePoint Embedded
 
-Try SharePoint Embedded for free by creating a [Trial Container Type](./app-concepts/containertypes.md).
+Try SharePoint Embedded for free by creating a container type for [trial purposes](./app-concepts/containertypes.md).
 
 1. Set up a free trial [Microsoft 365 tenant](https://www.microsoft.com/microsoft-365/enterprise/microsoft365-plans-and-pricing). Alternatively, you can use an existing tenant if you have admin credentials.
-1. Sign into the [SharePoint Embedded Visual Studio Code Extension](.././getting-started/spembedded-for-vscode.md) and follow the steps to create an application and Trial Container Type.
+1. Sign into the [SharePoint Embedded Visual Studio Code Extension](.././getting-started/spembedded-for-vscode.md) and follow the steps to create an application and container type for trial purposes.
 
 ## Prerequisites
 
@@ -32,17 +32,17 @@ To get started building with Fluid Framework, you need:
 1. **SharePoint Embedded Application**: Ensure that you register your application in [Microsoft Entra ID](https://entra.microsoft.com/). If you don't have a SharePoint Embedded application, refer to the [earlier section](#get-started-with-sharepoint-embedded).
 1. **Application (Client) ID**: Obtain the `ClientID` for your SharePoint Embedded Application.
 1. **Container Type Information**:
-   - Identify the `ContainerTypeId` associated with your app’s Container Type.
+   - Identify the `ContainerTypeId` associated with your app’s container type.
 1. **Containers**:
-   - Make sure you have *at least* one Container created of the same Container Type linked to your SharePoint Embedded Application.
+   - Make sure you have *at least* one container created of the same container type linked to your SharePoint Embedded Application.
 
 ## Get started with Fluid
 
 ### Access App information
 
-You need the `ClientID` from your application and the `ContainerTypeId` associated with the Containers created on that application.
+You need the `ClientID` from your application and the `ContainerTypeId` associated with the containers created on that application.
 
-The `ClientID` is essential for acquiring the correct access tokens when working with Fluid Framework and documents. The `ContainerTypeId` is necessary for accessing Containers associated with your SharePoint Embedded application.
+The `ClientID` is essential for acquiring the correct access tokens when working with Fluid Framework and documents. The `ContainerTypeId` is necessary for accessing containers associated with your SharePoint Embedded application.
 
 If you used the [Visual Studio Code Extension](../getting-started/spembedded-for-vscode.md), you can [export](/sharepoint/dev/embedded/getting-started/spembedded-for-vscode#export-postman-environment) your Postman Environment to easily view your both your `ContainerTypeId` and `ClientID`.
 

docs/embedded/concepts/security-and-compliance.md

@@ -11,7 +11,7 @@ Microsoft's SharePoint Embedded provides a faster way to create secure and compl
 
 In this article, we describe the security and compliance policies that are supported today on content that resides in the SharePoint Embedded platform, and their capabilities and limitations.
 
-Since SharePoint Embedded by design doesn’t have any user interface, some Compliance scenarios necessitating user interaction aren't natively supported. The owning application that governs the Container can choose to support these scenarios and provide the optimal experience to end users by using existing Microsoft Graph API.
+Since SharePoint Embedded by design doesn’t have any user interface, some Compliance scenarios necessitating user interaction aren't natively supported. The owning application that governs the container can choose to support these scenarios and provide the optimal experience to end users by using existing Microsoft Graph API.
 
 ## Compliance Policies using Microsoft Purview
 
@@ -23,7 +23,7 @@ Currently, SharePoint Embedded supports the following Compliance features under
     Get-SPOApplication
     ```
 
-1. Retrieve a list of Containers in a SharePoint Embedded application by providing the ApplicationID returned in Step #1
+1. Retrieve a list of containers in a SharePoint Embedded application by providing the ApplicationID returned in Step #1
 
     ```powershell
     Get-SPOContainer -OwningApplicationId <OwningApplicationID>
@@ -35,7 +35,7 @@ Currently, SharePoint Embedded supports the following Compliance features under
     Get-SPOContainer -OwningApplicationId <ApplicationID> -Identity<ContainerID>
     ```
 
-For information on how to retrieve the `ContainerSiteURL` to set the various compliance policies described in this article at a Container level, see [Get-SPOContainer](/powershell/module/sharepoint-online/get-spocontainer).
+For information on how to retrieve the `ContainerSiteURL` to set the various compliance policies described in this article at a container level, see [Get-SPOContainer](/powershell/module/sharepoint-online/get-spocontainer).
 
 ### Audit
 
@@ -52,49 +52,49 @@ In addition to existing file properties, Audit events related to SharePoint Embe
 
 Compliance Admins can use eDiscovery tools in Microsoft Purview to search/hold/export content hosted in the SharePoint Embedded platform. For more information on eDiscovery, see [Microsoft Purview eDiscovery solutions](/purview/ediscovery).
 
-To perform an eDiscovery Search on all SharePoint Embedded content, Admins should select on **'All'** SharePoint Sites when configuring the eDiscovery Search in Microsoft Purview. This enables the Search for content stored in all SharePoint Sites and all SharePoint Embedded Containers.
+To perform an eDiscovery Search on all SharePoint Embedded content, Admins should select on **'All'** SharePoint Sites when configuring the eDiscovery Search in Microsoft Purview. This enables the Search for content stored in all SharePoint Sites and all SharePoint Embedded containers.
 
 ![eDiscovery search](../images/sc2.png)
 
-To limit the eDiscovery Search to one/few SharePoint Embedded Containers, Admins can **'Choose sites'** under the **‘SharePoint sites’** workload and provide the desired Container URL.
+To limit the eDiscovery Search to one/few SharePoint Embedded containers, Admins can **'Choose sites'** under the **‘SharePoint sites’** workload and provide the desired container URL.
 
 ![choose sites in eDiscovery search](../images/sc3.png)
 
 ### Data Lifecycle Management (DLM)
 
 SharePoint Embedded supports retention and holds policies on content stored in its applications using the Microsoft Purview compliance portal. For more information on DLM, see [Learn about Microsoft Purview Data Lifecycle Management](/purview/data-lifecycle-management).
 
-The existing retention policy is applied to all SharePoint Embedded Containers if the policy is configured for 'All sites'. Similarly, creating a new retention/hold policy on *All* SharePoint Sites workload automatically enforces the policy on all SharePoint Sites and all Containers within SharePoint Embedded.
+The existing retention policy is applied to all SharePoint Embedded containers if the policy is configured for 'All sites'. Similarly, creating a new retention/hold policy on *All* SharePoint Sites workload automatically enforces the policy on all SharePoint Sites and all containers within SharePoint Embedded.
 
 ![retention policy](../images/sc4.png)
 
-To selectively enforce the policy on one or more SharePoint Embedded Containers, copy the Container URL and configure the policy to be selectively enforced only on those Containers.
+To selectively enforce the policy on one or more SharePoint Embedded containers, copy the container URL and configure the policy to be selectively enforced only on those containers.
 
 ![enforce retention policy](../images/sc5.png)
 
-Since SharePoint Embedded doesn't have a built-in user interface, DLM scenarios requiring user interaction aren't natively supported. For instance, if an end user attempts to apply a retention label on a Container using a SharePoint Embedded application (app), the app governing the access to the Container must furnish that functionality. In such cases, Graph APIs for DLM functionalities can be used.
+Since SharePoint Embedded doesn't have a built-in user interface, DLM scenarios requiring user interaction aren't natively supported. For instance, if an end user attempts to apply a retention label on a container using a SharePoint Embedded application (app), the app governing the access to the container must furnish that functionality. In such cases, Graph APIs for DLM functionalities can be used.
 
 ### Data Loss Protection (DLP)
 
 Using Microsoft Purview, Admins can identify, monitor, and automatically protect sensitive items stored in applications using SharePoint Embedded. For more information on DLP, see  [Learn about data loss prevention](/purview/dlp-learn-about-dlp).
 
-Like retention policies, DLP policies can be enforced on all SharePoint Sites and SharePoint Embedded Containers by choosing to configure the policy on ‘All sites’.
+Like retention policies, DLP policies can be enforced on all SharePoint Sites and SharePoint Embedded containers by choosing to configure the policy on ‘All sites’.
 
 ![DLP Policy](../images/sc6.png)
 
-Admins can also restrict the enforcement of a DLP policy to specific SharePoint Embedded Containers by specifying the relevant Container URLs during policy configuration.
+Admins can also restrict the enforcement of a DLP policy to specific SharePoint Embedded containers by specifying the relevant container URLs during policy configuration.
 
 ![Configure DLP Policy](../images/sc7.png)
 
 Several scenarios supported by DLP today need user interaction that isn’t natively supported by SharePoint Embedded. For instance, based on its configuration, a DLP policy that prevents external sharing might allow end users to provide a business justification to override the policy. The client app that renders this DLP-flagged file item needs to support such user interactions.
 
 Policy tips are shown today for files hosted in SharePoint so that users are kept informed about DLP-flagged file items and corresponding restrictions. Similarly, for policy tips to be displayed for files hosted in SharePoint Embedded, the client app can choose to provide more support by utilizing the existing Graph APIs for this purpose.
 
-## Security Features
+## Security features
 
-### Sensitivity labels on Containers
+### Sensitivity labels on containers
 
-Global Administrators and SharePoint Administrators can set and remove sensitivity labels on a SharePoint Embedded Container by using the newly created SharePoint PowerShell cmdlet:
+Global Administrators and SharePoint Administrators can set and remove sensitivity labels on a SharePoint Embedded container by using the newly created SharePoint PowerShell cmdlet:
 
 ```powershell
 Set-SPOContainer -Identity <ContainerID/ContainerSiteURL> -SensitivityLabel <SensitivityLabelGUID>
@@ -104,7 +104,7 @@ To learn more about setting sensitivity labels, see [Learn about sensitivity lab
 
 ### Block Download policy
 
-Block Download policy allows SharePoint Administrator or Global Administrator to block the download of files from SharePoint Embedded Containers using the following SharePoint PowerShell cmdlet.
+Block Download policy allows SharePoint Administrator or Global Administrator to block the download of files from SharePoint Embedded containers using the following SharePoint PowerShell cmdlet.
 
 ```powershell
 Set-SPOSite -Identity <ContainerSiteURL> -BlockDownloadPolicy $true