fix: more language fixes

Signed-off-by: Chris Butler <chris.butler@redhat.com>

Author: butler54

README.md

@@ -7,10 +7,10 @@ The target operating model has two clusters:
 - One in a "trusted" zone where the remote attestation, KMS and Key Broker infrastructure are deployed.
 - A second where a subset of workloads are deployed in confidential containers.
 
-**For the current version of this application the confidential containers assumes deployment to Azure**
+The current version of this application the confidential containers assumes deployment to Azure.
+
+On the platform a sample workload is deployed:
 
-On the platform a a sample workload is deployed:
- 
 1. Sample hello world applications to allow users to experiment with the policies for CoCo and the KBS (trustee).
 2. A sample application `kbs-access` which presents secrets obtained from trustee to a web service. This is designed to allow users to test locked down environments.
 
@@ -31,12 +31,14 @@ Future work includes:
 
 ### `2.*`
 This is currently the `main` branch for the repository. Version 2.* of the pattern is currently constrained to support:
+
 - (OpenShift Sandboxed Containers Operator) `1.9.*`
 - Trustee `0.3.*`
 
 This limits support to OpenShift 4.16 and higher.
 
 The pattern has been tested on Azure for two installation methods:
+
 1. Installing onto an ARO cluster
 2. Self managed OpenShift install using the `openshift-install` CLI.
 
@@ -47,9 +49,11 @@ The pattern has been tested on Azure for two installation methods:
 1.0.0 supports OpenShift Sandboxed containers version `1.8.1` along with Trustee version `0.2.0`.
 
 The pattern has been tested on Azure for one installation method:
+
 1. Self managed OpenShift install using the `openshift-install` CLI
+2. Installing on top of an existing Azure Red Hat OpenShift (ARO) cluster
 
-## validated pattern flavours 
+## Validated pattern flavours 
 **Today the demo has one flavour**. 
 A number are planned based on various different hub cluster-groups.
 You can change between behaviour by configuring [`global.main.clusterGroupName`](https://validatedpatterns.io/learn/values-files/) key in the `values-global.yaml` file. 
@@ -67,13 +71,15 @@ It deploys a hello-openshift application 3 times:
 The instructions here presume you have a cluster. See further down for provisioning instructions for a cluster.
 
 #### Fork and Clone the GitHub repo
+
 1. Following [standard validated patterns workflow](https://validatedpatterns.io/learn/workflow/) fork the repository and clone to your development environment which has `podman` and `git`
 2. If using a particular version (e.g. `1.0.0`) checkout the correct tag.
 
 > [!TIP]
 > Forking is essential as the validated pattern uses ArgoCD to reconcile it's state against your remote (forked) repository. 
 
 #### Configuring required secrets / parameters
+
 The secrets here secure Trustee and the peer-pod vms. Mostly they are for demonstration purposes. 
 This only has to be done once.
 
@@ -118,7 +124,8 @@ If you need a Let's Encrypt certificate to be issued the `letsencrypt` applicati
 > Configuration changes are only effective once committed and pushed to your remote repository.
 
 #### Installing onto a cluster
-Once you configuration is pushed (if required) `./pattern.sh make install` to provision a cluster. 
+
+Once you configuration is pushed (if required) `./pattern.sh make install` to provision a cluster.
 
 > [!TIP]
 > The branch and default origin you have checked-out in your local repository is used to determine what ArgoCD and the patterns operator should reconcile against. Typical choices are to use the main for your fork.
@@ -128,11 +135,12 @@ Once you configuration is pushed (if required) `./pattern.sh make install` to pr
 ### Single cluster install on an OCP cluster on azure using Red Hat Demo Platform
 
 Red Hat a demo platform. This allows easy access for Red Hat associates and partners to ephemeral cloud resources. The pattern is known to work with this setup.
+
 1. Get the [openshift installer](https://console.redhat.com/openshift/downloads)
    1. **NOTE: openshift installer must be updated regularly if you want to automatically provision the latest versions of OCP**
 2. Get access to an [Azure Subscription Based Blank Open Environment](https://catalog.demo.redhat.com/catalog?category=Open_Environments&search=azure&item=babylon-catalog-prod%2Fazure-gpte.open-environment-azure-subscription.prod).
 3. Import the required azure environmental variables (see coded block):
-   ```
+   ```shell
       export GUID=
       export CLIENT_ID=
       export PASSWORD=
@@ -148,6 +156,7 @@ Red Hat a demo platform. This allows easy access for Red Hat associates and part
   1. You *may* need to recreate the hello world peer-pods depending on timeouts.
 
 ### Single cluster install on plain old azure *not* using Red Hat Demo Platform
+
 **NOTE: Don't use the default node sizes.. increase the node sizes such as below**
 
 1. Login to console.redhat.com
@@ -170,4 +179,5 @@ Red Hat a demo platform. This allows easy access for Red Hat associates and part
   3. `./pattern.sh make install`
 
 ### Multi cluster setup
+
 TBD