ms.date and acrolinx for five articles

Author: tomvcassidy

articles/cloud-services/cloud-services-troubleshoot-overconstrained-allocation-request.md

@@ -6,15 +6,15 @@ author: hirenshah1
 ms.author: hirshah
 ms.service: cloud-services
 ms.topic: troubleshooting
-ms.date: 02/21/2023
+ms.date: 07/24/2024
 ms.custom: compute-evergreen
 ---
 
 # Troubleshoot OverconstrainedAllocationRequest when deploying Cloud services (classic) to Azure
 
 [!INCLUDE [Cloud Services (classic) deprecation announcement](includes/deprecation-announcement.md)]
 
-In this article, you'll troubleshoot over constrained allocation failures that prevent deployment of Azure Cloud Services (classic).
+In this article, you troubleshoot over constrained allocation failures that prevent deployment of Azure Cloud Services (classic).
 
 When you deploy instances to a Cloud Service or add new web or worker role instances, Microsoft Azure allocates compute resources.
 
@@ -29,7 +29,7 @@ You may occasionally receive errors during these operations even before you reac
 
 |Exception Type  |Error Message  |
 |---------|---------|
-|OverconstrainedAllocationRequest |The VM size (or combination of VM sizes) required by this deployment cannot be provisioned due to deployment request constraints. If possible, try relaxing constraints such as virtual network bindings, deploying to a hosted service with no other deployment in it and to a different affinity group or with no affinity group, or try deploying to a different region.|
+|OverconstrainedAllocationRequest |The virtual machine (VM) size (or combination of VM sizes) required by this deployment can't be provisioned due to deployment request constraints. If possible, try relaxing constraints such as virtual network bindings. Also try deploying to a hosted service with no other deployment in it and to a different affinity group or with no affinity group. You can try deploying to a different region altogether.|
 
 ## Cause
 
@@ -49,9 +49,9 @@ Follow the guidance for allocation failures in the following scenarios.
 
 ### Not pinned to a cluster
 
-The first time you deploy a Cloud service (classic), the cluster hasn't been selected yet, so the cloud service isn't *pinned*. Azure may have a deployment failure because:
+The first time you deploy a Cloud service (classic), the cluster is unselected, so the cloud service isn't *pinned*. Azure may have a deployment failure because:
 
-- You've selected a particular size that isn't available in the region.
+- You selected a particular size that isn't available in the region.
 - The combination of sizes that are needed across different roles isn't available in the region.
 
 When you experience an allocation error in this scenario, the recommended course of action is to check the available sizes in the region and change the size you previously specified.
@@ -65,7 +65,7 @@ When you experience an allocation error in this scenario, the recommended course
 
 ### Pinned to a cluster
 
-Existing cloud services are *pinned* to a cluster. Any further deployments for the Cloud service (classic) will happen in the same cluster.
+Existing cloud services are *pinned* to a cluster. Any further deployments for the Cloud service (classic) happen in the same cluster.
 
 When you experience an allocation error in this scenario, the recommended course of action is to redeploy to a new Cloud service (classic) (and update the *CNAME*).
 
@@ -97,4 +97,4 @@ For more allocation failure solutions and background information:
 > [!div class="nextstepaction"]
 > [Allocation failures - Cloud service (classic)](cloud-services-allocation-failures.md)
 
-If your Azure issue isn't addressed in this article, visit the Azure forums on [MSDN and Stack Overflow](https://azure.microsoft.com/support/forums/). You can post your issue in these forums, or post to [@AzureSupport on Twitter](https://twitter.com/AzureSupport). You also can submit an Azure support request. To submit a support request, on the [Azure support](https://azure.microsoft.com/support/options/) page, select *Get support*.
+If your Azure issue isn't addressed in this article, visit the Azure forums on [the Microsoft Developer Network (MSDN) and Stack Overflow](https://azure.microsoft.com/support/forums/). You can post your issue in these forums, or post to [@AzureSupport on Twitter](https://twitter.com/AzureSupport). You also can submit an Azure support request. To submit a support request, on the [Azure support](https://azure.microsoft.com/support/options/) page, select *Get support*.

articles/cloud-services/cloud-services-troubleshoot-roles-that-fail-start.md

@@ -3,7 +3,7 @@ title: Troubleshoot roles that fail to start | Microsoft Docs
 description: Here are some common reasons why a Cloud Service role may fail to start. Solutions to these problems are also provided.
 ms.topic: article
 ms.service: cloud-services
-ms.date: 02/21/2023
+ms.date: 07/24/2024
 author: hirenshah1
 ms.author: hirshah
 ms.reviewer: mimckitt
@@ -19,17 +19,17 @@ Here are some common problems and solutions related to Azure Cloud Services role
 [!INCLUDE [support-disclaimer](~/reusable-content/ce-skilling/azure/includes/support-disclaimer.md)]
 
 ## Missing DLLs or dependencies
