Merge pull request #83431 from ShawnJackson/sql-virtual-machines

edit pass: sql-virtual-machines

Author: Ja-Dunn

articles/virtual-machines/windows/sql/virtual-machines-windows-ps-sql-keyvault.md

@@ -50,7 +50,7 @@ For a detailed walkthrough of provisioning, see [Provision a SQL Server virtual
 
 [!INCLUDE [windows-virtual-machines-sql-use-new-management-blade](../../../../includes/windows-virtual-machines-sql-new-resource.md)]
 
-For existing SQL Server virtual machines, open your [SQL virtual machines resource](virtual-machines-windows-sql-manage-portal.md#access-sql-virtual-machine-resource) and select **Security** under **Settings**. Select **Enable** to enable Azure Key Vault integration. 
+For existing SQL Server virtual machines, open your [SQL virtual machines resource](virtual-machines-windows-sql-manage-portal.md#access-the-sql-virtual-machines-resource) and select **Security** under **Settings**. Select **Enable** to enable Azure Key Vault integration. 
 
 ![SQL AKV Integration for existing VMs](./media/virtual-machines-windows-ps-sql-keyvault/azure-sql-rm-akv-existing-vms.png)
 

articles/virtual-machines/windows/sql/virtual-machines-windows-sql-ahb.md

@@ -133,7 +133,7 @@ In the **SQL Server settings** tab, select **Enable** under **Automated backup**
 
 [!INCLUDE [windows-virtual-machines-sql-use-new-management-blade](../../../../includes/windows-virtual-machines-sql-new-resource.md)]
 
-For existing SQL Server virtual machines, navigate to the [SQL virtual machines resource](virtual-machines-windows-sql-manage-portal.md#access-sql-virtual-machine-resource) and then select **Backups** to configure your automated backups.
+For existing SQL Server virtual machines, navigate to the [SQL virtual machines resource](virtual-machines-windows-sql-manage-portal.md#access-the-sql-virtual-machines-resource) and then select **Backups** to configure your automated backups.
 
 ![SQL Automated Backup for existing VMs](./media/virtual-machines-windows-sql-automated-backup-v2/sql-server-configuration.png)
 

articles/virtual-machines/windows/sql/virtual-machines-windows-sql-automated-backup-v2.md

@@ -81,7 +81,7 @@ In the **SQL Server settings** tab, scroll down to **Automated backup** and sele
 [!INCLUDE [windows-virtual-machines-sql-use-new-management-blade](../../../../includes/windows-virtual-machines-sql-new-resource.md)]
 
 For existing SQL Server virtual machines, navigate to the 
-[SQL virtual machines resource](virtual-machines-windows-sql-manage-portal.md#access-sql-virtual-machine-resource) and then select **Backups**. 
+[SQL virtual machines resource](virtual-machines-windows-sql-manage-portal.md#access-the-sql-virtual-machines-resource) and then select **Backups**. 
 
 ![SQL Automated Backup for existing VMs](./media/virtual-machines-windows-sql-automated-backup/azure-sql-rm-autobackup-existing-vms.png)
 

articles/virtual-machines/windows/sql/virtual-machines-windows-sql-automated-backup.md

@@ -85,7 +85,7 @@ For context, see the complete topic on [provisioning a SQL Server virtual machin
 
 [!INCLUDE [windows-virtual-machines-sql-use-new-management-blade](../../../../includes/windows-virtual-machines-sql-new-resource.md)]
 
-For existing SQL Server virtual machines, open your [SQL virtual machines resource](virtual-machines-windows-sql-manage-portal.md#access-sql-virtual-machine-resource) and select **Patching** under **Settings**. 
+For existing SQL Server virtual machines, open your [SQL virtual machines resource](virtual-machines-windows-sql-manage-portal.md#access-the-sql-virtual-machines-resource) and select **Patching** under **Settings**. 
 
 ![SQL Automatic Patching for existing VMs](./media/virtual-machines-windows-sql-automated-patching/azure-sql-rm-patching-existing-vms.png)
 

articles/virtual-machines/windows/sql/virtual-machines-windows-sql-automated-patching.md

@@ -1,5 +1,5 @@
 ---
-title: How to perform an in-place upgrade of SQL Server edition on Azure VM| Microsoft Docs
+title: Perform an in-place upgrade of a SQL Server edition on an Azure VM| Microsoft Docs
 description: Learn how to change the edition of your SQL Server VM in Azure. 
 services: virtual-machines-windows
 documentationcenter: na
@@ -16,83 +16,82 @@ ms.author: mathoma
 ms.reviewer: jroth
 
 ---
-# How to perform an in-place upgrade of SQL Server edition on Azure VM
+# Perform an in-place upgrade of a SQL Server edition on an Azure VM
 
-This article describes how to change the edition of SQL Server for an existing SQL Server on a Windows virtual machine in Azure. 
+This article describes how to change the edition of SQL Server on a Windows virtual machine in Azure. 
 
-The edition of SQL Server is determined by the product key, and is specified with the installation process. The edition dictates what [features](/sql/sql-server/editions-and-components-of-sql-server-2017) are available within the SQL Server product. You can change the SQL Server edition with the installation media and either downgrade to reduce cost or upgrade to enable more features.
+The edition of SQL Server is determined by the product key, and is specified with the installation process. The edition dictates what [features](/sql/sql-server/editions-and-components-of-sql-server-2017) are available in the SQL Server product. You can change the SQL Server edition with the installation media and either downgrade to reduce cost or upgrade to enable more features.
 
-If you updated the edition of SQL Server using the installation media after registering with the SQL VM resource provider, then to update the Azure billing accordingly you should set the SQL Server Edition Property of the SQL VM resource as follows:
+If you updated the edition of SQL Server by using the installation media after registering with the SQL VM resource provider, then to update the Azure billing accordingly, you should set the SQL Server edition property of the SQL VM resource as follows:
 
-1. Sign into the [Azure portal](https://portal.azure.com). 
-1. Navigate to your SQL Server virtual machine resource. 
-1. Under **Settings**, select **Configure** and then select your desired edition of SQL Server from the drop-down under **Edition**. 
+1. Sign in to the [Azure portal](https://portal.azure.com). 
+1. Go to your SQL Server virtual machine resource. 
+1. Under **Settings**, select **Configure**. Then select your desired edition of SQL Server from the drop-down list under **Edition**. 
 
    ![Change edition metadata](media/virtual-machines-windows-sql-change-edition/edition-change-in-portal.png)
 
-1. Review the warning notifying you that you must change SQL Server edition first, and that edition property must match SQL Server edition. 
+1. Review the warning that says you must change the SQL Server edition first, and that the edition property must match the SQL Server edition. 
 1. Select **Apply** to apply your edition metadata changes. 
 
 
 ## Prerequisites
 
-To do an in-place change of the edition of SQL Server, you will need the following: 
+To do an in-place change of the edition of SQL Server, you need the following: 
 
 - An [Azure subscription](https://azure.microsoft.com/free/).
-- A Windows [SQL Server VM](https://docs.microsoft.com/azure/virtual-machines/windows/sql/virtual-machines-windows-portal-sql-server-provision) registered with the [SQL VM resource provider](virtual-machines-windows-sql-register-with-resource-provider.md).
-- Setup media with the desired edition of SQL Server. Customers who have [software assurance](https://www.microsoft.com/licensing/licensing-programs/software-assurance-default) can obtain their installation media from the [Volume Licensing Center](https://www.microsoft.com/Licensing/servicecenter/default.aspx). Customers do not have software assurance can use the setup media from a marketplace SQL Server VM image that has their desired edition.
+- A [SQL Server VM on Windows](https://docs.microsoft.com/azure/virtual-machines/windows/sql/virtual-machines-windows-portal-sql-server-provision) registered with the [SQL VM resource provider](virtual-machines-windows-sql-register-with-resource-provider.md).
+- Setup media with the desired edition of SQL Server. Customers who have [Software Assurance](https://www.microsoft.com/licensing/licensing-programs/software-assurance-default) can obtain their installation media from the [Volume Licensing Center](https://www.microsoft.com/Licensing/servicecenter/default.aspx). Customers who don't have Software Assurance can use the setup media from an Azure Marketplace SQL Server VM image that has their desired edition.
 
 
-## Upgrade edition
+## Upgrade an edition
 
-  > [!WARNING]
-  > - **Upgrading the edition of SQL Server will restart the service for SQL Server, as well as any associated services, such as Analysis Services and R Services.** 
+> [!WARNING]
+> Upgrading the edition of SQL Server will restart the service for SQL Server, along with any associated services, such as Analysis Services and R Services. 
 
-To upgrade the edition of SQL Server, obtain the SQL Server setup media for the desired edition of SQL Server, and then do the following:
+To upgrade SQL Server, obtain the SQL Server setup media for the desired edition of SQL Server, and then do the following:
 
-1. Launch Setup.exe from the SQL Server installation media. 
-1. Navigate to **Maintenance** and choose the **Edition Upgrade** option. 
+1. Open Setup.exe from the SQL Server installation media. 
+1. Go to **Maintenance** and choose the **Edition Upgrade** option. 
 
-   ![Upgrade edition of SQL Server](media/virtual-machines-windows-sql-change-edition/edition-upgrade.png)
+   ![Selection for upgrading the edition of SQL Server](media/virtual-machines-windows-sql-change-edition/edition-upgrade.png)
 
-1. Select **Next** until you reach the **Ready to upgrade edition** page, and then select **Upgrade**. The setup window may hang for a few minutes while the change is taking effect, and then you will see a **Complete** page confirming that your edition upgrade is complete. 
+1. Select **Next** until you reach the **Ready to upgrade edition** page, and then select **Upgrade**. The setup window might stop responding for a few minutes while the change is taking effect. A **Complete** page will confirm that your edition upgrade is finished. 
 
-After SQL Server edition is upgraded, you should modify the "Edition" property of the Sql Virtual Machine on Azure portal as shown above; this will update the metadata and billing associated with this VM.
+After the SQL Server edition is upgraded, modify the edition property of the SQL Server virtual machine in the Azure portal as shown earlier. This will update the metadata and billing associated with this VM.
 
-## Downgrade edition
+## Downgrade an edition
 
-  > [!WARNING]
-  > - **Downgrading the edition of SQL Server requires completely uninstalling SQL Server, which may incur additional downtime**. 
+To downgrade the edition of SQL Server, you need to completely uninstall SQL Server, and reinstall it again with the desired edition setup media.
 
-
-To downgrade the edition of SQL Server, you will need to completely uninstall SQL Server, and reinstall it again with the desired edition setup media. 
+> [!WARNING]
+> Uninstalling SQL Server might incur additional downtime. 
 
 You can downgrade the edition of SQL Server by following these steps:
 
 1. Back up all databases, including the system databases. 
 1. Move system databases (master, model, and msdb) to a new location. 
 1. Completely uninstall SQL Server and all associated services. 
 1. Restart the virtual machine. 
-1. Install SQL Server using the media with the desired edition of SQL Server.
+1. Install SQL Server by using the media with the desired edition of SQL Server.
 1. Install the latest service packs and cumulative updates.  
-1. Replace the new system databases that were created during installation with the system databases you previously moved to a different location. 
+1. Replace the new system databases that were created during installation with the system databases that you previously moved to a different location. 
 
-Once the SQL Server edition is downgraded, you should modify the 'Edition' property of the SQL virtual machine within the Azure portal as shown above; this will update the metadata and billing associated with this VM.
+After the SQL Server edition is downgraded, modify the edition property of the SQL Server virtual machine in the Azure portal as shown earlier. This will update the metadata and billing associated with this VM.
 
 ## Remarks
 
- - The edition property for the SQL Server VM must match the edition of the SQL Server installed to the virtual machine for all SQL Virtual Machines including both PAYG and BYOL license types.
- - If you drop your SQL Server VM resource, you will go back to the hard-coded edition setting of the image.
-  - The ability to change the edition is a feature of the SQL VM resource provider. Deploying a marketplace image through the Azure portal automatically registers a SQL Server VM with the resource provider. However, customers who are self-installing SQL Server will need to manually [register their SQL Server VM](virtual-machines-windows-sql-register-with-resource-provider.md).
-- Adding a SQL Server VM to an availability set requires recreating the VM. As such, any VMs added to an availability set will go back to the default edition and the edition will need to be modified again.
+- The edition property for the SQL Server VM must match the edition of the SQL Server instance installed for all SQL Server virtual machines, including both pay-as-you-go and bring-your-own-license types of licenses.
+- If you drop your SQL Server VM resource, you will go back to the hard-coded edition setting of the image.
+- The ability to change the edition is a feature of the SQL VM resource provider. Deploying an Azure Marketplace image through the Azure portal automatically registers a SQL Server VM with the resource provider. However, customers who are self-installing SQL Server will need to manually [register their SQL Server VM](virtual-machines-windows-sql-register-with-resource-provider.md).
+- Adding a SQL Server VM to an availability set requires re-creating the VM. Any VMs added to an availability set will go back to the default edition, and the edition will need to be modified again.
 
 ## Next steps
 
 For more information, see the following articles: 
 
 * [Overview of SQL Server on a Windows VM](virtual-machines-windows-sql-server-iaas-overview.md)
-* [SQL Server on a Windows VM FAQ](virtual-machines-windows-sql-server-iaas-faq.md)
-* [SQL Server on a Windows VM pricing guidance](virtual-machines-windows-sql-server-pricing-guidance.md)
-* [SQL Server on a Windows VM release notes](virtual-machines-windows-sql-server-iaas-release-notes.md)
+* [FAQ for SQL Server on a Windows VM](virtual-machines-windows-sql-server-iaas-faq.md)
+* [Pricing guidance for SQL Server on a Windows VM](virtual-machines-windows-sql-server-pricing-guidance.md)
+* [Release notes for SQL Server on a Windows VM](virtual-machines-windows-sql-server-iaas-release-notes.md)