Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into work01

Author: Virginia001

articles/automation/automation-dsc-onboarding.md

@@ -15,43 +15,34 @@ manager: carmonm
 
 Azure Automation State Configuration is an Azure service that allows you to write, manage, and
 compile PowerShell Desired State Configuration (DSC)
-[configurations](/powershell/scripting/dsc/configurations/configurations), import [DSC Resources](/powershell/scripting/dsc/resources/resources),
-and assign configurations to target nodes, all in the cloud.
+[configurations](/powershell/scripting/dsc/configurations/configurations). The service also imports [DSC Resources](/powershell/scripting/dsc/resources/resources), and assigns configurations to target nodes, all in the cloud.
 
 ## Why use Azure Automation State Configuration
 
 Azure Automation State Configuration provides several advantages over using DSC outside of Azure.
 
 ### Built-in pull server
 
-Azure Automation State Configuration provides a DSC pull server similar to the
-[Windows Feature DSC-Service](/powershell/scripting/dsc/pull-server/pullserver) so that target nodes automatically receive
-configurations, conform to the desired state, and report back on their compliance. The built-in pull
-server in Azure Automation eliminates the need to set up and maintain your own pull server. Azure
+Azure Automation State Configuration provides a DSC pull server similar to the [Windows Feature DSC-Service](/powershell/scripting/dsc/pull-server/pullserver). Target nodes can automatically receive
+configurations, conform to the desired state, and report on their compliance. The built-in pull server in Azure Automation eliminates the need to set up and maintain your own pull server. Azure
 Automation can target virtual or physical Windows or Linux machines, in the cloud or on-premises.
 
 ### Management of all your DSC artifacts
 
-Azure Automation State Configuration brings the same management layer to
-[PowerShell Desired State Configuration](/powershell/scripting/dsc/overview/overview) as Azure Automation offers for PowerShell scripting.
-
-From the Azure portal, or from PowerShell, you can manage all your DSC configurations, resources,
-and target nodes.
+Azure Automation State Configuration brings the same management layer to [PowerShell Desired State Configuration](/powershell/scripting/dsc/overview/overview) as it offers for PowerShell scripting. From the Azure portal or from PowerShell, you can manage all your DSC configurations, resources, and target nodes.
 
 ![Screenshot of the Azure Automation page](./media/automation-dsc-overview/azure-automation-blade.png)
 
-### Import reporting data into Azure Monitor logs
+### Import of reporting data into Azure Monitor logs
 
-Nodes that are managed with Azure Automation State Configuration send detailed reporting status
-data to the built-in pull server. You can configure Azure Automation State Configuration to send
-this data to your Log Analytics workspace. To learn how to send State Configuration status data to
-your Log Analytics workspace, see [Forward Azure Automation State Configuration reporting data to Azure Monitor logs](automation-dsc-diagnostics.md).
+Nodes that are managed with Azure Automation State Configuration send detailed reporting status data to the built-in pull server. You can configure Azure Automation State Configuration to send
+this data to your Log Analytics workspace. See [Forward Azure Automation State Configuration reporting data to Azure Monitor logs](automation-dsc-diagnostics.md).
 
-## Prerequisites
+## Prerequisites for using Azure Automation State Configuration
 
-Please consider the following requirements when using Azure Automation State Configuration (DSC).
+Please consider the following requirements when using Azure Automation State Configuration for DSC.
 
-### Operating System Requirements
+### Operating system requirements
 
 For nodes running Windows, the following versions are supported:
 
@@ -64,64 +55,56 @@ For nodes running Windows, the following versions are supported:
 - Windows 8.1
 - Windows 7
 
-The [Microsoft Hyper-V Server](/windows-server/virtualization/hyper-v/hyper-v-server-2016)
-standalone product sku does not contain an implementation of Desired State Configuraion
-so it cannot be managed by PowerShell DSC or Azure Automation State Configuration.
-
-For nodes running Linux, the following distros/versions are supported:
+>[!NOTE]
+>The [Microsoft Hyper-V Server](/windows-server/virtualization/hyper-v/hyper-v-server-2016) standalone product SKU does not contain an implementation of DSC. Thus it can't be managed by PowerShell DSC or Azure Automation State Configuration.
 
