Update hana-vm-operations.md

john-par · web-flow · commit 628de737af83 · 2019-08-08T16:33:47.000-07:00
diff --git a/articles/virtual-machines/workloads/sap/hana-vm-operations.md b/articles/virtual-machines/workloads/sap/hana-vm-operations.md
@@ -170,7 +170,7 @@ In the document [SAP HANA TDI Storage Requirements](https://www.sap.com/document
 Assuming you take the SAP HANA scale-out certified M128s Azure VM with roughly 2 TB memory, the SAP recommendations can be summarized like:
 
 - One master node and up to four worker node, the **/hana/shared** volume would need to be 2 TB of size. 
-- One master node and five and eight worker nodes, the size of **/hana/shared** should be 4 TB. 
+- One master node and five to eight worker nodes, the size of **/hana/shared** should be 4 TB. 
 - One master node and 9 to 12 worker nodes, a size of 6 TB for **/hana/shared** would be required. 
 - One master node and using between 12 and 15 worker nodes, you are required to provide a **/hana/shared** volume that is 8 TB in size.
 
@@ -213,7 +213,7 @@ If you want to share the highly available NFS cluster between SAP HANA configura
 ### Installing SAP HANA scale-out n Azure
 Installing a scale-out SAP configuration, you need to perform rough steps of:
 
-- Deploying new or adapting new Azure VNet infrastructure
+- Deploying new or adapting existing Azure VNet infrastructure
 - Deploying the new VMs using Azure Managed Premium Storage volumes
 - Deploying a new or adapt an existing highly available NFS cluster
 - Adapt network routing to make sure that, for example, intra-node communication between VMs is not routed through an [NVA](https://azure.microsoft.com/solutions/network-appliances/). Same is true for traffic between the VMs and the highly available NFS cluster.
