Merge pull request #5300 from ahardin-rh/5260-followup

Follow-up edits to PR#5260

Author: ahardin-rh

architecture/additional_concepts/authorization.adoc

@@ -569,14 +569,15 @@ value will be removed from `volumes`.
 ====
 
 [[authorization-allowed-flex-volumes]]
-=== Restricting an Access to Flexvolumes
+=== Restricting Access to FlexVolumes
 
-{product-title} provides additional control of Flexvolumes based on their
-driver. When SCC allows the usage of Flexvolumes, pods may request any Flexvolumes.
-But when cluster admin specifies driver names in the `AllowedFlexVolumes`
-field, pods may use only Flexvolumes with these drivers.
+{product-title} provides additional control of FlexVolumes based on their
+driver. When SCC allows the usage of FlexVolumes, pods can request any
+FlexVolumes. However, when the cluster administrator specifies driver names in
+the `AllowedFlexVolumes` field, pods must only use FlexVolumes with these
+drivers.
 
-.Example of limiting access to only two Flexvolumes
+.Example of Limiting Access to Only Two FlexVolumes
 [source,yaml]
 ----
 volumes:
@@ -749,5 +750,5 @@ ifdef::openshift-online[]
 In {product-title} Pro, you can grant roles (like *view* or *edit*) to other
 users or groups for your projects.
 
-In {product-title} Starter, collaboration is not available. 
+In {product-title} Starter, collaboration is not available.
 endif::[]