cropping image 4

Author: kquinn1204

content/patterns/retail/application.adoc

@@ -1,5 +1,5 @@
 ---
-title: Demonstrating retail example applications
+title: Demonstrating a retail example applications
 weight: 40
 aliases: /retail/application-demos/
 ---

content/patterns/retail/components.adoc

@@ -13,8 +13,7 @@ include::modules/comm-attributes.adoc[]
 === The Quarkus Coffeeshop Store https://github.com/validatedpatterns/retail/tree/main/charts/store/quarkuscoffeeshop-charts[Chart]
 
 This chart is responsible for deploying the applications, services and routes for the Quarkus Coffeeshop demo. It models a set of microservices
-that would make sense for a coffeeshop retail operation. The detail of what the microservices do is
-https://quarkuscoffeeshop.github.io/coffeeshop/[here].
+that would make sense for a coffeeshop retail operation. The detail of what the microservices do is https://quarkuscoffeeshop.github.io/coffeeshop/[here].
 
 * https://github.com/quarkuscoffeeshop/quarkuscoffeeshop-web[quarkuscoffeeshop-web] - Serves as the `front end` for ordering food and drinks.
 
@@ -34,19 +33,19 @@ https://quarkuscoffeeshop.github.io/coffeeshop/[here].
 
 All the components look like this in ArgoCD when deployed:
 
