Update README.md

kubernetes · Oct 25, 2018 · 00c3c2b · 00c3c2b
1 parent 00c9d96
commit 00c3c2b
Showing 1 changed file with 4 additions and 4 deletions.
diff --git a/staging/volumes/azure_disk/claim/README.md b/staging/volumes/azure_disk/claim/README.md
@@ -45,12 +45,12 @@ $ df -h
 ## How does it work? 
 
 ### Managed Disks
-The entire experience is offloaded to Azure to manage disks:storage accounts. You can use PVC (Kubernetes will automatically create a managed disk for you). Or you can you use an existing disk as PV in your PODs/RCs
+The entire experience is offloaded to Azure to manage disks:storage accounts. You can use PVC (Kubernetes will automatically create a managed disk for you). Or you can use an existing disk as PV in your PODs/RCs
 
 > Note: as a general rule, use PV disks provisioned in the same Azure resource group where the cluster is provisioned.   
 
 ### Blob Disks 
-Blob Disks works in two modes. Controlled by #kind# parameter on the storage class. 
+Blob Disks works in two modes. Controlled by *kind* parameter on the storage class. 
 
 ### Dedicated (default mode)
 When *kind* parameter is set to *dedicated* K8S will create a new dedicated storage account for this new disk. No other disks will be allowed in the this storage account. The account will be removed when the PVC is removed (according to K8S PVC reclaim policy) 
@@ -69,7 +69,7 @@ PVC: VHDs are created in a shared storage accounts in the same resource group as
 
 ```
 Resource Group
---Storage Account: pvc{unique-hash}001 // created by K8S as it provisoned  PVC, all disks are placed in the same blob container  
+--Storage Account: pvc{unique-hash}001 // created by K8S as it provisioned  PVC, all disks are placed in the same blob container  
 ---pvc-xxx-xxx-xxxx.vhd
 ---pvc-xxx-xxx-xxxx.vhd
 --Storage Account: pvc{unique-hash}002..n  
@@ -84,7 +84,7 @@ The following rules apply:
 4. K8S will create initial 2 accounts ( 1 standard and 1 premium ) to accelerate the provisioning process.
 
 ## Additional Notes
-The samples assumes that you have a cluster with node labeled with #disktype=blob# for VMs that are using blob disks and #disktype=managed# for VMs that are using managed disks. You can label your nodes or remove the node selector before using the files. 
+The samples assume that you have a cluster with node labeled with #disktype=blob# for VMs that are using blob disks and #disktype=managed# for VMs that are using managed disks. You can label your nodes or remove the node selector before using the files. 
 
 > Note: You can not attach managed disks to VMs that are not using managed OS disks. This applies also the other way around no blob disks on VMS that are using managed OS disks