Merge pull request #14171 from bergerhoffer/wording-fixes

Minor tweaks for service broker content

Author: bergerhoffer

modules/sb-about-ansible-service-broker.adoc

@@ -8,15 +8,15 @@
 The _{asb-name}_ is an implementation of the Open Service Broker (OSB) API that
 manages applications defined by _Ansible playbook bundles_ (APBs). APBs provide
 a method for defining and distributing container applications in
-{product-title}, consisting of a bundle of Ansible playbooks built into a
+{product-title}, and consist of a bundle of Ansible playbooks built into a
 container image with an Ansible runtime. APBs leverage Ansible to create a
-standard mechanism for automating complex deployments.
+standard mechanism to automate complex deployments.
 
 The {asb-name} follows this basic workflow:
 
 . A user requests the list of available applications from the service catalog
 using the {product-title} web console.
-. The service catalog requests the {asb-name} for available applications.
+. The service catalog requests the list of available applications from the {asb-name}.
 . The {asb-name} communicates with a defined container image registry to learn
 which APBs are available.
 . The user issues a request to provision a specific APB.

modules/sb-about-template-service-broker.adoc

@@ -9,10 +9,9 @@ The _template service broker_ gives the service catalog visibility into the
 default Instant App and Quickstart templates that have shipped with
 {product-title} since its initial release. The template service broker can also
 make available as a service anything for which an {product-title} template has
-been written, whether provided by Red Hat, a cluster administrator or user, or a
-third party vendor.
+been written, whether provided by Red Hat, a cluster administrator or user, or a third-party vendor.
 
-By default, the template service broker shows the objects that are globally
+By default, the template service broker shows objects that are globally
 available from the `openshift` project. It can also be configured to watch any
 other project that a cluster administrator chooses.
 

modules/sb-configuring-ansible-service-broker.adoc

@@ -13,7 +13,7 @@ The following procedure customizes the settings for your {asb-name}.
 
 .Procedure
 
-This procedure assumes that you used the `ansible-service-broker` project and name for the {asb-name}.
+This procedure assumes that you used `ansible-service-broker` both as the {asb-name} name and the project that it was installed into.
 
 . Navigate in the web console to *Catalog* -> *Installed Operators* and select the `ansible-service-broker` project.
 . Select the *OpenShift Ansible Service Broker Operator*.
@@ -22,6 +22,7 @@ This procedure assumes that you used the `ansible-service-broker` project and na
 +
 For example:
 +
+[source,yaml]
 ----
 spec:
   keepNamespace: true

modules/sb-install-asb-operator.adoc

@@ -7,7 +7,7 @@
 
 .Prerequisites
 
-* You have enabled service catalog.
+* You have installed the service catalog.
 
 .Procedure
 
@@ -38,5 +38,5 @@ This Operator will be available under the *Red Hat* category in the GA release.
 . Read the information about the Operator and click *Install*.
 . Review the default selections and click *Subscribe*.
 
-You must next start the {asb-name} in order to access the service
+Next, you must start the {asb-name} in order to access the service
 bundles it provides.

modules/sb-install-service-catalog.adoc

@@ -3,9 +3,9 @@
 // * applications/service_brokers/installing-service-catalog.adoc
 
 [id='sb-install-service-catalog-{context}']
-= Installing service catalog
+= Installing the service catalog
 
-You must install service catalog by completing the following steps if you plan on using any of the services from the {asb-name} or template service broker.
+You must install the service catalog by completing the following steps if you plan on using any of the services from the {asb-name} or template service broker.
 
 .Procedure
 
@@ -17,6 +17,7 @@ $ oc edit servicecatalogapiservers
 ----
 .. Under `spec`, set the `managementState` field to `Managed`:
 +
+[source,yaml]
 ----
 spec:
   logLevel: Normal
@@ -36,6 +37,7 @@ $ oc edit servicecatalogcontrollermanagers
 ----
 .. Under `spec`, set the `managementState` field to `Managed`:
 +
+[source,yaml]
 ----
 spec:
   logLevel: Normal

modules/sb-install-tsb-operator.adoc

@@ -7,7 +7,7 @@
 
 .Prerequisites
 
-* You have enabled service catalog.
+* You have installed the service catalog.
 
 .Procedure
 
@@ -30,5 +30,5 @@ This Operator will be available under the *Red Hat* category in the GA release.
 . Read the information about the Operator and click *Install*.
 . Review the default selections and click *Subscribe*.
 
-You must next start the template service broker in order to access the template
+Next, you must start the template service broker in order to access the template
 applications it provides.

modules/sb-provision-service-bundle.adoc

@@ -10,7 +10,7 @@ that was made available by the {asb-name}.
 
 .Prerequisites
 
-* You have enabled the service catalog.
+* You have installed the service catalog.
 * You have installed and started the {asb-name}.
 
 .Procedure

modules/sb-provision-template-application.adoc

@@ -10,7 +10,7 @@ that was made available by the template service broker.
 
 .Prerequisites
 
-* You have enabled the service catalog.
+* You have installed the service catalog.
 * You have installed and started the template service broker.
 
 .Procedure

modules/sb-start-asb.adoc

@@ -10,7 +10,7 @@ using the following procedure.
 
 .Prerequisites
 
-* You have enabled service catalog.
+* You have installed the service catalog.
 * You have installed the {asb-name} Operator.
 
 .Procedure

modules/sb-start-tsb.adoc

@@ -10,7 +10,7 @@ template service broker using the following procedure.
 
 .Prerequisites
 
-* You have enabled service catalog.
+* You have installed the service catalog.
 * You have installed the template service broker Operator.
 
 .Procedure