Update README.md

helm/examples/efs/README.md

@@ -100,23 +100,23 @@ To start the HPCC cluster, run
   helm install myhpcc ./hpcc --set global.image.version=latest -f examples/efs/values-retained-efs.yaml
 ```
 An example values file to be supplied when installing the HPCC chart.
-NB: Either use the output auto-generated when installing the "hpcc-efs" helm chart, or ensure the names in your values files for the storage types match the PVC names created. "values-retained-efs.yaml" expects that helm chart installation name is "awsstorage". Change the PVC name accordingly if another name is used.<br/>
+NB: Either use the output auto-generated when installing the "hpcc-efs" helm chart, or ensure the names in your values files for the storage types match the PVC names created. The "values-retained-efs.yaml" file expects that helm chart installation name is "awsstorage". Change the PVC name accordingly if another name is used.<br/>
 To cleanup, run
 ```console
   helm uninstall myhpcc
   helm uninstall awsstorage
 ```
 ## 3. Static storage beyond Kubernetes with values-retained-efs.yaml
 In this method, the storage lives beyond the Kubernetes cluster. It uses the helm chart "hpcc-efs-static-pv" to manually create PVs and PVCs and to configure access points in EFS with the Kubernetes cluster. This means that even if the Kubernetes cluster is deleted, the storage will remain and can be reused across different Kubernetes clusters.<br/>
-The create-ap.sh script creates five access points in EFS for each of dali, dll, sasha, data, and mydropzone, and it displays a description for each access point. You may need to add additional tags to the access points depending on your organization. For example, for RISK users, the "owner" and "owner_email" tags are required; add these to the script as needed.<br/>
+The create-ap.sh script creates five access points in EFS for each of dali, dll, sasha, data, and mydropzone. It also displays a description for each access point. You may need to add additional tags to the access points depending on your organization. For example, for RISK users, the "owner" and "owner_email" tags are required; add these to the script as needed.<br/>
 Once you are ready, under the efs directory run the following command:
 ```code
 ./create-ap.sh
 ```
 Note that running the script again will create five more access points with the same exact specifications. Use the delete-ap.sh to delete all access points.<br/>
 Navigate to hpcc-efs-static-pv -> values.yaml. Paste the EFS ID where it says "efsID" and the access point IDs where it says "apID". You can get the access point IDs either through the console or from the descriptions after running the create-ap.sh script. Make sure the correct access point IDs correspond to the correct names in the values.yaml.<br/>
 
-Again, the storage needs to be created before starting the HPCC cluster. Under the helm directory, run the following command:
+The storage needs to be created before starting the HPCC cluster. Under the helm directory, run the following command:
 ```console
   helm install awsstorage examples/efs/hpcc-efs-static-pv
 ```
@@ -201,4 +201,4 @@ To display the mount targets:
 Navigate to the EFS service and click "Create file system". Select the same VPC as the one your EKS cluster is running in.
 ### Configuring the Mount Targets
 Click on the file system you just created and navigate to "Network". Your mount targets should be displayed.<br/>
-Click on "Manage", and you should see that the security groups for the mount targets are the default security group. Replace these with the EKS cluster security group. To find the EKS cluster security group, navigate to EKS, click on your cluster, click on "Networking", and it is the security group displayed under "Cluster security group". After replacing the default security group for all mount targets, save your changes.
+Click on "Manage", and you should see that the security groups for the mount targets are the default security group. Replace these with the EKS cluster security group. To find the EKS cluster security group navigate to EKS. Click on your cluster. Click on "Networking", and find the security group displayed under "Cluster security group". After replacing the default security group for all mount targets, save your changes.