Document changes to annotation examples

Author: Srivaralakshmi

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

@@ -23,6 +23,23 @@ metadata:
 ----
 
 
+== Exposing a constant value as the binding item
+The following examples show how to expose constant value as annotations:
+
+.Example: Exposing constant value as annotations
+[source,yaml]
+----
+apiVersion: postgres-operator.crunchydata.com/v1beta1
+kind: PostgresCluster
+metadata:
+  name: hippo
+  namespace: my-postgresql
+  annotations:
+    "service.binding/type": "postgresql" <1>
+----
+<1> Binding `type` that is to be exposed with the `postgresql` value.
+
+
 == Exposing an entire config map or secret that is referenced from a resource
 The following examples show how to expose an entire secret as annotations:
 
@@ -107,7 +124,7 @@ The following example shows how to expose a specific entry from a config map as
 
 This example uses the `path` attribute with an `X-Descriptors` update for `service.binding` and `sourceKey` by providing the following information:
 
-* Name of the binding key that is to be injected
+* Name of the binding key that is to be projected
 * Name of the key in the Secret service resource
 
 
@@ -129,7 +146,7 @@ metadata:
 
 The following example shows how to expose a resource definition value as OLM descriptors:
 
-.Example: Exposing  a resource definition value as OLM descriptors
+.Example: Exposing a resource definition value as OLM descriptors
 [source,yaml]
 ----
 - path: data.connectionURL

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

@@ -143,7 +143,7 @@ You can use this method to annotate the resources of the backing service to expo
 
 The following examples show the annotations that are added under the `metadata` section and a referenced `ConfigMap` object from a resource:
 
-.Example: Exposing binding data from a `Secret` object in the `metadata.annotations.dbsecret` custom field
+.Example: Exposing binding data from a `Secret` object defined in the CR annotations
 [source,yaml]
 ----
 apiVersion: postgres-operator.crunchydata.com/v1beta1
@@ -156,7 +156,21 @@ metadata:
     ...
 ----
 
-.Example: Exposing binding data from a `ConfigMap` object in the `metadata.annotations.dbconfig` custom field
+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.
+
+.Example: Referenced `Secret` object from a resource
+[source,yaml]
+----
+apiVersion: v1
+kind: Secret
+metadata:
+  name: hippo-pguser-hippo
+data:
+  password: "MTBz"
+  user: "Z3Vlc3Q="
+----
+
+.Example: Exposing binding data from a `ConfigMap` object defined in the CR annotations
 [source,yaml]
 ----
 apiVersion: postgres-operator.crunchydata.com/v1beta1
@@ -169,7 +183,7 @@ metadata:
     ...
 ----
 
-The previous example places the name of the config map in the `metadata.annotations.dbconfig` custom field and specifies to expose a single key from the config map.
+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.
 
 .Example: Referenced `ConfigMap` object from a resource
 [source,yaml]