Merge pull request #281746 from tomvcassidy/40CSDate

FINAL: ms.date and acrolinx for ten articles

Author: prmerger-automator[bot]

articles/cloud-services-extended-support/schema-cscfg-networkconfiguration.md

@@ -3,15 +3,15 @@ title: Azure Cloud Services (extended support) NetworkConfiguration Schema | Mic
 description: Information related to the network configuration schema for Cloud Services (extended support)
 ms.topic: article
 ms.service: cloud-services-extended-support
-ms.date: 10/14/2020
+ms.date: 07/24/2024
 author: gachandw
 ms.author: gachandw
 ms.reviewer: mimckitt
 ---
 
 # Azure Cloud Services (extended support) config networkConfiguration schema
 
-The `NetworkConfiguration` element of the service configuration file specifies Virtual Network and DNS values. These settings are optional for Cloud Services  (classic).
+The `NetworkConfiguration` element of the service configuration file specifies Virtual Network and Domain Name System (DNS) values. These settings are optional for Cloud Services  (classic).
 
 You can use the following resource to learn more about Virtual Networks and the associated schemas:
 
@@ -61,10 +61,10 @@ The following table describes the child elements of the `NetworkConfiguration` e
 | Rule | Optional. Specifies the action that should be taken for a specified subnet range of IP addresses. The order of the rule is defined by a string value for the `order` attribute. The lower the rule number the higher the priority. For example, rules could be specified with order numbers of 100, 200, and 300. The rule with the order number of 100 takes precedence over the rule that has an order of 200.<br /><br /> The action for the rule is defined by a string for the `action` attribute. Possible values are:<br /><br /> -   `permit` – Specifies that only packets from the specified subnet range can communicate with the endpoint.<br />-   `deny` – Specifies that access is denied to the endpoints in the specified subnet range.<br /><br /> The subnet range of IP addresses that are affected by the rule are defined by a string for the `remoteSubnet` attribute. The description for the rule is defined by a string for the `description` attribute.|
 | EndpointAcl | Optional. Specifies the assignment of access control rules to an endpoint. The name of the role that contains the endpoint is defined by a string for the `role` attribute. The name of the endpoint is defined by a string for the `endpoint` attribute. The name of the set of `AccessControl` rules that should be applied to the endpoint are defined in a string for the `accessControl` attribute. More than one `EndpointAcl` elements can be defined.|
 | DnsServer | Optional. Specifies the settings for a DNS server. You can specify settings for DNS servers without a Virtual Network. The name of the DNS server is defined by a string for the `name` attribute. The IP address of the DNS server is defined by a string for the `IPAddress` attribute. The IP address must be a valid IPv4 address.|
-| VirtualNetworkSite | Mandatory. Specifies the name of the Virtual Network site in which you want deploy your Cloud Service. This setting does not create a Virtual Network Site. It references a site that has been previously defined in the network file for your Virtual Network. A Cloud Service (extended support) can only be a member of one Virtual Network. The name of the Virtual Network site is defined by a string for the `name` attribute.|
-| InstanceAddress | Mandatory. Specifies the association of a role to a subnet or set of subnets in the Virtual Network. When you associate a role name to an instance address, you can specify the subnets to which you want this role to be associated. The `InstanceAddress` contains a Subnets element. The name of the role that is associated with the subnet or subnets is defined by a string for the `roleName` attribute.You need to specify one instance address for each role defined for your cloud service|
+| VirtualNetworkSite | Mandatory. Specifies the name of the Virtual Network site in which you want to deploy your Cloud Service. This setting doesn't create a Virtual Network Site. It references a site previously defined in the network file for your Virtual Network. A Cloud Service (extended support) can only be a member of one Virtual Network. The name of the Virtual Network site is defined by a string for the `name` attribute.|
+| InstanceAddress | Mandatory. Specifies the association of a role to a subnet or set of subnets in the Virtual Network. When you associate a role name to an instance address, you can specify the subnets to which you want this role to be associated. The `InstanceAddress` contains a Subnets element. The name of the role that is associated with the subnet or subnets is defined by a string for the `roleName` attribute. You need to specify one instance address for each role defined for your cloud service|
 | Subnet | Mandatory. Specifies the subnet that corresponds to the subnet name in the network configuration file. The name of the subnet is defined by a string for the `name` attribute.|
-| ReservedIP | Optional. Specifies the reserved IP address that should be associated with the deployment. The allocation method for a reserved IP needs to be specified as `Static` for template and powershell deployments. Each deployment in a Cloud Service can be associated with only one reserved IP address. The name of the reserved IP address is defined by a string for the `name` attribute.|
+| ReservedIP | Optional. Specifies the reserved IP address that should be associated with the deployment. The allocation method for a reserved IP needs to be specified as `Static` for template and PowerShell deployments. Each deployment in a Cloud Service can be associated with only one reserved IP address. The name of the reserved IP address is defined by a string for the `name` attribute.|
 
 ## See also
 [Cloud Service (extended support) Configuration Schema](schema-cscfg-file.md).

