pages/*.adoc: s/persistence/persistent (#56)

Correct persistence ^(storage volume volume claim) to persistent.

Author: joshix

documentation/modules/ROOT/pages/statefulset.adoc

@@ -3,7 +3,7 @@ include::_attributes.adoc[]
 :watch-terminal: Terminal 2
 
 A `StatefulSet` provides a unique identity to the Pods that they manage.
-`StatefulSet` s are particularly useful when your application requires a unique network identifier or persistence storage across Pod (re)scheduling or when your application needs some guarantee about the ordering of deployment and scaling.
+`StatefulSet` s are particularly useful when your application requires a unique network identifier or persistent storage across Pod (re)scheduling or when your application needs some guarantee about the ordering of deployment and scaling.
 
 One of the most typical examples of using `StatefulSet` s is when one needs to deploy primary/secondary servers (i.e database cluster) where you need to know beforehand the hostname of each of the servers to start the cluster.
 Also, when you scale up and down you want to do it in a specified order (i.e you want to start the primary node first and then the secondary node).

documentation/modules/ROOT/pages/volumes-persistentvolumes.adoc

@@ -525,7 +525,7 @@ It can request for a specific volume size or, for example, the access mode.
 
 :quick-open-file: demo-persistent-volume-hostpath.yaml
 
-Let's use `hostPath` strategy, but not configuring it directly as volume, but using persistence volume and persistence volume claim. Check out `{quick-open-file}`:
+Let's use `hostPath` strategy, but not configuring it directly as volume, but using persistent volume and persistent volume claim. Check out `{quick-open-file}`:
 
 include::partial$tip_vscode_quick_open.adoc[]
 
@@ -668,7 +668,7 @@ Volumes:
     ReadOnly:   false
 ----
 
-Notice that now the description of the pod shows that the volume is not set directly but through a persistence volume claim.
+Notice that now the description of the pod shows that the volume is not set directly but through a persistent volume claim.
 
 include::partial$create-greeting-file.adoc[]