Update spot-placement-score.md

Author: am4234m

articles/virtual-machines/spot-placement-score.md

@@ -14,37 +14,37 @@ ms.reviewer: ju-shim
 > The Spot Placement Score feature is currently in PREVIEW. See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
 
 # Spot Placement Score (Preview)
-Spot Placement Score evaluates the likelihood of success for individual Spot deployments by considering parameters like desired Spot Virtual Machine (VM) count, VM size, and your deployment region or zone. This feature enables you to generate a placement score to deploy a desired number of Spot Virtual Machines (VMs) across various combinations of regions, zones, and VM sizes. By inputting lists of up to 8 regions and 5 VM sizes, you can obtain placement scores categorized as either High, Medium, or Low. A score of High indicates that the deployment is highly likely to succeed while a score of Low indicates that the deployment has a low chance of success. These scores are based on analyses of Spot capacity allocation probability and the survivability of the specified number of Spot VMs within each region and VM size combination. This functionality enhances deployment planning by providing predictive insights into deployment success and optimizing resource allocation for your Spot VMs. 
+Spot Placement Score evaluates the likelihood of success for individual Spot deployments by considering parameters like desired Spot Virtual Machine (VM) count, VM size, and your deployment region or zone. This feature enables you to generate a placement score to deploy a desired number of Spot Virtual Machines (VMs) across various combinations of regions, zones, and VM sizes. By inputting lists of up to eight regions and five VM sizes, you can obtain placement scores categorized as either High, Medium, or Low. A score of High indicates that the deployment is highly likely to succeed while a score of Low indicates that the deployment has a low chance of success. These scores are based on analyses of Spot capacity allocation probability and the survivability of the specified number of Spot VMs within each region and VM size combination. This functionality enhances deployment planning by providing predictive insights into deployment success and optimizing resource allocation for your Spot VMs. 
 
 Using Spot Placement Score, you can achieve the following: 
 
 - A clear evaluation of how likely your Spot deployment is to succeed based on specified parameters. 
 
 - Identify the most suitable combination of regions and VM sizes to maximize Spot VM availability and survivability based on placement scores. 
 
-- Improve the overall success rate of deploying Spot VMs by leveraging data-driven placement scores, reducing the risk of capacity issues or failures during deployment. 
+- Improve the overall success rate of deploying Spot VMs by applying data-driven placement scores, reducing the risk of capacity issues or failures during deployment. 
 
 ## Cost
 
 There are no costs associated with this feature. 
 
 ## Considerations
 
-- Spot placement scores serve purely as a recommendation based on certain data points like eviction rate and VM availability. A high placement score does not guarantee that the Spot request will be fully or partially fulfilled. 
+- Spot placement scores serve purely as a recommendation based on certain data points like eviction rate and VM availability. A high placement score doesn't guarantee that the Spot request will be fully or partially fulfilled. 
 
-- Placement Scores are only valid at the time when it is requested. The same Placement Score is not valid at a different time of the same day or another day. Any similarities are purely coincidental.  
+- Placement Scores are only valid at the time when it's requested. The same Placement Score isn't valid at a different time of the same day or another day. Any similarities are purely coincidental.  
 
-- The Spot Placement Score is only relevant if the Spot request has the same configuration as the Spot Placement Score configuration; desired count, VM size, location, and zone. In all other circumstances, the likelihood of getting available Spot capacity will not align with the placement score generated by the tool. 
+- The Spot Placement Score is only relevant if the Spot request has the same configuration as the Spot Placement Score configuration; desired count, VM size, location, and zone. In all other circumstances, the likelihood of getting available Spot capacity won't align with the placement score generated by the tool. 
 
-- Spot Placement Scores don't consider additional constraints, such as Virtual Machine Scale Sets `SinglePlacementGroup`. 
+- Spot Placement Scores don't consider other constraints, such as Virtual Machine Scale Sets `SinglePlacementGroup`. 
 
-- A subscription's available Spot VM quota will need to be checked or requested separately. 
+- A subscription's available Spot VM quota needs to be checked or requested separately. 
 
 - Spot Placement Score supports both regionally and zonally scoped placement score. 
 
 - Spot Placement Score API internally calls other GET APIs and is part of your GET call quota. 
 
-- A score of **High** or **Medium** does not guarantee allocation success or no evictions. 
+- A score of **High** or **Medium** doesn't guarantee allocation success or no evictions. 
 
 
 ## Configure your Spot Placement Score
@@ -74,7 +74,7 @@ Find the Spot Placement Score in the Spot tab of the Virtual Machine Scale Sets
 
 ### [REST API](#tab/rest-api)
 
-Use the following REST API to get your Spot Placement Score. The Placement Score API supports the following versions: *2024-03-01-preview* and *2024-06-01-preview*. You will need to add the RBAC role "Compute Recommendations Role" and select the members to enable the subscription they want to run the API on (https://learn.microsoft.com/azure/role-based-access-control/role-assignments-portal).
+Use the following REST API to get your Spot Placement Score. The Placement Score API supports the following versions: *2024-03-01-preview* and *2024-06-01-preview*. You need to add the Role-Based Access Control (RBAC) role "Compute Recommendations Role" and select the members to enable the subscription they want to run the API on (https://learn.microsoft.com/azure/role-based-access-control/role-assignments-portal).
 
 ```
 POST https://management.azure.com/subscriptions/{subscription}/providers/Microsoft.Compute/locations/{region}/placementScores/spot/generate?api-version={api-version} 
@@ -91,7 +91,7 @@ POST https://management.azure.com/subscriptions/{subscription}/providers/Microso
 ```
 Some important terminology to consider:
 
-**Restricted SKU** is returned if the Spot VM SKU is not available for the subscription.
+**Restricted SKU** is returned if the Spot VM SKU isn't available for the subscription.
 
 **Data Not Found** is returned when the data necessary to generate a score or recommendation is either not found in upstream databases, or is found but the data lifespan is greater than what our service considers "fresh".
 
@@ -131,7 +131,7 @@ Invoke-AzSpotPlacementScore
 The following examples have scenario assumptions and a table with the results score to help you understand how Spot Placement Score works.
 
 ### Scenario 1
-This is an example of a request returning regionally scoped placement scores for multiple desired VM sizes and regions.
+This table is an example of a request returning regionally scoped placement scores for multiple desired VM sizes and regions.
 
 The following scenario assumptions apply to this example:
 - **Desired locations:** `westus`, `eastus`
@@ -147,7 +147,7 @@ The following scenario assumptions apply to this example:
 | Standard_D4_v2                    | eastus      | False                | True               | High             |
 
 ### Scenario 2
-This is an example of a request returning zonally scoped placement scores for multiple desired VM sizes and regions.
+This table is an example of a request returning zonally scoped placement scores for multiple desired VM sizes and regions.
 
 The following scenario assumptions apply to this example:
 - **Desired locations:** `westus`, `eastus`