Acrolinx

Author: Michael Bender

articles/load-balancer/load-balancer-ipv6-for-linux.md

@@ -18,7 +18,7 @@ ms.author: mbender
 # Configure DHCPv6 for Linux VMs
 
 
-Some of the Linux virtual-machine images in the Azure Marketplace do not have Dynamic Host Configuration Protocol version 6 (DHCPv6) configured by default. To support IPv6, DHCPv6 must be configured in the Linux OS distribution that you are using. The various Linux distributions configure DHCPv6 in a variety of ways because they use different packages.
+Some of the Linux virtual-machine images in the Azure Marketplace don't have Dynamic Host Configuration Protocol version 6 (DHCPv6) configured by default. To support IPv6, DHCPv6 must be configured in the Linux OS distribution that you're using. The various Linux distributions configure DHCPv6 in various ways because they use different packages.
 
 > [!NOTE]
 > Recent SUSE Linux and CoreOS images in the Azure Marketplace have been pre-configured with DHCPv6. No additional changes are required when you use these images.
@@ -53,6 +53,7 @@ This document describes how to enable DHCPv6 so that your Linux virtual machine
                 dhcp4: true
                 dhcp6: true
     ```
+
 1.  Save the file and reboot.
 
 1. Renew the IPv6 address:
@@ -63,7 +64,7 @@ This document describes how to enable DHCPv6 so that your Linux virtual machine
 
 Beginning with Ubuntu 17.10, the default network configuration mechanism is [NETPLAN]( https://netplan.io).  At install/instantiation time, NETPLAN reads network configuration from YAML configuration files at this location: /{lib,etc,run}/netplan/*.yaml.
 
-Please include a *dhcp6:true* statement for each ethernet interface in your configuration.  For example:
+Include a *dhcp6:true* statement for each ethernet interface in your configuration.  For example:
 
 ```config
 network:
@@ -121,7 +122,7 @@ For reference information about NETPLAN, see https://netplan.io/reference.
 
 ## SLES 11 and openSUSE 13
 
-Recent SUSE Linux Enterprise Server (SLES) and openSUSE images in Azure have been pre-configured with DHCPv6. No additional changes are required when you use these images. If you have a VM that's based on an older or custom SUSE image, do the following:
+Recent SUSE Linux Enterprise Server (SLES) and openSUSE images in Azure have been pre-configured with DHCPv6. No other changes are required when you use these images. If you have a VM that's based on an older or custom SUSE image, follow the steps below:
 
 1. Install the `dhcp-client` package, if needed:
 
@@ -143,7 +144,7 @@ Recent SUSE Linux Enterprise Server (SLES) and openSUSE images in Azure have bee
 
 ## SLES 12 and openSUSE Leap
 
-Recent SLES and openSUSE images in Azure have been pre-configured with DHCPv6. No additional changes are required when you use these images. If you have a VM that's based on an older or custom SUSE image, do the following:
+Recent SLES and openSUSE images in Azure have been pre-configured with DHCPv6. No other changes are required when you use these images. If you have a VM that's based on an older or custom SUSE image, follow the steps below:
 
 1. Edit the */etc/sysconfig/network/ifcfg-eth0* file, and replace the `#BOOTPROTO='dhcp4'` parameter with the following value:
 
@@ -165,7 +166,7 @@ Recent SLES and openSUSE images in Azure have been pre-configured with DHCPv6. N
 
 ## CoreOS
 
-Recent CoreOS images in Azure have been pre-configured with DHCPv6. No additional changes are required when you use these images. If you have a VM based on an older or custom CoreOS image, do the following:
+Recent CoreOS images in Azure have been pre-configured with DHCPv6. No other changes are required when you use these images. If you have a VM based on an older or custom CoreOS image, follow the steps below:
 
 1. Edit the */etc/systemd/network/10_dhcp.network* file: