fix(docs): managed-nfs-storage -> nfs-client

Changed at https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner/commit/65b3ac93b6e8f621fc6b42dd1d2cb1d7a6be2b9e But it missed the one in README.md

fix(docs): managed-nfs-storage -> nfs-client
92fd6aac · NeverBehave · GitHub · 0bd4e87b · 92fd6aac
Unverified Commit 92fd6aac authored Jun 24, 2022 by NeverBehave Committed by GitHub Jun 24, 2022
Show whitespace changes
Inline Side-by-side

Showing with 2 additions and 2 deletions

README.md README.md +2 -2

No files found.
--- a/README.md
+++ b/README.md
@@ -125,7 +125,7 @@ Now check the PVC's directory has been deleted.
 **Step 7: Deploying your own PersistentVolumeClaims**
-To deploy your own PVC, make sure that you have the correct `storageClassName` (by default `managed-nfs-storage`). You can also patch the StorageClass resource to change it, like so:
+To deploy your own PVC, make sure that you have the correct `storageClassName` (by default `nfs-client`). You can also patch the StorageClass resource to change it, like so:
 ```yaml
 # kustomization.yaml
@@ -136,7 +136,7 @@ resources:
 patches:
 - target:
    kind: StorageClass
-    name: managed-nfs-storage
+    name: nfs-client
  patch: |-
    - op: replace
      path: /metadata/name