Addressing peer-review comments

Author: Srivaralakshmi

modules/sbo-categories-of-exposable-binding-data.adoc

@@ -24,9 +24,9 @@ metadata:
 
 
 == Exposing a constant value as the binding item
-The following examples show how to expose constant value from the `PostgresCluster` custom resource (CR):
+The following examples show how to expose a constant value from the `PostgresCluster` custom resource (CR):
 
-.Example: Exposing constant value
+.Example: Exposing a constant value
 [source,yaml]
 ----
 apiVersion: postgres-operator.crunchydata.com/v1beta1
@@ -37,7 +37,7 @@ metadata:
   annotations:
     "service.binding/type": "postgresql" <1>
 ----
-<1> Binding `type` that is to be exposed with the `postgresql` value.
+<1> Binding `type` to be exposed with the `postgresql` value.
 
 
 == Exposing an entire config map or secret that is referenced from a resource
@@ -160,7 +160,7 @@ If required values are available as attributes of backing service resources, ann
 
 
 == Exposing entries of a collection with the key and value from each entry
-Following is the example for exposing the entries of a collection with the key and value from each entry through annotations:
+The following example shows how to expose the entries of a collection with the key and value from each entry through annotations:
 
 .Example: Exposing the entries of a collection through annotations
 [source,yaml]
@@ -193,7 +193,7 @@ The following example shows how the previous entries of a collection in annotati
 /bindings/<binding-name>/uri_404 => black-hole.example.com
 ----
 
-Following is the example for exposing the entries of a collection with the key and value from each entry through OLM descriptors:
+The following example shows how to expose the entries of a collection with the key and value from each entry through OLM descriptors:
 
 .Example: Exposing the entries of a collection through OLM descriptors
 [source,yaml]
@@ -223,7 +223,7 @@ The previous example helps you to project all those values with keys such as `pr
 
 
 == Exposing items of a collection with one key per item
-Following is the example for exposing the items of a collection with one key per item through annotations:
+The following example shows how to expose the items of a collection with one key per item through annotations:
 
 .Example: Exposing the items of a collection through annotations
 [source,yaml]
@@ -251,7 +251,7 @@ The following example shows how the previous items of a collection in annotation
 /bindings/<binding-name>/tags_2 => power
 ----
 
-Following is the example for exposing the items of a collection with one key per item through OLM descriptors:
+The following example shows how to expose the items of a collection with one key per item through OLM descriptors:
 
 .Example: Exposing the items of a collection through OLM descriptors
 [source,yaml]
@@ -274,7 +274,7 @@ spec:
 
 
 == Exposing values of collection entries with one key per entry value
-Following is the example for exposing the values of collection entries with one key per entry value through annotations:
+The following example shows how to expose the values of collection entries with one key per entry value through annotations:
 
 .Example: Exposing the values of collection entries through annotations
 [source,yaml]
@@ -305,7 +305,7 @@ The following example shows how the previous values of a collection in annotatio
 /bindings/<binding-name>/url_2 => black-hole.example.com
 ----
 
-Following is the example for exposing the values of collection entries with one key per entry value through OLM descriptors:
+The following example shows how to expose the values of collection entries with one key per entry value through OLM descriptors:
 
 .Example: Exposing the values of collection entries through OLM descriptors
 [source,yaml]

modules/sbo-methods-of-exposing-binding-data.adoc

@@ -156,7 +156,7 @@ metadata:
     ...
 ----
 
-The previous example places the name of the secret name in the `{.metadata.name}-pguser-{.metadata.name}` template that resolves to `hippo-pguser-hippo` eventually. The template can contain multiple JSONPath.
+The previous example places the name of the secret name in the `{.metadata.name}-pguser-{.metadata.name}` template that resolves to `hippo-pguser-hippo`. The template can contain multiple JSONPath expressions.
 
 .Example: Referenced `Secret` object from a resource
 [source,yaml]
@@ -183,7 +183,7 @@ metadata:
     ...
 ----
 
-The previous example places the name of the config map in the `{.metadata.name}-config` template that resolves to `hippo-config` eventually. The template can contain multiple JSONPath.
+The previous example places the name of the config map in the `{.metadata.name}-config` template that resolves to `hippo-config`. The template can contain multiple JSONPath expressions.
 
 .Example: Referenced `ConfigMap` object from a resource
 [source,yaml]