Merge pull request #90817 from MashaMSFT/patch-55

Added clarity around pay per usage (Issue 40007)

Author: PRMerger10

articles/virtual-machines/windows/sql/virtual-machines-windows-sql-server-pricing-guidance.md

@@ -59,7 +59,7 @@ You have two options to pay for SQL Server licensing for these editions: *pay pe
 
 ## Pay per usage
 
-**Paying the SQL Server license per usage** means that the per-second cost of running the Azure VM includes the cost of the SQL Server license. You can see the pricing for the different SQL Server editions (Web, Standard, Enterprise) in the Azure VM pricing page for [Windows](https://azure.microsoft.com/pricing/details/virtual-machines/windows) or [Linux](https://azure.microsoft.com/pricing/details/virtual-machines/linux).
+**Paying the SQL Server license per usage** (also known as **pay as you go**) means that the per-second cost of running the Azure VM includes the cost of the SQL Server license. You can see the pricing for the different SQL Server editions (Web, Standard, Enterprise) in the Azure VM pricing page for [Windows](https://azure.microsoft.com/pricing/details/virtual-machines/windows) or [Linux](https://azure.microsoft.com/pricing/details/virtual-machines/linux).
 
 The cost is the same for all versions of SQL Server (2012 SP3 to 2017). The per-second licensing cost depends on the number of VM vCPUs.
 
@@ -69,7 +69,7 @@ Paying the SQL Server licensing per usage is recommended for:
 
 - **Workloads with unknown lifetime or scale**. For example, an app that may not be required in a few months, or which may require more, or less compute power, depending on demand.
 
-To create a SQL Server 2017 Azure VM with one of these pay-per-usage images, see the following links:
+To create a SQL Server 2017 Azure VM with one of these pay-as-you-go images, see the following links:
 
 | Platform | Licensed images |
 |---|---|