Contact support fixes

Author: RoseHJM

articles/dev-box/how-to-resolve-dev-box-connectivity-issues.md

@@ -30,7 +30,7 @@ Before proceeding with troubleshooting, ensure that your Remote Desktop app is u
 
 Any improper network configurations on your Dev Box can disrupt Remote Desktop connections. 
 
-Additionally, if you haven't accessed your Dev Box in the past three months, check if Microsoft Entra ID removed you due to inactivity. To regain access, contact the Cloud PC Service support team.
+Additionally, if you haven't accessed your Dev Box for some time, check whether your organization has a policy that removes users from Microsoft Entra ID due to inactivity. To regain access, contact your support team.
 
 ### Step 0: Preliminary Checks
 - **Internet Connection:** Verify that your local machine has an active internet connection.
@@ -39,15 +39,15 @@ Additionally, if you haven't accessed your Dev Box in the past three months, che
 
 ### Step 1: Windows Update and App Restart
 - **Pending Updates:** If Windows is updating, it can take up to 30 minutes, during which your Dev Box won't connect.
-- **Restart Remote Desktop:** Close all instances of the Remote Desktop app, terminate any 'msrdc.exe' and 'msrdcw.exe' processes via Task Manager, and then reopen the app to attempt reconnection.
+- **Restart Remote Desktop:** Close all instances of the Remote Desktop app, terminate any 'msrdc.exe' and 'msrdcw.exe' processes via Task Manager, and then to attempt reconnection, reopen the app.
 
 ### Step 2: Address App Hang and Authentication Issues
 - **App Hang:** If the Remote Desktop app hangs, capture a process dump of MSRDC.exe and create a support request. Restart your computer and try connecting again.
-- **Authentication Errors:** If denied sign-in despite correct credentials, check the join status using `dsregcmd.exe /status`. Resolve any errors with the helpdesk and restart your computer. If authentication errors persist, unsubscribe and resubscribe to your Dev Box pool in the app. 
+- **Authentication Errors:** If denied sign-in despite correct credentials, check the join status using `dsregcmd.exe /status`. Resolve any errors with your support team and restart your computer. If authentication errors persist, unsubscribe and resubscribe to your Dev Box pool in the app. 
 
 ### Step 3: Browser Client Connection
 - **Browser Access:** Attempt to connect via the browser client by visiting https://DevBox.microsoft.com and selecting "Open in browser".
-- **Black Screen Issue:** If the RDP window is black, "Shutdown" or "Stop" your Dev Box via the portal and restart it.
+- **Black Screen Issue:** If the Remote Desktop Protocol (RDP) window is black, "Shutdown" or "Stop" your Dev Box via the portal and restart it.
 
 ### Step 4: Connection Drops During High CPU Load
 **Registry Adjustment:** If you experience frequent connection drops with the Remote Desktop app during high CPU load, ensure your Dev Box has the latest Windows 11 build. Set the `SetGpuRealtimePriority` registry value to DWORD 2 in the Dev Box and restart.
@@ -85,7 +85,7 @@ You can set the `fClientDisableUDP` registry value by using this command in an e
 reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client" /v fClientDisableUDP /d 1 /t REG_DWORD
 ```
 
-#### Use TCP instead of UDP - Group policy
+#### Use TCP instead of UDP - Group policy:
 Alternatively, use Group Policy Editor on your Dev Box to set RDP transport protocols to "Use only TCP".
 
 1. Open the Group Policy Editor on your Dev Box.
@@ -94,7 +94,7 @@ Alternatively, use Group Policy Editor on your Dev Box to set RDP transport prot
 4. Set it to **Enabled**.
 5. For **Select Transport Type**, select **Use only TCP**.
 
-If the preceding steps don't resolve your issue, contact the Dev Box team support by creating an incident [here]. For urgent or widespread issues, raise the priority of the incident or email the Dev Box team directly at [email protected]. 
+If the preceding steps don't resolve your issue, contact your support team. 
 
 Include the following details in your incident report:
 
@@ -103,11 +103,11 @@ Include the following details in your incident report:
 - A detailed description of the problem
 - The Activity ID from your Remote Desktop session, if available. You can find this ID by clicking on the connection bar during your session.
 
-   :::image type="content" source="media/how-to-resolve-dev-box-connectivity-issues/troubleshooting-connection-bar.png" alt-text="Alt text":::
+   :::image type="content" source="media/how-to-resolve-dev-box-connectivity-issues/troubleshooting-connection-bar.png" alt-text="Screenshot of the Remote Desktop connection bar.":::
 
 - Include information from the connection dialog.
 
-   :::image type="content" source="media/how-to-resolve-dev-box-connectivity-issues/troubleshooting-connection-information-dialog.png" alt-text="alt text":::
+   :::image type="content" source="media/how-to-resolve-dev-box-connectivity-issues/troubleshooting-connection-information-dialog.png" alt-text="Troubleshooting connection information dialog for resolving Dev Box connectivity issues.":::
 
 In macOS clients, use the terminal to change connections to TCP instead of UDP:
 
@@ -124,3 +124,4 @@ defaults write com.microsoft.rdc.osx.beta ClientSettings.EnableAvdUdpSideTranspo
 
 ## Related content
 - [Troubleshoot and resolve dev box Remote Desktop connectivity issues](how-to-troubleshoot-repair-dev-box.md)
+- [Get support for Microsoft Dev Box](how-to-get-help.md)