Merge pull request #8070 from ErikjeMS/win365

PRMerger5 · web-flow · commit 70c3a2151efc · 2022-07-21T13:48:45.000-07:00
more acrolinx fixes 4
diff --git a/windows-365/enterprise/cloud-pc-size-recommendations.md b/windows-365/enterprise/cloud-pc-size-recommendations.md
@@ -41,10 +41,10 @@ This table shows examples of the different sizes available for a Cloud PC:
 | Cloud PC CPUs, RAM, and storage | Example scenarios | Recommended apps |
 | --- | --- | --- | --- |
 | 1vCPU/2GB/64GB\* | Firstline workers, call centers, education/training/CRM access.  | Office (web-based), Microsoft Edge, OneDrive, lightweight line-of-business app (call center application – web-apps), Defender support. |
-| 2vCPU/4GB/256GB<br>2vCPU/4GB/128GB<br>2vCPU/4GB/64GB  | Mergers and acquisition, short-term and seasonal, customer services  | Microsoft 365 Apps, Microsoft Teams (Audio only),  OneDrive, Adobe Reader, Edge, line-of-business apps, Defender support. |
-| 2vCPU/8GB/256GB<br>2vCPU/8GB/128GB | Bring-your-own-PC, work from home, market researchers, government, consultants. | Microsoft 365 Apps, Microsoft Teams, Outlook, Excel, Access, PowerPoint, OneDrive, Adobe Reader, Edge, line-of-business apps, Defender support. |
-| 4vCPU/16GB/512GB<br>4vCPU/16GB/256GB<br>4vCPU/16GB/128GB | Finance, government, consultants, healthcare services, bring-your-own-PC, work from home. | Microsoft 365 Apps, Microsoft Teams, Outlook, Excel, Access, PowerPoint, Power BI, Dynamics 365, OneDrive, Adobe Reader, Edge, line-of-business app, Defender support. |
-| 8vCPU/32GB/512GB<br>8vCPU/32GB/256GB<br>8vCPU/32GB/128GB | Software developers, engineers, content creators, design and engineering workstations. | Microsoft 365 Apps, Microsoft Teams, Outlook, Access, OneDrive, Adobe Reader, Edge, Power BI, Visual Studio Code, virtualization-based workloads: Hyper-V, Windows Subsystem for Linux (WSL), line-of-business apps, and Defender support. |
+| 2vCPU/4GB/256GB<br>2vCPU/4GB/128GB<br>2vCPU/4GB/64GB  | Mergers and acquisition, short-term and seasonal, customer services  | Microsoft 365 Apps, Microsoft Teams (Audio only),  OneDrive, Adobe Reader, Microsoft Edge, line-of-business apps, Defender support. |
+| 2vCPU/8GB/256GB<br>2vCPU/8GB/128GB | Bring-your-own-PC, work from home, market researchers, government, consultants. | Microsoft 365 Apps, Microsoft Teams, Outlook, Excel, Access, PowerPoint, OneDrive, Adobe Reader, Microsoft Edge, line-of-business apps, Defender support. |
+| 4vCPU/16GB/512GB<br>4vCPU/16GB/256GB<br>4vCPU/16GB/128GB | Finance, government, consultants, healthcare services, bring-your-own-PC, work from home. | Microsoft 365 Apps, Microsoft Teams, Outlook, Excel, Access, PowerPoint, Power BI, Dynamics 365, OneDrive, Adobe Reader, Microsoft Edge, line-of-business app, Defender support. |
+| 8vCPU/32GB/512GB<br>8vCPU/32GB/256GB<br>8vCPU/32GB/128GB | Software developers, engineers, content creators, design and engineering workstations. | Microsoft 365 Apps, Microsoft Teams, Outlook, Access, OneDrive, Adobe Reader, Microsoft Edge, Power BI, Visual Studio Code, virtualization-based workloads: Hyper-V, Windows Subsystem for Linux (WSL), line-of-business apps, and Defender support. |
 
 \* The 1vCPU option is being retired. Instead, we recommend the 2vCPU as the minimum configuration for new purchases.
 
diff --git a/windows-365/enterprise/connection-errors.md b/windows-365/enterprise/connection-errors.md
@@ -107,7 +107,7 @@ Connection problems may be caused by settings delivered by group policies. To te
 
 ### On-premises Group Policy Objects (GPO) may affect a Cloud PC's provisioning or behavior
 