-Unresponsive roles and roles that are cycling between **Initializing**, **Busy**, and **Stopping** states can be caused by missing DLLs or assemblies.
+Unresponsive roles and roles that are cycling between **Initializing**, **Busy**, and **Stopping** states can be caused by missing dynamic link libraries (DLLs) or assemblies.
 
 Symptoms of missing DLLs or assemblies can be:
 
 * Your role instance is cycling through **Initializing**, **Busy**, and **Stopping** states.
-* Your role instance has moved to **Ready** but if you navigate to your web application, the page does not appear.
+* Your role instance moved to **Ready** but if you navigate to your web application, the page doesn't appear.
 
 There are several recommended methods for investigating these issues.
 
 ## Diagnose missing DLL issues in a web role
-When you navigate to a website that is deployed in a web role, and the browser displays a server error similar to the following, it may indicate that a DLL is missing.
+When you navigate to a website deployed in a web role, and the browser displays a server error similar to the following, it may indicate a DLL is missing.
 
 ![Server Error in '/' Application.](./media/cloud-services-troubleshoot-roles-that-fail-start/ic503388.png)
 
@@ -48,7 +48,7 @@ To view more complete errors without using Remote Desktop:
 4. Save the file.
 5. Repackage and redeploy the service.
 
-Once the service is redeployed, you will see an error message with the name of the missing assembly or DLL.
+Once the service redeploys, you see an error message with the name of the missing assembly or DLL.
 
 ## Diagnose issues by viewing the error remotely
 You can use Remote Desktop to access the role and view more complete error information remotely. Use the following steps to view the errors by using Remote Desktop:
@@ -63,7 +63,7 @@ You can use Remote Desktop to access the role and view more complete error infor
 9. Open Internet Explorer.
 10. Type the address and the name of the web application. For example, `http://<IPV4 Address>/default.aspx`.
 
-Navigating to the website will now return more explicit error messages:
+Navigating to the website now returns more explicit error messages:
 
 * Server Error in '/' Application.
 * Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
@@ -81,10 +81,10 @@ For best results in using this method of diagnosis, you should use a computer or
 1. Install the standalone version of the [Azure SDK](https://azure.microsoft.com/downloads/).
 2. On the development machine, build the cloud service project.
 3. In Windows Explorer, navigate to the bin\debug folder of the cloud service project.
-4. Copy the .csx folder and .cscfg file to the computer that you are using to debug the issues.
+4. Copy the .csx folder and .cscfg file to the computer you're using to debug the issues.
 5. On the clean machine, open an Azure SDK Command Prompt window and type `csrun.exe /devstore:start`.
 6. At the command prompt, type `run csrun <path to .csx folder> <path to .cscfg file> /launchBrowser`.
-7. When the role starts, you will see detailed error information in Internet Explorer. You can also use standard Windows troubleshooting tools to further diagnose the problem.
+7. When the role starts, you see detailed error information in Internet Explorer. You can also use standard Windows troubleshooting tools to further diagnose the problem.
 
 ## Diagnose issues by using IntelliTrace
 For worker and web roles that use .NET Framework 4, you can use [IntelliTrace](/visualstudio/debugger/intellitrace), which is available in Microsoft Visual Studio Enterprise.
@@ -96,8 +96,8 @@ Follow these steps to deploy the service with IntelliTrace enabled:
 3. Once the instance starts, open the **Server Explorer**.
 4. Expand the **Azure\\Cloud Services** node and locate the deployment.
 5. Expand the deployment until you see the role instances. Right-click on one of the instances.
-6. Choose **View IntelliTrace logs**. The **IntelliTrace Summary** will open.
-7. Locate the exceptions section of the summary. If there are exceptions, the section will be labeled **Exception Data**.
+6. Choose **View IntelliTrace logs**. The **IntelliTrace Summary** opens.
+7. Locate the exceptions section of the summary. If there are exceptions, the section is labeled **Exception Data**.
 8. Expand the **Exception Data** and look for **System.IO.FileNotFoundException** errors similar to the following:
 
 ![Exception data, missing file, or assembly](./media/cloud-services-troubleshoot-roles-that-fail-start/ic503390.png)
@@ -107,11 +107,11 @@ To address missing DLL and assembly errors, follow these steps:
 
 1. Open the solution in Visual Studio.
 2. In **Solution Explorer**, open the **References** folder.
-3. Click the assembly identified in the error.
+3. Select the assembly identified in the error.
 4. In the **Properties** pane, locate **Copy Local property** and set the value to **True**.
 5. Redeploy the cloud service.
 
-Once you have verified that all errors have been corrected, you can deploy the service without checking the **Enable IntelliTrace for .NET 4 roles** check box.
+Once you verify all errors are corrected, you can deploy the service without checking the **Enable IntelliTrace for .NET 4 roles** check box.
 
 ## Next steps
 View more [troubleshooting articles](../index.yml?product=cloud-services&tag=top-support-issue) for cloud services.