Merge pull request #281618 from tomvcassidy/26CSDate

ms.date and acrolinx for three articles

Author: prmerger-automator[bot]

articles/cloud-services/cloud-services-model-and-package.md

@@ -4,7 +4,7 @@ description: Describes the cloud service model (.csdef, .cscfg) and package (.cs
 ms.topic: article
 ms.service: cloud-services
 ms.subservice: deployment-files
-ms.date: 02/21/2023
+ms.date: 07/23/2024
 author: hirenshah1
 ms.author: hirshah
 ms.reviewer: mimckitt
@@ -15,15 +15,15 @@ ms.custom: compute-evergreen
 
 [!INCLUDE [Cloud Services (classic) deprecation announcement](includes/deprecation-announcement.md)]
 
-A cloud service is created from three components, the service definition *(.csdef)*, the service config *(.cscfg)*, and a service package *(.cspkg)*. Both the **ServiceDefinition.csdef** and **ServiceConfig.cscfg** files are XML-based and describe the structure of the cloud service and how it's configured; collectively called the model. The **ServicePackage.cspkg** is a zip file that is generated from the **ServiceDefinition.csdef** and among other things, contains all the required binary-based dependencies. Azure creates a cloud service from both the **ServicePackage.cspkg** and the **ServiceConfig.cscfg**.
+A cloud service is created from three components, the service definition *(.csdef)*, the service config *(.cscfg)*, and a service package *(.cspkg)*. Both the **ServiceDefinition.csdef** and **ServiceConfig.cscfg** files are XML-based and describe the structure of the cloud service and its configuration; collectively called the model. The **ServicePackage.cspkg** is a zip file that is generated from the **ServiceDefinition.csdef** and among other things, contains all the required binary-based dependencies. Azure creates a cloud service from both the **ServicePackage.cspkg** and the **ServiceConfig.cscfg**.
 
-Once the cloud service is running in Azure, you can reconfigure it through the **ServiceConfig.cscfg** file, but you cannot alter the definition.
+Once the cloud service is running in Azure, you can reconfigure it through the **ServiceConfig.cscfg** file, but you can't alter the definition.
 
 ## What would you like to know more about?
 * I want to know more about the [ServiceDefinition.csdef](#csdef) and [ServiceConfig.cscfg](#cscfg) files.
 * I already know about that, give me [some examples](#next-steps) on what I can configure.
 * I want to create the [ServicePackage.cspkg](#cspkg).
-* I am using Visual Studio and I want to...
+* I'm using Visual Studio and I want to...
   * [Create a cloud service][vs_create]
   * [Reconfigure an existing cloud service][vs_reconfigure]
   * [Deploy a Cloud Service project][vs_deploy]
@@ -83,7 +83,7 @@ The **ServiceDefinition.csdef** file specifies the settings that are used by Azu
 </ServiceDefinition>
 ```
 
-You can refer to the [Service Definition Schema](/previous-versions/azure/reference/ee758711(v=azure.100)) for a better understanding of the XML schema used here, however, here is a quick explanation of some of the elements:
+You can refer to the [Service Definition Schema](/previous-versions/azure/reference/ee758711(v=azure.100)) for a better understanding of the XML schema used here, however, here's a quick explanation of some of the elements:
 
 **Sites**  
 Contains the definitions for websites or web applications that are hosted in IIS7.
@@ -114,7 +114,7 @@ Contains tasks that are run when the role starts. The tasks are defined in a .cm
 ## ServiceConfiguration.cscfg
 The configuration of the settings for your cloud service is determined by the values in the **ServiceConfiguration.cscfg** file. You specify the number of instances that you want to deploy for each role in this file. The values for the configuration settings that you defined in the service definition file are added to the service configuration file. The thumbprints for any management certificates that are associated with the cloud service are also added to the file. The [Azure Service Configuration Schema (.cscfg File)](/previous-versions/azure/reference/ee758710(v=azure.100)) provides the allowable format for a service configuration file.
 
-The service configuration file is not packaged with the application, but is uploaded to Azure as a separate file and is used to configure the cloud service. You can upload a new service configuration file without redeploying your cloud service. The configuration values for the cloud service can be changed while the cloud service is running. The following example shows the configuration settings that can be defined for the Web and Worker roles:
+The service configuration file isn't packaged with the application. The configuration uploads to Azure as a separate file and used to configure the cloud service. You can upload a new service configuration file without redeploying your cloud service. The configuration values for the cloud service can be changed while the cloud service is running. The following example shows the configuration settings that can be defined for the Web and Worker roles:
 
 ```xml
 <?xml version="1.0"?>
@@ -134,10 +134,10 @@ The service configuration file is not packaged with the application, but is uplo
 </ServiceConfiguration>
 ```
 
-You can refer to the [Service Configuration Schema](/previous-versions/azure/reference/ee758710(v=azure.100)) for better understanding the XML schema used here, however, here is a quick explanation of the elements:
+You can refer to the [Service Configuration Schema](/previous-versions/azure/reference/ee758710(v=azure.100)) for better understanding the XML schema used here, however, here's a quick explanation of the elements:
 
 **Instances**  
-Configures the number of running instances for the role. To prevent your cloud service from potentially becoming unavailable during upgrades, it is recommended that you deploy more than one instance of your web-facing roles. By deploying more than one instance, you are adhering to the guidelines in the [Azure Compute Service Level Agreement (SLA)](https://azure.microsoft.com/support/legal/sla/), which guarantees 99.95% external connectivity for Internet-facing roles when two or more role instances are deployed for a service.
+Configures the number of running instances for the role. To prevent your cloud service from potentially becoming unavailable during upgrades, we recommend you deploy more than one instance of your web-facing roles. By deploying more than one instance, you adhere to the guidelines in the [Azure Compute Service Level Agreement (SLA)](https://azure.microsoft.com/support/legal/sla/), which guarantees 99.95% external connectivity for Internet-facing roles when two or more role instances are deployed for a service.
 
 **ConfigurationSettings**  
 Configures the settings for the running instances for a role. The name of the `<Setting>` elements must match the setting definitions in the service definition file.
@@ -155,7 +155,7 @@ Configures the certificates that are used by the service. The previous code exam
 ## Defining ports for role instances
 Azure allows only one entry point to a web role. Meaning that all traffic occurs through one IP address. You can configure your websites to share a port by configuring the host header to direct the request to the correct location. You can also configure your applications to listen to well-known ports on the IP address.
 
-The following sample shows the configuration for a web role with a website and web application. The website is configured as the default entry location on port 80, and the web applications are configured to receive requests from an alternate host header that is called “mail.mysite.cloudapp.net”.
+The following sample shows the configuration for a web role with a website and web application. The website is configured as the default entry location on port 80. The web applications are configured to receive requests from an alternate host header that is called “mail.mysite.cloudapp.net”.
 
 ```xml
 <WebRole>
@@ -191,14 +191,14 @@ The following sample shows the configuration for a web role with a website and w
 
 
 ## Changing the configuration of a role
-You can update the configuration of your cloud service while it is running in Azure, without taking the service offline. To change configuration information, you can either upload a new configuration file, or edit the configuration file in place and apply it to your running service. The following changes can be made to the configuration of a service:
+You can update the configuration of your cloud service while it runs in Azure, without taking the service offline. To change configuration information, you can either upload a new configuration file, or edit the configuration file in place and apply it to your running service. The following changes can be made to the configuration of a service:
 
 * **Changing the values of configuration settings**  
   When a configuration setting changes, a role instance can choose to apply the change while the instance is online, or to recycle the instance gracefully and apply the change while the instance is offline.
 * **Changing the service topology of role instances**  
-  Topology changes do not affect running instances, except where an instance is being removed. All remaining instances generally do not need to be recycled; however, you can choose to recycle role instances in response to a topology change.
+  Topology changes don't affect running instances, except where an instance is being removed. All remaining instances generally don't need to be recycled; however, you can choose to recycle role instances in response to a topology change.
 * **Changing the certificate thumbprint**  
-  You can only update a certificate when a role instance is offline. If a certificate is added, deleted, or changed while a role instance is online, Azure gracefully takes the instance offline to update the certificate and bring it back online after the change is complete.
+  You can only update a certificate when a role instance is offline. If a certificate is added, deleted, or changed while a role instance is online, Azure gracefully takes the instance offline to update the certificate. Azure brings it back online after the change is complete.
 
 ### Handling configuration changes with Service Runtime Events
 The [Azure Runtime Library](/previous-versions/azure/reference/mt419365(v=azure.100)) includes the [Microsoft.WindowsAzure.ServiceRuntime](/previous-versions/azure/reference/ee741722(v=azure.100)) namespace, which provides classes for interacting with the Azure environment from a role. The [RoleEnvironment](/previous-versions/azure/reference/ee773173(v=azure.100)) class defines the following events that are raised before and after a configuration change:
@@ -266,7 +266,7 @@ Where the variables are defined as follows:
 | --- | --- |
 | \[DirectoryName\] |The subdirectory under the root project directory that contains the .csdef file of the Azure project. |
 | \[ServiceDefinition\] |The name of the service definition file. By default, this file is named ServiceDefinition.csdef. |
-| \[OutputFileName\] |The name for the generated package file. Typically, this is set to the name of the application. If no file name is specified, the application package is created as \[ApplicationName\].cspkg. |
+| \[OutputFileName\] |The name for the generated package file. Typically, this variable is set to the name of the application. If no file name is specified, the application package is created as \[ApplicationName\].cspkg. |
 | \[RoleName\] |The name of the role as defined in the service definition file. |
 | \[RoleBinariesDirectory] |The location of the binary files for the role. |
 | \[VirtualPath\] |The physical directories for each virtual path defined in the Sites section of the service definition. |
@@ -279,7 +279,7 @@ I'm creating a cloud service package and I want to...
 * [Setup remote desktop for a cloud service instance][remotedesktop]
 * [Deploy a Cloud Service project][deploy]
 
-I am using Visual Studio and I want to...
+I'm using Visual Studio and I want to...
 
 * [Create a new cloud service][vs_create]
 * [Reconfigure an existing cloud service][vs_reconfigure]

articles/cloud-services/cloud-services-nodejs-chat-app-socketio.md

@@ -3,7 +3,7 @@ title: Node.js application using Socket.io - Azure
 description: Socket.IO is now natively supported on Azure. This old tutorial shows how to self-host a socket.IO-based chat application on Azure. The latest recommendation is to let Socket.IO provide real time communication for a Node.js server and clients, and let Azure manage scaling client connections.
 ms.topic: article
 ms.service: cloud-services
-ms.date: 08/31/2023
+ms.date: 07/23/2024
 author: hirenshah1
 ms.author: hirshah
 ms.reviewer: mimckitt
@@ -23,7 +23,7 @@ server and clients. This tutorial walks you through hosting a
 socket.IO based chat application on Azure. For more information
 on Socket.IO, see [socket.io](https://socket.io).
 
-A screenshot of the completed application is below:
+The following screenshot shows the completed application:
 
 ![A browser window displaying the service hosted on Azure][completed-app]
 
@@ -35,7 +35,7 @@ Ensure that the following products and versions are installed to successfully co
 * Install [Python version 2.7.10](https://www.python.org/)
 
 ## Create a Cloud Service Project
-The following steps create the cloud service project that will host the Socket.IO application.
+The following steps create the cloud service project that hosts the Socket.IO application.
 
 1. From the **Start Menu** or **Start Screen**, search for **Windows PowerShell**. Finally, right-click **Windows PowerShell** and select **Run As Administrator**.
 
@@ -60,13 +60,13 @@ The following steps create the cloud service project that will host the Socket.I
     PS C:\Node> Add-AzureNodeWorkerRole
     ```
 
-    You will see the following response:
+    You see the following response:
 
     ![The output of the new-azureservice and add-azurenodeworkerrolecmdlets](./media/cloud-services-nodejs-chat-app-socketio/socketio-1.png)
 
 ## Download the Chat Example
 
-For this project, we will use the chat example from the [Socket.IO
+For this project, we use the chat example from the [Socket.IO
 GitHub repository]. Perform the following steps to download the example
 and add it to the project you previously created.
 
@@ -80,9 +80,9 @@ and add it to the project you previously created.
 
    ![Explorer, displaying the contents of the examples\\chat directory extracted from the archive][chat-contents]
 
-   The highlighted items in the screenshot above are the files copied from the **examples\\chat** directory
+   The highlighted items in the previous screenshot are the files copied from the **examples\\chat** directory
 
-3. In the **C:\\node\\chatapp\\WorkerRole1** directory, delete the **server.js** file, and then rename the **app.js** file to **server.js**. This removes the default **server.js** file created previously by the **Add-AzureNodeWorkerRole** cmdlet and replaces it with the application file from the chat example.
+3. In the **C:\\node\\chatapp\\WorkerRole1** directory, delete the **server.js** file, and then rename the **app.js** file to **server.js**. This step removes the default **server.js** file created previously by the **Add-AzureNodeWorkerRole** cmdlet and replaces it with the application file from the chat example.
 
 ### Modify Server.js and Install Modules
 Before testing the application in the Azure emulator, we must
@@ -91,7 +91,7 @@ server.js file:
 
 1. Open the **server.js** file in Visual Studio or any text editor.
 
-2. Find the **Module dependencies** section at the beginning of server.js and change the line containing **sio = require('..//..//lib//socket.io')** to **sio = require('socket.io')** as shown below:
+2. Find the **Module dependencies** section at the beginning of server.js and change the line containing **sio = require('..//..//lib//socket.io')** to **sio = require('socket.io')** as follows:
 
     ```js
     var express = require('express')
@@ -104,7 +104,7 @@ server.js file:
 
 3. To ensure the application listens on the correct port, open
    server.js in Notepad or your favorite editor, and then change the
-   following line by replacing **3000** with **process.env.port** as shown below:
+   following line by replacing **3000** with **process.env.port** as follows:
 
     ```js
     //app.listen(3000, function () {            //Original
@@ -118,21 +118,21 @@ After saving the changes to **server.js**, use the following steps to
 install required modules, and then test the application in the
 Azure emulator:
 
-1. Using **Azure PowerShell**, change directories to the **C:\\node\\chatapp\\WorkerRole1** directory and use the following command to install the modules required by this application:
+1. In **Azure PowerShell**, change directories to the **C:\\node\\chatapp\\WorkerRole1** directory and use the following command to install the modules required by this application:
 
     ```powershell
     PS C:\node\chatapp\WorkerRole1> npm install
     ```
 
-   This will install the modules listed in the package.json file. After
+   This command installs the modules listed in the package.json file. After
    the command completes, you should see output similar to the
-   following:
+   following screenshot:
 
    ![The output of the npm install command][The-output-of-the-npm-install-command]
 
 2. Since this example was originally a part of the Socket.IO GitHub
    repository, and directly referenced the Socket.IO library by
-   relative path, Socket.IO was not referenced in the package.json
+   relative path, Socket.IO wasn't referenced in the package.json
    file, so we must install it by issuing the following command:
 
     ```powershell
@@ -156,8 +156,8 @@ Azure emulator:
 2. Open a browser and navigate to `http://127.0.0.1`.
 
 3. When the browser window opens, enter a nickname and then hit enter.
-   This will allow you to post messages as a specific nickname. To test
-   multi-user functionality, open additional browser windows using the
+   This step allows you to post messages as a specific nickname. To test
+   multi-user functionality, open more browser windows using the
    same URL and enter different nicknames.
 
    ![Two browser windows displaying chat messages from User1 and User2](./media/cloud-services-nodejs-chat-app-socketio/socketio-8.png)
@@ -193,7 +193,7 @@ messages between different clients using Socket.IO.
 
 ## Next steps
 
-In this tutorial you learned how to create a basic chat application hosted in an Azure Cloud Service. To learn how to host this application in an Azure Website, see [Build a Node.js Chat Application with Socket.IO on an Azure Web Site][chatwebsite].
+In this tutorial, you learned how to create a basic chat application hosted in an Azure Cloud Service. To learn how to host this application in an Azure Website, see [Build a Node.js Chat Application with Socket.IO on an Azure Web Site][chatwebsite].
 
 For more information, see also the [Node.js Developer Center](/azure/developer/javascript/).