doc: refine inline volume example

deploy/example/e2e_usage.md

@@ -101,10 +101,8 @@ Filesystem                                                                Size
 In the above example, there is a `/mnt/azurefile` directory mounted as cifs filesystem.
 
 #### Option#3: Inline volume
- > only available from `v1.3.0` for SMB protocol (NFS protocol is not supported) <br>
- > inline volume feature can only read storage account name and key in the same namespace, cannot use cluster identity to read storage account name and key <br>
- - Create `azure-secret` with existing storage account name and key in the same namespace as pod
- > in below example, both secret and pod are in `default` namespace
+ > to avoid performance issue, use persistent volume instead of inline volume when numerous pods are accessing the same volume.
+ - in below SMB protocol example, create `azure-secret` with existing storage account name and key in the same namespace as pod, both secret and pod are in `default` namespace
 ```console
 kubectl create secret generic azure-secret --from-literal azurestorageaccountname=NAME --from-literal azurestorageaccountkey="KEY" --type=Opaque
 ```