Merge pull request #262734 from RoseHJM/mdb-faq-seo-update

Updating verbiage for copy paste question

Author: prmerger-automator[bot]

articles/dev-box/dev-box-faq.yml

@@ -50,13 +50,13 @@ sections:
           
           For optimal latency, we recommend creating pools close to the developer's physical location. For example, if a developer is based in India, we recommend creating a dev box in the Central India region. This is generally thought of as a best practice to improve typing speeds as developers work within their dev boxes.  
 
-          Developers primarily spend their time typing and moving their mouse within their Dev Box. We recommend optimizing for typing latency, since these actions will affect development teams the most. 
+          Developers primarily spend their time typing and moving their mouse within their Dev Box. We recommend optimizing for typing latency, since these actions affect development teams the most. 
       
       - question: Can I look up in which regions I should create my pools?  
         answer: |
           Whether you're creating a new pool, or choosing a pool for creating a dev box, it's important to optimize for latency and performance. It can be difficult to determine the optimal region for developers to host their dev boxes.  
 
-          For best results, we recommend that admins ask the developers to use the [Azure Virtual Desktop Experience Estimator](https://aka.ms/avd-estimator). This tool estimates the connection round trip time (RTT) from the developer's physical location, through the Azure Virtual Desktop service, to each Azure region in which you can deploy your dev box. The highlighted region is the region with the lowest RTT from your current location. This is the region where the developer will experience optimal connectivity.  
+          For best results, we recommend that admins ask the developers to use the [Azure Virtual Desktop Experience Estimator](https://aka.ms/avd-estimator). This tool estimates the connection round trip time (RTT) from the developer's physical location, through the Azure Virtual Desktop service, to each Azure region in which you can deploy your dev box. The highlighted region is the region with the lowest RTT from your current location. This is the region where the developer experiences optimal connectivity.  
 
           If there isn't a pool for that region yet, we recommend that you create a new pool for that region or for the next best option according to the estimator.  
      
@@ -78,21 +78,21 @@ sections:
                 [Compare the features of remote desktop clients - Redirections comparison](../virtual-desktop/compare-remote-desktop-clients.md#redirections-comparison)
 
       - question: What if I use Linux as my development environment?
-        answer: Microsoft Dev Box supports Windows Subsystem for Linux (WSL) for Linux scenarios. This enables users to use Linux environment alongside Windows tools. GitHub users who use VS Code for development can use GitHub Codespaces.  
+        answer: Microsoft Dev Box supports Windows Subsystem for Linux (WSL) for Linux scenarios. This support enables users to use Linux environment alongside Windows tools. GitHub users who use VS Code for development can use GitHub Codespaces.  
 
-      - question: What to do when network connection health check fails?
-        answer: Dev Box service is built on top of Windows 365 Enterprise and uses the same [Azure network connection health checks](/windows-365/enterprise/health-checks). Such health checks can make sure that Dev Box provisioning is successful and end-user experiences are optimal. If you see the failure of health check, please click “view details” to see what causes the failure and address the issue from there. Most of the time it can be your network policy that blocks the following service URLs and ports [Network requirements for Windows 365](/windows-365/enterprise/requirements-network?tabs=enterprise%2Cent#allow-network-connectivity).
+      - question: What should I do when a network connection health check fails?
+        answer: Dev Box service is built on top of Windows 365 Enterprise and uses the same [Azure network connection health checks](/windows-365/enterprise/health-checks). Such health checks ensure that Dev Box provisioning is successful and end-user experiences are optimal. If a health check fails, select *view details* to see what is causing the failure and address the issue from there. For example, your network policy might block the following service URLs and ports [Network requirements for Windows 365](/windows-365/enterprise/requirements-network?tabs=enterprise%2Cent#allow-network-connectivity).
 
-      - question: How can I prevent copy/paste between the local device and the remote Dev Box?
-        answer: You can prevent copy/paste between the local device and the remote dev box by disabling the clipboard redirection feature in the RDP client. You can manage this setting through a device configuration policy in Microsoft Intune. For more information, see [RDP device redirection settings](/windows-365/enterprise/manage-rdp-device-redirections#rdp-device-redirection-settings).
+      - question: Is there a policy or a feature to prevent users copying data or code from the Dev Box to their laptop using the clipboard? 
+        answer: You can prevent users copying data or code from the Dev Box to their local machine by disabling the clipboard redirection feature in the RDP client. You can manage this setting through a device configuration policy in Microsoft Intune. For more information, see [RDP device redirection settings](/windows-365/enterprise/manage-rdp-device-redirections#rdp-device-redirection-settings).
 
   - name: Dev Box quota
     questions:
       - question: What is quota?
         answer: |
                 To ensure that resources are available for customers, Microsoft Dev Box has a limit on the number of each type of resource that can be used in a subscription. This limit is called a quota.  
                 There are different types of quota that you can encounter in the Developer portal and Azure portal, such as quota for:  
-                - Dev Box vCPU (This is a quota error you will encounter in devportal.microsoft.com during dev box creation) 
+                - Dev Box vCPU (This is a quota error you'll encounter in devportal.microsoft.com during dev box creation) 
 
                 Or, for Azure portal resource limits:  
                 - Dev Centers 
@@ -101,9 +101,9 @@ sections:
       
       - question: What should I do if I hit a vCPU quota error?  
         answer: |
-                If you are in the developer portal, you may have seen a *QuotaExceeded* error during dev box creation. 
-                If you see this error, please contact your administrator for assistance to increase this quota. You can point them to the documentation on [requesting a quota limit](/azure/dev-box/how-to-request-quota-increase). 
-                If your admin cannot increase the quota limit at this time, please try selecting another pool with a region close to your location.  
+                If you are in the developer portal, you might see a *QuotaExceeded* error during dev box creation. 
+                If you see this error, contact your administrator for assistance to increase this quota. You can point them to the documentation on [requesting a quota limit](/azure/dev-box/how-to-request-quota-increase). 
+                If your admin can't increase the quota limit at this time, try selecting another pool with a region close to your location.  
                 
       - question: How can I check my Dev Box quota?
         answer: |