Merge pull request #110666 from openshift-cherrypick-robot/cherry-pick-109238-to-enterprise-4.22

[enterprise-4.22] OSDOCS-18675-abstracts: PC review for REG-3 Registry Core Access, Sec…

Author: dfitzmau

modules/pruning-images.adoc

@@ -7,7 +7,7 @@
 = Automatically pruning images
 
 [role="_abstract"]
-Images from the {product-registry} that are no longer required by the system because of age, status, or exceed limits being automatically pruned. As a cluster administrator, can configure or suspend the pruning Custom Resource (CR).
+To reclaim storage in the {product-registry} in {product-title} and set how long the cluster keeps images, you can configure the automatic image pruner. You set the schedule, suspension, and retention options on the pruning custom resource (CR).
 
 .Prerequisites
 

modules/registry-operator-distribution-across-availability-zones.adoc

@@ -7,7 +7,7 @@
 = Image Registry Operator distribution across availability zones
 
 [role="_abstract"]
-The default configuration of the Image Registry Operator spreads image registry pods across topology zones to prevent delayed recovery times in case of a complete zone failure where all pods are impacted. Reference the following YAML to understand the default parameter values that the Image Registry Operator uses when the Operator deploys with a zone-related topology constraint:
+The default configuration of the Image Registry Operator spreads image registry pods across topology zones to prevent delayed recovery times in case of a complete zone failure where all pods are impacted. Reference the example YAML to understand the default parameter values that the Image Registry Operator uses when the Operator deploys with a zone-related topology constraint:
 
 [source,yaml]
 ----