-The DSC Linux extension supports all the Linux distributions listed under [Supported Linux Distributions](https://github.com/Azure/azure-linux-extensions/tree/master/DSC#4-supported-linux-distributions).
+For nodes running Linux, the DSC Linux extension supports all the Linux distributions listed under [Supported Linux Distributions](https://github.com/Azure/azure-linux-extensions/tree/master/DSC#4-supported-linux-distributions).
 
 ### DSC requirements
 
 For all Windows nodes running in Azure,
 [WMF 5.1](https://docs.microsoft.com/powershell/scripting/wmf/setup/install-configure)
-will be installed during onboarding.  For nodes running Windows Server 2012 and Windows 7,
-[WinRM will be enabled](https://docs.microsoft.com/powershell/scripting/dsc/troubleshooting/troubleshooting#winrm-dependency).
+is installed during onboarding. For nodes running Windows Server 2012 and Windows 7,
+[WinRM](https://docs.microsoft.com/powershell/scripting/dsc/troubleshooting/troubleshooting#winrm-dependency) is enabled.
 
 For all Linux nodes running in Azure,
 [PowerShell DSC for Linux](https://github.com/Microsoft/PowerShell-DSC-for-Linux)
-will be installed during onboarding.
+is installed during onboarding.
 
-### <a name="network-planning"></a>Configure private networks
+### <a name="network-planning"></a>Configuration of private networks
 
-If your nodes are located within a private network,
-the following port and URLs are required for State Configuration (DSC) to communicate with Automation:
+If your nodes are located in a private network, the following port and URLs are required. These resources provide network connectivity for the managed node and allow DSC to communicate with Azure Automation.
 
-* Port: Only TCP 443 is required for outbound internet access.
-* Global URL: *.azure-automation.net
-* Global URL of US Gov Virginia: *.azure-automation.us
-* Agent service: https://\<workspaceId\>.agentsvc.azure-automation.net
+* Port: Only TCP 443 required for outbound internet access
+* Global URL: ***.azure-automation.net**
+* Global URL of US Gov Virginia: ***.azure-automation.us**
+* Agent service: **https://\<workspaceId\>.agentsvc.azure-automation.net**
 
-This provides network connectivity for the managed node to communicate with Azure Automation.
 If you are using DSC resources that communicate between nodes,
 such as the [WaitFor* resources](https://docs.microsoft.com/powershell/scripting/dsc/reference/resources/windows/waitForAllResource),
-you will also need to allow traffic between nodes.
-See the documentation for each DSC resource to understand those network requirements.
+you also need to allow traffic between nodes. See the documentation for each DSC resource to understand these network requirements.
 
-#### Proxy Support
+#### Proxy support
 
-Proxy support for the DSC agent is available in Windows version 1809 and later.
-To configure this option,
-set the value for **ProxyURL** and **ProxyCredential** in the
-[metaconfiguration script](automation-dsc-onboarding.md#generating-dsc-metaconfigurations)
+Proxy support for the DSC agent is available in Windows version 1809 and later. This option is enabled by setting the values for `ProxyURL` and `ProxyCredential` in the [metaconfiguration script](automation-dsc-onboarding.md#generating-dsc-metaconfigurations)
 used to register nodes.
-Proxy is not available in DSC for previous versions of Windows.
 
-For Linux nodes,
-the DSC agent supports proxy and will utilize the http_proxy variable to determine the url.
+>[!NOTE]
+>Azure Automation State Configuration does not provide DSC proxy support for previous versions of Windows.
+
+For Linux nodes, the DSC agent supports proxy and uses the `http_proxy` variable to determine the URL.
 
-#### Azure State Configuration network ranges and namespace
+#### Azure Automation State Configuration network ranges and namespace
 
-It's recommended to use the addresses listed when defining exceptions. For IP addresses you can download the [Microsoft Azure Datacenter IP Ranges](https://www.microsoft.com/download/details.aspx?id=41653). This file is updated weekly, and has the currently deployed ranges and any upcoming changes to the IP ranges.
+It's recommended to use the addresses listed below when defining exceptions. For IP addresses, you can download the [Microsoft Azure Datacenter IP Ranges](https://www.microsoft.com/download/details.aspx?id=41653). This file is updated weekly, and has the currently deployed ranges and any upcoming changes to the IP ranges.
 
 If you have an Automation account that's defined for a specific region, you can restrict communication to that regional datacenter. The following table provides the DNS record for each region:
 
 | **Region** | **DNS record** |
 | --- | --- |
 | West Central US | wcus-jobruntimedata-prod-su1.azure-automation.net</br>wcus-agentservice-prod-1.azure-automation.net |
 | South Central US |scus-jobruntimedata-prod-su1.azure-automation.net</br>scus-agentservice-prod-1.azure-automation.net |
-| East US	| eus-jobruntimedata-prod-su1.azure-automation.net</br>eus-agentservice-prod-1.azure-automation.net |
+| East US    | eus-jobruntimedata-prod-su1.azure-automation.net</br>eus-agentservice-prod-1.azure-automation.net |
 | East US 2 |eus2-jobruntimedata-prod-su1.azure-automation.net</br>eus2-agentservice-prod-1.azure-automation.net |
 | Canada Central |cc-jobruntimedata-prod-su1.azure-automation.net</br>cc-agentservice-prod-1.azure-automation.net |
 | West Europe |we-jobruntimedata-prod-su1.azure-automation.net</br>we-agentservice-prod-1.azure-automation.net |
@@ -138,15 +121,15 @@ For a list of region IP addresses instead of region names, download the [Azure D
 > [!NOTE]
 > The Azure Datacenter IP address XML file lists the IP address ranges that are used in the Microsoft Azure datacenters. The file includes compute, SQL, and storage ranges.
 >
->An updated file is posted weekly. The file reflects the currently deployed ranges and any upcoming changes to the IP ranges. New ranges that appear in the file aren't used in the datacenters for at least one week.
->
-> It's a good idea to download the new XML file every week. Then, update your site to correctly identify services running in Azure. Azure ExpressRoute users should note that this file is used to update the Border Gateway Protocol (BGP) advertisement of Azure space in the first week of each month.
+>An updated file is posted weekly. The file reflects the currently deployed ranges and any upcoming changes to the IP ranges. New ranges that appear in the file aren't used in the datacenters for at least one week. It's a good idea to download the new XML file every week. Then update your site to correctly identify services running in Azure. 
+
+Azure ExpressRoute users should note that this file is used to update the Border Gateway Protocol (BGP) advertisement of Azure space in the first week of each month.
 
 ## Next steps
 
-- To get started, see [Getting started with Azure Automation State Configuration](automation-dsc-getting-started.md)
-- To learn how to onboard nodes, see [Onboarding machines for management by Azure Automation State Configuration](automation-dsc-onboarding.md)
-- To learn about compiling DSC configurations so that you can assign them to target nodes, see [Compiling configurations in Azure Automation State Configuration](automation-dsc-compile.md)
-- For PowerShell cmdlet reference, see [Azure Automation State Configuration cmdlets](/powershell/module/azurerm.automation/#automation)
-- For pricing information, see [Azure Automation State Configuration pricing](https://azure.microsoft.com/pricing/details/automation/)
-- To see an example of using Azure Automation State Configuration in a continuous deployment pipeline, see [Continuous Deployment Using Azure Automation State Configuration and Chocolatey](automation-dsc-cd-chocolatey.md)
+- To get started using DSC in Azure Automation State Configuration, see [Getting started with Azure Automation State Configuration](automation-dsc-getting-started.md).
+- To learn how to onboard nodes, see [Onboarding machines for management by Azure Automation State Configuration](automation-dsc-onboarding.md).
+- To learn about compiling DSC configurations so that you can assign them to target nodes, see [Compiling configurations in Azure Automation State Configuration](automation-dsc-compile.md).
+- For PowerShell cmdlet reference, see [Azure Automation State Configuration cmdlets](/powershell/module/azurerm.automation/#automation).
+- For pricing information, see [Azure Automation State Configuration pricing](https://azure.microsoft.com/pricing/details/automation/).
+- To see an example of using Azure Automation State Configuration in a continuous deployment pipeline, see [Continuous deployment using Azure Automation State Configuration and Chocolatey](automation-dsc-cd-chocolatey.md).

articles/automation/automation-dsc-overview.md

@@ -160,17 +160,15 @@
       maintainContext: true
   - name: Integrate with Apache Kafka
     items:
-      - name: Create Apache Kafka-enabled event hubs
-        href: event-hubs-create-kafka-enabled.md
-      - name: Mirror a Kafka broker in an Apache Kafka-enabled event hub
+      - name: Mirror a Kafka broker in an event hub
         href: event-hubs-kafka-mirror-maker-tutorial.md
-      - name: Connect Apache Spark to an Apache Kafka-enabled event hub
+      - name: Connect Apache Spark to an event hub
         href: event-hubs-kafka-spark-tutorial.md
-      - name: Connect Apache Flink to an Apache Kafka-enabled event hub
+      - name: Connect Apache Flink to an event hub
         href: event-hubs-kafka-flink-tutorial.md
-      - name: Integrate Apache Kafka Connect with a Kafka-enabled event hub (Preview)
+      - name: Integrate Apache Kafka Connect with a hub (Preview)
         href: event-hubs-kafka-connect-tutorial.md
-      - name: Connect Akka Streams to an Apache Kafka-enabled event hub
+      - name: Connect Akka Streams to an event hub
         href: event-hubs-kafka-akka-streams-tutorial.md
   - name: Manage and monitor
     items:

articles/event-hubs/TOC.yml

@@ -338,10 +338,10 @@ String myStringProperty = new String(rawbytes, StandardCharsets.UTF_8);
 ```
 
 ## Next steps
-In this article, you learned how to stream into Kafka-enabled Event Hubs without changing your protocol clients or running your own clusters. To learn more about Event Hubs and Event Hubs for Kafka, see the following articles:  
+In this article, you learned how to stream into Event Hubs without changing your protocol clients or running your own clusters. To learn more about Event Hubs and Event Hubs for Kafka, see the following articles:  
 
 * [Learn about Event Hubs](event-hubs-what-is-event-hubs.md)
 * [Learn about Event Hubs for Kafka](event-hubs-for-kafka-ecosystem-overview.md)
 * [Explore more samples on the Event Hubs for Kafka GitHub](https://github.com/Azure/azure-event-hubs-for-kafka)
-* Use [MirrorMaker](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=27846330) to [stream events from Kafka on premises to Kafka enabled Event Hubs on cloud.](event-hubs-kafka-mirror-maker-tutorial.md)
-* Learn how to stream into Kafka enabled Event Hubs using [native Kafka applications](event-hubs-quickstart-kafka-enabled-event-hubs.md), [Apache Flink](event-hubs-kafka-flink-tutorial.md), or [Akka Streams](event-hubs-kafka-akka-streams-tutorial.md)
+* Use [MirrorMaker](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=27846330) to [stream events from Kafka on premises to Event Hubs on cloud.](event-hubs-kafka-mirror-maker-tutorial.md)
+* Learn how to stream into Event Hubs using [native Kafka applications](event-hubs-quickstart-kafka-enabled-event-hubs.md), [Apache Flink](event-hubs-kafka-flink-tutorial.md), or [Akka Streams](event-hubs-kafka-akka-streams-tutorial.md)

articles/event-hubs/event-hubs-exchange-events-different-protocols.md

@@ -106,7 +106,7 @@ If you use the zone redundancy for your namespace, you need to do a few addition
 Event Hubs provides a Kafka endpoint that can be used by your existing Apache Kafka based applications. A configuration change is all that is required to have the PaaS Kafka experience. It provides an alternative to running your own Kafka cluster. Event Hubs supports Apache Kafka 1.0 and newer client versions and works with your existing Kafka applications, tools, and frameworks. For more information, see [Event Hubs for Kafka repo](https://github.com/Azure/azure-event-hubs-for-kafka).
 
 ### What configuration changes need to be done for my existing application to talk to Event Hubs?
-To connect to a Kafka-enabled Event Hub, you'll need to update the Kafka client configs. It's done by creating an Event Hubs namespace and obtaining the [connection string](event-hubs-get-connection-string.md). Change the bootstrap.servers to point the Event Hubs FQDN and the port to 9093. Update the sasl.jaas.config to direct the Kafka client to your Kafka-enabled Event Hubs endpoint (which is the connection string you've obtained), with correct authentication as shown below:
+To connect to an event hub, you'll need to update the Kafka client configs. It's done by creating an Event Hubs namespace and obtaining the [connection string](event-hubs-get-connection-string.md). Change the bootstrap.servers to point the Event Hubs FQDN and the port to 9093. Update the sasl.jaas.config to direct the Kafka client to your Event Hubs endpoint (which is the connection string you've obtained), with correct authentication as shown below:
 
 bootstrap.servers={YOUR.EVENTHUBS.FQDN}:9093
 request.timeout.ms=60000
@@ -124,8 +124,8 @@ sasl.jaas.config=org.apache.kafka.common.security.plain.PlainLoginModule require
 
 Note: If sasl.jaas.config isn't a supported configuration in your framework, find the configurations that are used to set the SASL username and password and use those instead. Set the username to $ConnectionString and the password to your Event Hubs connection string.
 
-### What is the message/event size for Kafka-enabled Event Hubs?
-The maximum message size allowed for Kafka-enabled Event Hubs is 1 MB.
+### What is the message/event size for Event Hubs?
+The maximum message size allowed for Event Hubs is 1 MB.
 
 ## Throughput units