Minor edits.

Author: ankedia

documentation/site/content/managing-domains/persistent-storage/oci-fss-pv.md

@@ -16,17 +16,17 @@ when the domain is initially created."
 - [Provisioning PVCs on the File Storage Service (FSS)](https://docs.oracle.com/en-us/iaas/Content/ContEng/Tasks/contengcreatingpersistentvolumeclaim_Provisioning_PVCs_on_FSS.htm#Provisioning_Persistent_Volume_Claims_on_the_FileStorageService) in the OCI documentation.
 - [Setting up storage for kubernetes clusters](https://docs.oracle.com/en-us/iaas/Content/ContEng/Tasks/contengcreatingpersistentvolumeclaim.htm) in the OCI documentation.
 
-If you are running your Kubernetes cluster on Oracle Container Engine
-for Kubernetes (commonly known as OKE), and you use Oracle Cloud Infrastructure File Storage (FSS)
-for persistent volumes to store the WebLogic domain home or log files, then the file system
+Oracle recommends using Oracle Cloud Infrastructure File Storage (FSS) for persistent volumes to store
+the WebLogic domain home or log files when running the Kubernetes cluster on Oracle Container Engine
+for Kubernetes (OKE). When using the FSS with OKE for domain home or log files,  the file system
 handling will require an update to properly initialize the file ownership on the persistent volume 
 when the domain is initially created.  
 
 {{% notice note %}}
 File permission handling on persistent volumes can differ between
 cloud providers and even with the underlying storage handling on
-Linux based systems. 
-The operator requires permissions to create directories on the persistent volume under the shared mount path.
+Linux-based systems. 
+The operator requires permission to create directories on the persistent volume under the shared mount path.
 The following instructions provide an option to update the file ownership and permissions.
 {{% /notice %}}
 
@@ -38,13 +38,13 @@ This script launches a Pod and mounts the specified PVC in the Pod containers at
 
 See the `pv-pvc-helper.sh` in `Examine, change permissions or delete PV contents` section in the [README](https://github.com/oracle/weblogic-kubernetes-operator/tree/{{< latestMinorVersion >}}/kubernetes/samples/scripts/domain-lifecycle/README.md) file for the script details.
 
-For example, run the following command to create the pod.
+For example, run the following command to create the Pod.
 
 ```
 $ pv-pvc-helper.sh -n sample-domain1-ns -r -c sample-domain1-weblogic-sample-pvc -m /shared
 ```
 
-This will create a pod with following specifications.
+The script will create a Pod with the following specifications.
 ```
 apiVersion: v1
 kind: Pod
@@ -72,7 +72,7 @@ Run the following command to exec into the Pod.
 $ kubectl -n sample-domain1-ns exec -it pvhelper -- /bin/sh
 ```
 
-After you get a shell to the running pod container, change the directory to `/shared` and you can change the ownership or permissions using appropriate `chown` or `chmod` commands. For example,
+After you get a shell to the running Pod container, change the directory to `/shared`, and you can change the ownership or permissions using appropriate `chown` or `chmod` commands. For example,
 
 ```
 chown 1000:0 /shared/. && find /shared/. -maxdepth 1 ! -name '.snapshot' ! -name '.' -print0 | xargs -r -0 chown -R 1000:0

documentation/site/content/managing-domains/persistent-storage/pv-pvc.md

@@ -20,7 +20,7 @@ PersistentVolumes can point to different storage locations, for example NFS serv
 
 **Note regarding HostPath**: In a single-node Kubernetes cluster, such as may be used for testing or proof of concept activities, `HOST_PATH` provides the simplest configuration.  In a multinode Kubernetes cluster, a `HOST_PATH` that is located on shared storage mounted by all nodes in the Kubernetes cluster is the simplest configuration.  If nodes do not have shared storage, then NFS is probably the most widely available option.  There are other options listed in the referenced table.
 
-The operator provides a sample script to create the PersistentVolume and PersistentVolumeClaim for the domain. this script must be executed before creating the domain.  Beginning with Operator 4.1.0, for Domain on PV [domain home source type]({{< relref "/managing-domains/choosing-a-model/_index.md" >}}), the operator provides options to create the PV and PVC during the domain initialization. See [Domain on PV documentation]({{< relref "/managing-domains/domain-on-pv/_index.md" >}}) or the `domain.spec.configuration.initializeDomainOnPV` section in the domain resource [schema](https://github.com/oracle/weblogic-kubernetes-operator/blob/{{< latestMinorVersion >}}/documentation/domains/Domain.md) for more details.
+The operator provides a sample script to create the PersistentVolume and PersistentVolumeClaim for the domain. This script must be executed before creating the domain.  Beginning with operator version 4.1.0, for the Domain on PV [domain home source type]({{< relref "/managing-domains/choosing-a-model/_index.md" >}}), the operator provides options to create the PV and PVC during the domain initialization. See [Domain on PV documentation]({{< relref "/managing-domains/domain-on-pv/_index.md" >}}) or the `domain.spec.configuration.initializeDomainOnPV` section in the domain resource [schema](https://github.com/oracle/weblogic-kubernetes-operator/blob/{{< latestMinorVersion >}}/documentation/domains/Domain.md) for more details.
 
 #### Persistent Volumes using HostPath approach
 The `HOST_PATH` provider is the simplest case for creating a Persistent Volume. It requires creating a directory on the Kubernetes master and ensuring that it has the correct permissions:
@@ -35,7 +35,7 @@ Persistent volumes and claims are described in YAML files. For each PersistentVo
 
 For sample YAML templates, refer to the [PersistentVolumes example]({{< relref "/samples/storage/_index.md" >}}).
 
-For more details, refer to [Kubernetes examples](https://github.com/kubernetes/examples/), and the PV/PVC examples [here](https://github.com/kubernetes/examples/tree/master/staging/volumes).
+For more details, refer to Kubernetes PV/PVC examples [here](https://github.com/kubernetes/examples/tree/master/staging/volumes).
 
 #### Verify the results
 

kubernetes/samples/scripts/domain-lifecycle/README.md

@@ -283,10 +283,10 @@ $ waitForDomain.sh -n my-namespace -d my-domain -p 0
 
 #### `pv-pvc-helper.sh` 
 
-Use this helper script for examining, changing permissions or deleting the contents of persistent volume (such as domain files or logs) for a WebLogic Domain on PV or Model in Image domain.
-The script launches a a Kubernetes pod named as 'pvhelper' using the provided persistent volume claim name and the mount path.
-You can run the 'kubectl exec' to get a shell to the running pod container and run commands to examine or clean up the contents of shared directories on persistent volume.
-Use 'kubectl delete pvhelper -n <namespace>' command to delete the pod after it's no longer needed.
+Use this helper script for examining, changing permissions, or deleting the contents of the persistent volume (such as domain files or logs) for a WebLogic Domain on PV or Model in Image domain.
+The script launches a Kubernetes pod named 'pvhelper' using the provided persistent volume claim name and the mount path.
+You can run the 'kubectl exec' to get a shell to the running pod container and run commands to examine or clean up the contents of shared directories on the persistent volume.
+Use 'kubectl delete pvhelper -n <namespace>' command to delete the Pod after it's no longer needed.
 
 Use the following command for script usage:
 
@@ -300,17 +300,17 @@ Following is an example command to launch the helper pod with PVC name `sample-d
 $ domain-on-pv-helper.sh -n sample-domain1-ns -c sample-domain1-weblogic-sample-pvc -m /shared
 ```
 
-After the pod is created, use following command to get a shell to the running pod container.
+After the Pod is created, use the following command to get a shell to the running pod container.
 
 ```
 $ kubectl -n sample-domain1-ns exec -it pvhelper -- /bin/sh
 ```
 
 After you get a shell to the running pod container, you can recursively delete the contents of the domain home and applications 
 directories using rm -rf /shared/domains/sample-domain1 and rm -rf /shared/applications/sample-domain1 commands. Since these 
-commands will actually delete files on the persistent storage, we recommend that you understand and execute these commands carefully.
+commands will delete files on the persistent storage, we recommend you understand and execute these commands carefully.
 
-Use the following command to delete the pod after it's no longer needed.
+Use the following command to delete the Pod after it's no longer needed.
 
 ```
 $ kubectl delete pod pvhelper -n <namespace>
@@ -320,8 +320,8 @@ $ kubectl delete pod pvhelper -n <namespace>
 
 #### `opss-wallet.sh` 
 
-The OPSS wallet utility is a helper script for JRF type domains that can save an OPSS key
-wallet from a running domain's introspector configmap to a file, and/or
+The OPSS wallet utility is a helper script for the JRF-type domains that can save an OPSS key
+wallet from a running domain's introspector configmap to a file and
 restore an OPSS key wallet file to a Kubernetes secret for use by a
 domain that you're about to run.
 

kubernetes/samples/scripts/domain-lifecycle/pv-pvc-helper.sh

@@ -25,7 +25,7 @@ initGlobals() {
 usage() {
   cat << EOF
 
-  This is a helper script for examining, changing permissions, or deleting the contents of persistent 
+  This is a helper script for examining, changing permissions, or deleting the contents of the persistent
   volume (such as domain files or logs) for a WebLogic Domain on PV or Model in Image domain.
   The script launches a a Kubernetes pod named as 'pvhelper' using the provided persistent volume claim name and the mount path. 
   You can run the '${KUBERNETES_CLI} exec' to get a shell to the running pod container and run commands to examine or clean up the contents of