-Settings delivered by group policies may cause connection problems. To test this, you can move the Cloud PC to a separate OU that's blocked from receiving group policies.
+Settings delivered by group policies may cause connection problems. To test this problem, you can move the Cloud PC to a separate OU that's blocked from receiving group policies.
 
 ## Next steps
 
diff --git a/windows-365/enterprise/create-custom-image-languages.md b/windows-365/enterprise/create-custom-image-languages.md
@@ -101,7 +101,7 @@ The following steps configure [Group Policy Preferences](/previous-versions/wind
 10. Select **User in group**, then select **OK** and **OK** to complete the new registry process.
 11. In the "Group Policy Management Editor", navigate to **User Configuration** > **Preferences** > **Control Panel Settings**, right-click **Regional Options**, and select **New** > **Regional Options**.
 12. Under **User Locale**, select the language and region combination that matches the registry key you created in a previous step.
-13. After selecting your desired language and region combination from the dropdown, the dropdown menu may be underlined in red. This indicates that the selection isn't confirmed. Press the **F5** function key on your keyboard to confirm the selection, resulting in a green underlined dropdown menu.
+13. After you select your desired language and region combination from the dropdown, the dropdown menu may be underlined in red. This underline indicates that the selection isn't confirmed. Press the **F5** function key on your keyboard to confirm the selection, resulting in a green underlined dropdown menu.
 
     Before hitting **F5**:
 
diff --git a/windows-365/enterprise/create-custom-image-support-teams.md b/windows-365/enterprise/create-custom-image-support-teams.md
@@ -30,7 +30,7 @@ ms.collection: M365-identity-device-management
 
 # Create a Cloud PC custom image that supports Microsoft Teams
 
-During the initial setup of your tenant, we recommend that you provision your Cloud PCs with the Windows 10/11 Enterprise + Microsoft 365 images available in the image gallery. This gives you the benefit of having all the Office applications optimized and pre-installed without the need for any extra level of configuration.
+During the initial setup of your tenant, we recommend that you provision your Cloud PCs with the Windows 10/11 Enterprise + Microsoft 365 images available in the image gallery. These images give you the benefit of having all the Office applications optimized and pre-installed without the need for any extra level of configuration.
 
 If you want to create custom images that don’t include the optimizations for Microsoft Teams, you'll need you perform the following steps in your custom image. These steps make sure your image has the correct registry settings and policies to support Teams.
 
@@ -40,7 +40,7 @@ The following steps are only needed when you aren’t using the Windows 365 gall
     - Name: IsWVDEnvironment
     - Type: DWORD
     - Value: 1
-2. Install the [latest Visual C++ runtime](https://support.microsoft.com/help/2977003/the-latest-supported-visual-c-downloads). This is required for the Teams WebRTC protocol redirection to work.
+2. Install the [latest Visual C++ runtime](https://support.microsoft.com/help/2977003/the-latest-supported-visual-c-downloads). This runtime is required for the Teams WebRTC protocol redirection to work.
 3. Install the [WebRTC Redirector (websocket) plugin](https://query.prod.cms.rt.microsoft.com/cms/api/am/binary/RWNg9F). For instructions on how to install, see [Install the Teams WebSocket Service](/azure/virtual-desktop/teams-on-avd#install-the-teams-websocket-service). The plugin is required for Teams to function properly in a Cloud PC environment with the optimizations.
 
 > [!NOTE]
@@ -51,7 +51,7 @@ The following steps are only needed when you aren’t using the Windows 365 gall
 If you need to verify that Teams optimizations are working on a Cloud PC (for an end user, for example), tell the Cloud PC user to follow these steps:
 
 1. In Microsoft Teams, select the ellipses (**…**) in the menu bar > **About** > **Version**.
-2. Confirm that **WVD Media Optimized** is listed alongside the version. If it is,you’re ready to test the better experience.
+2. Confirm that **WVD Media Optimized** is listed alongside the version. If it is, you’re ready to test the better experience.
 
 If media optimizations loaded successfully, the audio devices and cameras available locally are listed in the device menu. If the menu shows **Remote audio**, follow these steps:
 
diff --git a/windows-365/enterprise/create-device-configuration-profile.md b/windows-365/enterprise/create-device-configuration-profile.md
@@ -30,7 +30,7 @@ ms.collection: M365-identity-device-management
 
 # Create device configuration profile
 
-In this example, we’ll apply a **Device restrictions** [device configuration profile](/mem/intune/configuration/device-profile-create) and apply it to **All Cloud PCs**. You will need either a dynamic device group or a filter to accomplish this task.
+In this example, we’ll apply a **Device restrictions** [device configuration profile](/mem/intune/configuration/device-profile-create) and apply it to **All Cloud PCs**. You'll need either a dynamic device group or a filter to accomplish this task.
 
 > [!NOTE]
 > If you haven’t already, follow the steps to either [create a dynamic device group containing all Cloud PCs](create-dynamic-device-group-all-cloudpcs.md#create-a-dynamic-device-group-for-all-cloud-pcs) or [create a filter for all Cloud PCs](create-filter.md#create-a-filter-for-all-cloud-pcs), then return here to create the device configuration profile.
diff --git a/windows-365/enterprise/create-dynamic-device-group-all-cloudpcs.md b/windows-365/enterprise/create-dynamic-device-group-all-cloudpcs.md
@@ -43,7 +43,7 @@ In these steps, you’ll use the Device Model device property to create the dyna
 1. Sign in to the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431) > **Groups** > **New Group**.
 ![Screenshot of delete policy](./media/create-dynamic-device-group-all-cloudpcs/create-group.png)
 2. Select the **New Group** page, choose **Security** for **Group type**.
-3. Enter the following:
+3. Enter the following information:
     1. **Group name** = "All Cloud PCs" (or some other name indicating it will contain all Cloud PCs).
     2. **Group description** = "A dynamic device group containing all Cloud PC devices"
 4. For **Membership type**, choose **Dynamic Device**.
@@ -64,7 +64,7 @@ In these steps, you’ll use the Enrollment Profile Name device property to crea
 1. Sign in to the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431) > **Groups** > **New Group**.
 ![Screenshot of delete policy](./media/create-dynamic-device-group-all-cloudpcs/create-group.png)
 2. Select the **New Group** page, choose **Security** for **Group type**.
-3. Enter the following:
+3. Enter the following information:
     1. **Group name** = "All UX Engineering Cloud PC devices"
     2. **Group description** = "A dynamic device group containing all UX Engineering Cloud PC devices."
 4. For **Membership type**, choose **Dynamic Device**.
@@ -78,14 +78,14 @@ In these steps, you’ll use the Enrollment Profile Name device property to crea
 
 ## Create a dynamic device group for all Cloud PCs with a specific configuration
 
-For the example below, we use 2 vCPU and 4GB RAM as the configuration. Anywhere you see "2vCPU/4GB" replace it with the desired configuration. You can also target a specific Cloud PC size by adding the OS storage as part of the configuration. You can follow the below steps and create a filter for any of the configurations that make up Cloud PC sizes.
+For the example below, we use 2 vCPU and 4-GB RAM as the configuration. Anywhere you see "2vCPU/4GB" replace it with the desired configuration. You can also target a specific Cloud PC size by adding the OS storage as part of the configuration. You can follow the below steps and create a filter for any of the configurations that make up Cloud PC sizes.
 
-In these steps, you will use the Device Model device property to create the dynamic device group.
+In these steps, you'll use the Device Model device property to create the dynamic device group.
 
 1. Sign in to the [Microsoft Endpoint Manager admin center](https://endpoint.microsoft.com/) > **Groups** > **New Group**.
 ![Screenshot of delete policy](./media/create-dynamic-device-group-all-cloudpcs/create-group.png)
 2. Select the **New Group** page, choose **Security** for **Group type**.
-3. Enter the following:
+3. Enter the following information:
     1. **Group name** = “All 2vCPU/4GB RAM Cloud PCs".
     2. **Group description** = “A dynamic device group containing all Cloud PCs with the 2vCPU/4GB RAM configuration.
 4. For **Membership type**, choose **Dynamic Device**.
diff --git a/windows-365/enterprise/create-dynamic-device-group-for-specific-configuration.md b/windows-365/enterprise/create-dynamic-device-group-for-specific-configuration.md
@@ -30,16 +30,16 @@ ms.collection: M365-identity-device-management
 
 # Create a dynamic device group containing all Cloud PCs of a specific configuration
 
-You might want to apply the same set of policies to all your Cloud PCs with the same computing power (vCPU and RAM). You can do this by creating a dynamic device group containing all Cloud PCs with the same Cloud PC configuration.
+You might want to apply the same set of policies to all your Cloud PCs with the same computing power (vCPU and RAM). You can apply policies like this by creating a dynamic device group containing all Cloud PCs with the same Cloud PC configuration.
 
-For the example below, we use 2 vCPU and 4GB RAM as the configuration. Anywhere you see "2vCPU/4GB" replace it with the desired configuration. You can also target a specific Cloud PC size by adding the OS storage as part of the configuration.
+For the example below, we use 2 vCPU and 4-GB RAM as the configuration. Anywhere you see "2vCPU/4GB" replace it with the desired configuration. You can also target a specific Cloud PC size by adding the OS storage as part of the configuration.
 
-You can follow the below steps and create a dynamic group for any of the configurations that make up Cloud PC sizes. In these steps, you will use the Device Model device property to create the dynamic device group.
+You can follow the below steps and create a dynamic group for any of the configurations that make up Cloud PC sizes. In these steps, you'll use the Device Model device property to create the dynamic device group.
 
 1. Sign in to the [Microsoft Endpoint Manager admin center](https://endpoint.microsoft.com/) > **Groups** > **New Group**.
 ![Screenshot of delete policy](./media/create-dynamic-device-group-all-cloudpcs/create-group.png)
 2. Select the **New Group** page, choose **Security** for **Group type**.
-3. Enter the following:
+3. Enter the following information:
     1. **Group name** = “All 2vCPU/4GB RAM Cloud PCs".
     2. **Group description** = “A dynamic device group containing all Cloud PCs with the 2vCPU/4GB RAM configuration.
 4. For **Membership type**, choose **Dynamic Device**.
diff --git a/windows-365/enterprise/create-dynamic-device-group-from-specific-policy.md b/windows-365/enterprise/create-dynamic-device-group-from-specific-policy.md
@@ -30,7 +30,7 @@ ms.collection: M365-identity-device-management
 
 # Create a dynamic device group containing all Cloud PCs from a specific provisioning policy
 
-You can also apply the same set of policies to all Cloud PCs based on the same image and located in the same region. You can do this by creating a dynamic device group that contains all Cloud PCs provisioned from a specific provisioning policy.
+You can also apply the same set of policies to all Cloud PCs based on the same image and located in the same region. You can apply policies like this by creating a dynamic device group that contains all Cloud PCs provisioned from a specific provisioning policy.
 
 For the example below, we use "UX Engineering" as the name of the provisioning policy. Anywhere you see "UX Engineering" replace it with the name of your provisioning policy.
 
@@ -39,7 +39,7 @@ In these steps, you’ll use the Enrollment Profile Name and Device Model device
 1. Sign in to the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431) > **Groups** > **New Group**.
 ![Screenshot of delete policy](./media/create-dynamic-device-group-all-cloudpcs/create-group.png)
 2. Select the **New Group** page, choose **Security** for **Group type**.
-3. Enter the following:
+3. Enter the following information:
     1. **Group name** = "All UX Engineering Cloud PC devices"
     2. **Group description** = "A dynamic device group containing all UX Engineering Cloud PC devices."
 4. For **Membership type**, choose **Dynamic Device**.
@@ -48,7 +48,7 @@ In these steps, you’ll use the Enrollment Profile Name and Device Model device
     1. **Property** = "enrollmentProfileName"
     2. **Operator** = "Equals"
     3. **Value** = "UX Engineering"
-7. If you used the same enrollment profile name for Windows Autopilot, Apple Device Enrollment, or Android Enterprise enrollment, then you may want to filter on Cloud PCs as well. To do so, select **+ Add expression** to create a second query. Enter the following:
+7. If you used the same enrollment profile name for Windows Autopilot, Apple Device Enrollment, or Android Enterprise enrollment, then you may want to filter on Cloud PCs as well. To do so, select **+ Add expression** to create a second query. Enter the following information:
     - **And/Or** = "And"
     - **Property** = "deviceModel"
     - **Operator** = "Contains"
