Update co-location.md

Updated as per review comments

Author: ShivapriyaGujjarlapudi

articles/virtual-machines/co-location.md

@@ -44,9 +44,9 @@ Intent is an optional parameter to provide the intended [VM Sizes](../virtual-ma
 
 Additionally, an optional avaiability zone can be indicated through intent by providing the zone parameter, in case the proximity placement group must be created within a specific availability zone. Please note the following while providing zone parameter:
 
-- The availability zone parameter can only be provided while creation of the proximity placement group and cannot be modified after that
-- The availability zone can be specified only when intent is specified and not otherwise
-- Only one availability zone can be specified
+- The availability zone parameter can only be provided while creation of the proximity placement group and cannot be modified after that.
+- The availability zone can be specified only when intent is specified and not otherwise.
+- Only one availability zone can be specified.
 
 Proximity Placement Group creation or update will succeed only when at least one data center supports all the VM Sizes speicified in the intent. Otherwise, the creation or update would fail with "OverconstrainedAllocationRequest", indicating that the combination of VM Sizes cannot be supported within a proximity placement group. The **intent does not provide any capacity reservation or guarantee**; it only uses the provided intent VM Sizes and zone to select an appropriate data center, reducing the chances of failure arising from non-existence of the intended VM Sizes in a single data center. Therefore, **allocation failures** can still occur if there is no capacity for a VM Size at the time of deployment.