edit pass: three-workloads-redhat-articles

Author: paulth1

articles/virtual-machines/workloads/redhat/byos.md

@@ -35,7 +35,8 @@ Red Hat Enterprise Linux (RHEL) images are available in Azure via a pay-as-you-g
 - It's currently not possible to dynamically switch between BYOS and pay-as-you-go billing models for Linux images. To switch the billing model, you must redeploy the VM from the respective image.
 
 >[!NOTE]
-> Generation 2 RHEL BYOS images aren't currently available through the marketplace offer. If you require a generation 2 RHEL BYOS image, visit the Cloud Access dashboard in Red Hat subscription management. For more information, see the [Red Hat documentation](https://access.redhat.com/articles/4847681).
+> Generation 2 RHEL BYOS images aren't currently available through the marketplace offer. If you require a 
+Generation 2 RHEL BYOS image, visit the Cloud Access dashboard in Red Hat subscription management. For more information, see the [Red Hat documentation](https://access.redhat.com/articles/4847681).
 
 ## Requirements and conditions to access the Red Hat Gold Images
 
@@ -186,7 +187,7 @@ For steps to apply Azure Disk Encryption, see [Azure Disk Encryption scenarios o
 
 ## Additional information
 
-- If you attempt to provision a VM on a subscription that isn't enabled for this offer, you get the following error:
+- If you attempt to provision a VM on a subscription that isn't enabled for this offer, you get the following message:
 
     ```
     "Offer with PublisherId: redhat, OfferId: rhel-byos, PlanId: rhel-lvm75 is private and can not be purchased by subscriptionId: GUID"

articles/virtual-machines/workloads/redhat/overview.md

@@ -1,6 +1,6 @@
 ---
 title: Red Hat workloads on Azure overview | Microsoft Docs
-description: Learn about the Red Hat product offerings available on Azure
+description: Learn about the Red Hat product offerings available on Azure.
 services: virtual-machines-linux
 author: asinn826
 manager: borisb2015
@@ -13,39 +13,48 @@ ms.author: alsin
 ---
 
 # Red Hat workloads on Azure
+
 Red Hat workloads are supported through a variety of offerings on Azure. Red Hat Enterprise Linux (RHEL) images are at the core of RHEL workloads, as is the Red Hat Update Infrastructure (RHUI).
 
-## Red Hat Enterprise Linux (RHEL) images
-Azure offers a wide offering of RHEL images on Azure. These images are made available through two different licensing models: pay-as-you-go (PAYG), and bring-your-own-subscription (BYOS). New RHEL images on Azure are published when new RHEL versions are released and updated throughout their lifecycles as necessary.
+## Red Hat Enterprise Linux images
+
+Azure offers a wide offering of RHEL images on Azure. These images are made available through two different licensing models: pay-as-you-go and bring-your-own-subscription (BYOS). New RHEL images on Azure are published when new RHEL versions are released and updated throughout their lifecycles, as necessary.
+
+### Pay-as-you-go images
 
-### Pay-as-you-go (PAYG) images
-Azure offers a variety of RHEL PAYG images. These images come properly entitled for RHEL and are attached to a source of updates (Red Hat Update Infrastructure). These images will charge a premium fee for the RHEL entitlement and updates. RHEL PAYG image variants include:
-* Standard RHEL
-* RHEL for SAP
+Azure offers a variety of RHEL pay-as-you-go images. These images come properly entitled for RHEL and are attached to a source of updates (Red Hat Update Infrastructure). These images charge a premium fee for the RHEL entitlement and updates. RHEL pay-as-you-go image variants include:
+
+* Standard RHEL.
+* RHEL for SAP.
 * RHEL for SAP with High Availability and Update Services.
 
-You may want to use the PAYG images if you don't want to worry about paying separately for the appropriate number of subscriptions.
+You might want to use the pay-as-you-go images if you don't want to worry about paying separately for the appropriate number of subscriptions.
+
+### Red Hat Gold Images
 
-### Red Hat Gold Images (`rhel-byos`)
-Azure also offers Red Hat Gold Images. These images may be useful to customers who have existing Red Hat subscriptions and want to use them in Azure. You are required to enable your existing Red Hat subscriptions for Red Hat Cloud Access before you can use them in Azure. Access to these images is granted automatically when your Red Hat subscriptions are enabled for Cloud Access and meet the eligibility requirements. Using these images allows a customer to avoid double-billing that may be incurred from using the PAYG images.
-* [Learn how to enable your Red Hat subscriptions for Cloud Access with Azure](https://access.redhat.com/documentation/en-us/red_hat_subscription_management/1/html/red_hat_cloud_access_reference_guide/con-enable-subs)
-* [Learn how to locate Red Hat Gold Images in the Azure portal, CLI, or PowerShell Cmdlet](./byos.md)
+Azure also offers Red Hat Gold Images (`rhel-byos`). These images might be useful to customers who have existing Red Hat subscriptions and want to use them in Azure. You're required to enable your existing Red Hat subscriptions for Red Hat Cloud Access before you can use them in Azure. Access to these images is granted automatically when your Red Hat subscriptions are enabled for Cloud Access and meet the eligibility requirements. Using these images allows a customer to avoid double billing that might be incurred from using the pay-as-you-go images.
+* Learn how to [enable your Red Hat subscriptions for Cloud Access with Azure](https://access.redhat.com/documentation/en-us/red_hat_subscription_management/1/html/red_hat_cloud_access_reference_guide/con-enable-subs).
+* Learn how to [locate Red Hat Gold Images in the Azure portal, the Azure CLI, or PowerShell cmdlet](./byos.md).
 
 > [!NOTE]
-> Note on double billing: Double billing is incurred when a user pays twice for RHEL subscriptions. This usually happens when a customer uses subscription-manager to attach an entitlement on a RHEL PAYG VM. For example, a customer that uses subscription-manager to attach an entitlement for SAP packages on a RHEL PAYG image will indirectly be double-billed because they will pay twice for RHEL - once through the PAYG premium fee and once through their SAP subscription. This will not happen to BYOS image users.
+> Double billing is incurred when a user pays twice for RHEL subscriptions. This scenario usually happens when a customer uses Red Hat Subscription-Manager to attach an entitlement on a RHEL pay-as-you-go VM. For example, a customer who uses Subscription-Manager to attach an entitlement for SAP packages on a RHEL pay-as-you-go image is indirectly double billed because they pay twice for RHEL. They pay once through the pay-as-you-go premium fee and once through their SAP subscription. This scenario doesn't happen to BYOS image users.
 
 ### Generation 2 images
-Generation 2 VMs provide some newer features compared to Generation 1 VMs. Details are laid out in the [Generation 2 documentation](https://docs.microsoft.com/azure/virtual-machines/linux/generation-2). The key difference from a RHEL image perspective is that Generation 2 VMs use a UEFI instead of BIOS firmware interface, and use a GUID Partition Table (GPT) instead of a master boot record (MBR) on boot time. This allows for, among other things, OS disk sizes larger than 2TB. In addition, the [Mv2 series VMs](../../mv2-series.md) run only on Generation 2 images.
 
-RHEL Generation 2 images are available in the marketplace. Look for "gen2" in the image SKU when listing all images using the Azure CLI, and go to the "Advanced" tab in the VM deploy process to deploy a Generation 2 VM.
+Generation 2 virtual machines (VMs) provide some newer features compared to Generation 1 VMs. For more information, see the [Generation 2 documentation](https://docs.microsoft.com/azure/virtual-machines/linux/generation-2). The key difference from a RHEL image perspective is that Generation 2 VMs use a UEFI instead of BIOS firmware interface. They also use a GUID Partition Table (GPT) instead of a master boot record (MBR) on boot time. Use of a GPT allows for, among other things, OS disk sizes larger than 2 TB. In addition, the [Mv2 series VMs](../../mv2-series.md) run only on Generation 2 images.
 
-## Red Hat Update Infrastructure (RHUI)
-Azure provides Red Hat Update Infrastructure only for PAYG RHEL virtual machines (VMs). RHUI is effectively a mirror of the Red Hat CDNs but is only accessible to the Azure PAYG RHEL VMs. You will have access to the appropriate packages depending on which RHEL image you have deployed. For example, a RHEL for SAP image will have access to the SAP packages in addition to base RHEL packages.
+RHEL Generation 2 images are available in the Azure Marketplace. Look for "gen2" in the image SKU in the list of all images that appears when you use the Azure CLI. Go to the **Advanced** tab in the VM deploy process to deploy a Generation 2 VM.
+
+## Red Hat Update Infrastructure
+
+Azure provides Red Hat Update Infrastructure only for pay-as-you-go RHEL VMs. RHUI is effectively a mirror of the Red Hat CDNs but is only accessible to the Azure pay-as-you-go RHEL VMs. You have access to the appropriate packages depending on which RHEL image you've deployed. For example, a RHEL for SAP image has access to the SAP packages in addition to base RHEL packages.
 
 ### RHUI update behavior
-RHEL images connected to RHUI will, by default, update to the latest minor version of RHEL when a `yum update` is run. This behavior means that a RHEL 7.4 VM may get upgraded to RHEL 7.7 if a `yum update` operation is run on it. This is by design of RHUI. However, this upgrade behavior can be mitigated by switching from regular RHEL repositories to the [Extended Update Support (EUS) repositories](./redhat-rhui.md#rhel-eus-and-version-locking-rhel-vms).
+
+RHEL images connected to RHUI update by default to the latest minor version of RHEL when a `yum update` is run. This behavior means that a RHEL 7.4 VM might get upgraded to RHEL 7.7 if a `yum update` operation is run on it. This behavior is by design for RHUI. To mitigate this upgrade behavior, switch from regular RHEL repositories to [Extended Update Support repositories](./redhat-rhui.md#rhel-eus-and-version-locking-rhel-vms).
 
 ## Next steps
-* Learn more about [RHEL images on Azure](./redhat-images.md)
-* Learn more about [Red Hat Update Infrastructure](./redhat-rhui.md)
-* Learn more about the [Red Hat Gold Image (`rhel-byos`) offer](./byos.md)
+
+* Learn more about [RHEL images on Azure](./redhat-images.md).
+* Learn more about [Red Hat Update Infrastructure](./redhat-rhui.md).
+* Learn more about the [Red Hat Gold Image (`rhel-byos`) offer](./byos.md).

articles/virtual-machines/workloads/redhat/redhat-images.md

@@ -81,7 +81,7 @@ For RHEL 6.x images, the image types are shown in the following table.
 For RHEL 7.x images, there are a few different image types. The following table shows the different sets of images we offer. To see a full list, use the Azure CLI command `az vm image list --publisher redhat --all`.
 
 >[!NOTE]
-> Unless otherwise indicated, all images are LVM partitioned and connect to regular RHEL repositories (that is, not Extended Update Support [EUS] and not E4S). Going forward, we're moving to publishing only LVM-partitioned images but are open to feedback on this decision. For more information on Extended Update Support and Update Services for SAP, see [Red Hat Enterprise Linux life cycle](https://access.redhat.com/support/policy/updates/errata).
+> Unless otherwise indicated, all images are LVM partitioned and connect to regular RHEL repositories. That is, the repositories aren't Extended Update Support (EUS) and aren't Update Services for SAP (E4S). Going forward, we're moving to publishing only LVM-partitioned images but are open to feedback on this decision. For more information on Extended Update Support and Update Services for SAP, see [Red Hat Enterprise Linux life cycle](https://access.redhat.com/support/policy/updates/errata).
 
 |Publisher | Offer | SKU value | Version | Details
 |----------|-------|------------|---------|--------
@@ -103,7 +103,7 @@ Details for RHEL 8 image types are below.
 |Publisher | Offer | SKU value | Version | Details
 |----------|-------|------------|---------|--------
 |RedHat | RHEL | 8 | Concatenated values of the RHEL minor version and the date published (for example, 8.0.20191023) | These images are RHEL 8.0 LVM-partitioned images connected to standard Red Hat repositories.
-|RedHat | RHEL | 8-gen2 | Concatenated values of the RHEL minor version and the date published (for example, 8.0.20191024) | These images are Hyper-V generation 2 RHEL 8.0 LVM-partitioned images connected to standard Red Hat repositories. For more information about generation 2 VMs in Azure, see [Support for generation 2 VMs on Azure](https://docs.microsoft.com/azure/virtual-machines/linux/generation-2).
+|RedHat | RHEL | 8-gen2 | Concatenated values of the RHEL minor version and the date published (for example, 8.0.20191024) | These images are Hyper-V Generation 2 RHEL 8.0 LVM-partitioned images connected to standard Red Hat repositories. For more information about Generation 2 VMs in Azure, see [Support for Generation 2 VMs on Azure](https://docs.microsoft.com/azure/virtual-machines/linux/generation-2).
 
 ## RHEL longer support add-ons
 
@@ -127,7 +127,7 @@ RedHat:RHEL:7-LVM:7.6.2019062414
 RedHat:RHEL:7.6:7.6.2019102813
 ```
 
-In this case, `RedHat:RHEL:7.6:7.6.2019102813` is attached to EUS repositories by default (SKU value of 7.4). And `RedHat:RHEL:7-LVM:7.6.2019062414` is attached to non-EUS repositories by default (SKU value of 7-LVM).
+In this case, `RedHat:RHEL:7.6:7.6.2019102813` is attached to EUS repositories by default. The SKU value is 7.4). And `RedHat:RHEL:7-LVM:7.6.2019062414` is attached to non-EUS repositories by default The SKU value is 7-LVM.
 
 To use regular (non-EUS) repositories, use an image that doesn't contain a minor version number in the SKU.
 
@@ -147,7 +147,7 @@ RHEL 7.5      |RedHat:RHEL:7.5:7.5.2019060305 | Images published June 2019 and l
 RHEL 7.6      |RedHat:RHEL:7.6:7.6.2019052206 | Images published May 2019 and later are EUS by default. |
 RHEL 8.0      |N/A                            | No EUS is available from Red Hat.                               |
 
-### Update Services for SAP (E4S)
+### Update Services for SAP
 
 The latest RHEL for SAP images will be connected to the Update Services for SAP Solutions subscriptions (E4S). For more information about E4S, see the Red Hat [documentation](https://access.redhat.com/support/policy/updates/errata#Update_Services_for_SAP_Solutions).
 
@@ -160,7 +160,7 @@ Images from the following offers created after December 2019 are connected to E4
 
 ## Other available offers and SKUs
 
-The full list of available offers and SKUs might include additional images beyond what is listed in the previous table. An example is `RedHat:rhel-ocp-marketplace:rhel74:7.4.1`. These offers might be used to provide support for specific marketplace solutions. Or, they could be published for previews and testing purposes. They might be changed or removed at any time without warning. Don't use them unless their presence is publicly documented by either Microsoft or Red Hat.
+The full list of available offers and SKUs might include additional images beyond what is listed in the previous table. An example is `RedHat:rhel-ocp-marketplace:rhel74:7.4.1`. These offers might be used to provide support for specific marketplace solutions. Or they could be published for previews and testing purposes. They might be changed or removed at any time without warning. Don't use them unless their presence is publicly documented by either Microsoft or Red Hat.
 
 ## Publishing policy