fix

Author: umagnus

deploy/example/mountstorage/README.md

@@ -162,9 +162,9 @@ You can use a dedicated user-assigned managed identity to mount the storage.
 
 # dynamic provisioning in an existing resource group
 
-1. Grant cluster system assigned identity `Contributor` to resource group, if mount in an existing storage account, then should also grant identity to storage account
+1. Grant cluster system assigned identity and kubelet identity `Contributor` role to resource group, if mount in an existing storage account, then should also grant identity to storage account
 
-1. Grant kubelet identity `Storage Blob Data Owner` to resource group to mount blob storage, if mount in an existing storage account, then should also grant identity to storage account
+1. Grant kubelet identity `Storage Blob Data Owner` role to resource group to mount blob storage, if mount in an existing storage account, then should also grant identity to storage account
 
 1. Create a storage class and give an existing resource group, CSI will create a new storage account when `storageAccount` is not provided.
     ```yml
@@ -180,7 +180,7 @@ You can use a dedicated user-assigned managed identity to mount the storage.
       storageAccount: EXISTING_STORAGE_ACCOUNT_NAME # optional, if use existing storage account
       containerName: EXISTING_CONTAINER_NAME # optional, if use existing container
       AzureStorageAuthType: MSI
-      AzureStorageIdentityClientID: "92926dfd-e61b-4730-85ab-5be73b374e82"
+      AzureStorageIdentityClientID: "xxxxx-xxxx-xxx-xxx-xxxxxxx"
     reclaimPolicy: Delete
     volumeBindingMode: Immediate
     allowVolumeExpansion: true