articles/cloud-services-extended-support/schema-cscfg-role.md

@@ -3,7 +3,7 @@ title: Azure Cloud Services (extended support) Role Schema | Microsoft Docs
 description: Information related to the role schema for Cloud Services (extended support)
 ms.topic: article
 ms.service: cloud-services-extended-support
-ms.date: 10/14/2020
+ms.date: 07/24/2024
 author: gachandw
 ms.author: gachandw
 ms.reviewer: mimckitt
@@ -15,7 +15,7 @@ The `Role` element of the configuration file specifies the number of role instan
 
 For more information about the Azure Service Configuration Schema, see [Cloud Service (extended support) Configuration Schema](schema-cscfg-file.md). For more information about the Azure Service Definition Schema, see [Cloud Service (extended support) Definition Schema](schema-csdef-file.md).
 
-##  <a name="Role"></a> role element
+##  <a name="Role"></a> Role element
 The following example shows the `Role` element and its child elements.
 
 ```xml 

articles/cloud-services-extended-support/schema-csdef-file.md

@@ -3,7 +3,7 @@ title: Azure Cloud Services (extended support) Definition Schema (csdef File) |
 description: Information related to the definition schema (csdef) for Cloud Services (extended support)
 ms.topic: article
 ms.service: cloud-services-extended-support
-ms.date: 10/14/2020
+ms.date: 07/24/2024
 author: gachandw
 ms.author: gachandw
 ms.reviewer: mimckitt
@@ -18,7 +18,7 @@ By default, the Azure Diagnostics configuration schema file is installed to the
 The default extension for the service definition file is csdef.
 
 ## Basic service definition schema
-The service definition file must contain one `ServiceDefinition` element. The service definition must contain at least one role (`WebRole` or `WorkerRole`) element. It can contain up to 25 roles defined in a single definition and you can mix role types. The service definition also contains the optional `NetworkTrafficRules` element which restricts which roles can communicate to specified internal endpoints. The service definition also contains the optional `LoadBalancerProbes` element which contains customer defined health probes of endpoints.
+The service definition file must contain one `ServiceDefinition` element. The service definition must contain at least one role (`WebRole` or `WorkerRole`) element. It can contain up to 25 roles defined in a single definition and you can mix role types. The service definition also contains the optional `NetworkTrafficRules` element, which restricts which roles can communicate to specified internal endpoints. The service definition also contains the optional `LoadBalancerProbes` element, which contains customer defined health probes of endpoints.
 
 The basic format of the service definition file is as follows.
 
@@ -45,7 +45,7 @@ The basic format of the service definition file is as follows.
 ```
 
 ## Schema definitions
-The following topics describe the schema:
+The following articles describe the schema:
 
 - [LoadBalancerProbe Schema](schema-csdef-loadbalancerprobe.md)
 - [WebRole Schema](schema-csdef-webrole.md)
@@ -60,7 +60,7 @@ The following table describes the attributes of the `ServiceDefinition` element.
 | Attribute               | Description |
 | ----------------------- | ----------- |
 | name                    |Required. The name of the service. The name must be unique within the service account.|
-| topologyChangeDiscovery | Optional. Specifies the type of topology change notification. Possible values are:<br /><br /> -   `Blast` - Sends the update as soon as possible to all role instances. If you choose option, the role should be able to handle the topology update without being restarted.<br />-   `UpgradeDomainWalk` – Sends the update to each role instance in a sequential manner after the previous instance has successfully accepted the update.|
+| topologyChangeDiscovery | Optional. Specifies the type of topology change notification. Possible values are:<br /><br /> -   `Blast` - Sends the update as soon as possible to all role instances. If you choose option, the role should be able to handle the topology update without being restarted.<br />-   `UpgradeDomainWalk` – Sends the update to each role instance in a sequential manner after the previous instance successfully accepts the update.|
 | schemaVersion           | Optional. Specifies the version of the service definition schema. The schema version allows Visual Studio to select the correct SDK tools to use for schema validation if more than one version of the SDK is installed side-by-side.|
 | upgradeDomainCount      | Optional. Specifies the number of upgrade domains across which roles in this service are allocated. Role instances are allocated to an upgrade domain when the service is deployed. For more information, see [Update a Cloud Service role or deployment](sample-update-cloud-service.md) and [Manage the availability of virtual machines](../virtual-machines/availability.md) You can specify up to 20 upgrade domains. If not specified, the default number of upgrade domains is 5.|