-link:/images/retail/retail-v1-argo-coffeeshop-store.png[image:/images/retail/retail-v1-argo-coffeeshop-store.png[retail-v1-argo-coffeeshop-store]
+image:/images/retail/retail-v1-argo-coffeeshop-store.png[retail-v1-argo-coffeeshop-store]
 
 The chart is designed such that the same chart can be deployed in the hub cluster as the `production` store, the `demo` or `TEST` store, and on a remote cluster.
 
 === The Quarkus Coffeeshop Database https://github.com/validatedpatterns/retail/tree/main/charts/all/crunchy-pgcluster[Chart]
 
 This installs a database instance suitable for use in the Retail pattern. It uses the Crunchy PostgreSQL https://github.com/CrunchyData/postgres-operator[Operator] to provide PostgreSQL services, which includes high availability and backup services by default, and other features available.
 
-Like the store chart, the Database chart can be deployed in the same different scenarios.
+Similar to the store chart, the Database chart can be deployed in the same variety of scenarios.
 
 In ArgoCD, it looks like this:
 
-link:/images/retail/retail-v1-argo-coffeeshopdb.png[image:/images/retail/retail-v1-argo-coffeeshopdb.png[retail-v1-argo-coffeeshopdb]
+image:/images/retail/retail-v1-argo-coffeeshopdb.png[retail-v1-argo-coffeeshopdb]
 
 === The Quarkus Coffeeshop Kafka https://github.com/validatedpatterns/retail/tree/main/charts/all/quarkuscoffeeshop-kafka[Chart]
 
@@ -55,16 +54,14 @@ https://access.redhat.com/documentation/en-us/red_hat_amq/7.2/html/using_amq_str
 
 === The Quarkus Coffeeshop Pipelines https://github.com/validatedpatterns/retail/tree/main/charts/hub/quarkuscoffeeshop-pipelines[Chart]
 
-The pipelines chart defines build pipelines using the Red Hat OpenShift
-Pipelines https://catalog.redhat.com/software/operators/detail/5ec54a4628834587a6b85ca5[Operator] (tektoncd). Pipelines are provided for all of the application images that ship with the pattern; the pipelines all build the app from source, deploy them to the "`demo`" namespace, and push them to the configured
-image registry.
+The pipelines chart defines build pipelines using the Red Hat OpenShift Pipelines https://catalog.redhat.com/software/operators/detail/5ec54a4628834587a6b85ca5[Operator] (tektoncd). Pipelines are provided for all of the application images that ship with the pattern; the pipelines all build the app from source, deploy them to the `demo` namespace, and push them to the configured image registry.
 
 Like the store and database charts, the kafka chart supports all three modes of deployment.
 
-link:/images/retail/retail-v1-argo-pipelines.png[image:/images/retail/retail-v1-argo-pipelines.png[retail-v1-argo-pipelines]
+image:/images/retail/retail-v1-argo-pipelines.png[retail-v1-argo-pipelines]
 
 === The Quarkus Coffeeshop Landing Page https://github.com/validatedpatterns/retail/tree/main/charts/all/landing-page[Chart]
 
 The Landing Page chart builds the page that presents the links for the demos in the pattern.
 
-link:/images/retail/retail-v1-argo-landing-page.png[image:/images/retail/retail-v1-argo-landing-page.png[retail-v1-landing-page]
+image:/images/retail/retail-v1-argo-landing-page.png[retail-v1-landing-page]

content/patterns/retail/store.adoc

@@ -1,5 +1,5 @@
 ---
-title: Managed cluster sites
+title: Managed store sites
 weight: 30
 aliases: /retail/retail-managed-cluster/
 ---
@@ -17,7 +17,7 @@ A store ("`ATLANTA`") is installed on the hub cluster by default. This feature i
 cluster to install the same application on a different cluster.
 
 The way we apply this is through the `managedClusterGroups` block in `values-hub.yaml`:
-+
+
 [source,yaml]
 ----
   managedClusterGroups:

modules/retail-example-applications.adoc

@@ -4,63 +4,47 @@
 [id="deploying-mcg-pattern"]
 = Demonstrating Retail example applications
 
-Up until now the Retail validated pattern has focused primarily on
-successfully deploying the architectural pattern. Now it is time to see
+Up until now the retail validated pattern has focused primarily on successfully deploying the architectural pattern. Now it is time to see
 the actual applications running as we have deployed them.
 
-If you have already deployed the hub cluster, then you have already seen
-several applications deployed in the OpenShift GitOps console. If you
-haven’t done this then we recommend you deploy the hub after you have
-setup the Quay repositories described below.
+If you have already deployed the hub cluster, then you have already seen several applications deployed in the OpenShift GitOps console. If you
+have not done this then we recommend you deploy the hub after you have setup the Quay repositories described below.
 
 == Ordering Items at the Coffeeshop
 
-The easiest way to get to the coffeeshop store page is from the
-OpenShift Console Menu Landing Page entry:
+The easiest way to get to the coffeeshop store page is from the OpenShift Console Menu Landing Page entry:
 
-link:/images/retail/retail-v1-console-menu.png[image:/images/retail/retail-v1-console-menu.png[retail-v1-console-menu]
+image:/images/retail/retail-v1-console-menu.png[retail-v1-console-menu]
 
-1. Click the *Quarkus Coffeeshop Landing Page* link will bring you to
-this page:
+1. Click the *Quarkus Coffeeshop Landing Page* link will bring you to this page:
 +
-link:/images/retail/retail-v1-landing-page.png[image:/images/retail/retail-v1-landing-page.png[retail-v1-landing-page]
+image:/images/retail/retail-v1-landing-page.png[retail-v1-landing-page]
 
-2. Select either the `Store Web Page` or "`TEST Store Web Page`"
-links brings you to a screen that looks like this:
+2. Select either the `Store Web Page` or `TEST Store Web Page` links brings you to a screen that looks like this:
 +
-link:/images/retail/retail-v1-store-page.png[image:/images/retail/retail-v1-store-page.png[retail-v1-store-page]
+image:/images/retail/retail-v1-store-page.png[retail-v1-store-page]
 +
 [NOTE]
 ====
-The applications are initially identical. The `TEST`" site is
-deployed to the `quarkuscoffeeshop-demo` namespace; the regular Store
-site is deployed to the `quarkuscoffeeshop-store` namespace.
+The applications are initially identical. The `TEST`" site is deployed to the `quarkuscoffeeshop-demo` namespace; the regular Store site is deployed to the `quarkuscoffeeshop-store` namespace.
 
-Each store requires supporting services, in PostgreSQL and Kafka. In our
-pattern, PostgreSQL is provided by the Crunchy PostgreSQL operator, and
-Kafka is provided by the Red Hat AMQ Streams operator. Each instance,
-the regular instance and the TEST instance, has its own instance of each
-of these supporting services it uses.
+Each store requires supporting services, in PostgreSQL and Kafka. In our pattern, PostgreSQL is provided by the Crunchy PostgreSQL operator, and Kafka is provided by the Red Hat AMQ Streams operator. Each instance, the regular instance and the TEST instance, has its own instance of each of these supporting services it uses.
 ====
 
-. Order by clicking the `Place an Order` button on the front page. The
-menu should look like this:
+. Order by clicking the `Place an Order` button on the front page. The menu should look like this:
 +
-link:/images/retail/retail-v1-store-web-menu.png[image:/images/retail/retail-v1-store-web-menu.png[retail-v1-store-web-menu]]
+image:/images/retail/retail-v1-store-web-menu.png[retail-v1-store-web-menu]
 
-. Click the `Add` button next to a menu item; the item name will appear.
-Add a name for the order:
-
-link:/images/retail/retail-v1-order-p1.png[image:/images/retail/retail-v1-order-p1.png[retail-v1-order-p1]]
-
-You can add as many orders as you want. On your last item, click the
-"`Place Order`" button on the item dialog:
-
-link:/images/retail/retail-v1-place-order.png[image:/images/retail/retail-v1-place-order.png[retail-v1-place-order]]
+. Click the `Add` button next to a menu item; the item name will appear. Add a name for the order:
++
+image:/images/retail/retail-v1-order-p1.png[image:/images/retail/retail-v1-order-p1.png[retail-v1-order-p1]
 
-As the orders are serviced by the barista and kitchen services, you can
-see their status in the "`Orders`" section of the page:
+. Add as many orders as you want. On your last item, click the `Place Order` button on the item dialog:
++
+image:/images/retail/retail-v1-place-order.png[image:/images/retail/retail-v1-place-order.png[retail-v1-place-order]
 
-link:/images/retail/retail-v1-orders-status.png[image:/images/retail/retail-v1-orders-status.png[retail-v1-orders-status]
+As the orders are serviced by the barista and kitchen services, you can see their status in the `Orders` section of the page:
++
+image:/images/retail/retail-v1-orders-status.png[retail-v1-orders-status]