fix: autofixed

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

Author: butler54

README.md

@@ -30,6 +30,7 @@ Future work includes:
 ## Major versions
 
 ### `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.*`
@@ -46,20 +47,23 @@ The pattern has been tested on Azure for two installation methods:
 > You need an external CA signed certificate for to be added (e.g. with let's encrypt) to a self-managed install
 
 ### `1.0.0`
+
 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 
-**Today the demo has one flavour**. 
+## 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. 
+You can change between behaviour by configuring [`global.main.clusterGroupName`](https://validatedpatterns.io/learn/values-files/) key in the `values-global.yaml` file.
 
 `values-simple.yaml`: or the `simple` cluster group is the default for the pattern.
-It deploys a hello-openshift application 3 times: 
+It deploys a hello-openshift application 3 times:
+
 - A standard pod
 - A kata container with peer-pods
 - A confidential kata-container
@@ -76,26 +80,27 @@ The instructions here presume you have a cluster. See further down for provision
 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. 
+> 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. 
+The secrets here secure Trustee and the peer-pod vms. Mostly they are for demonstration purposes.
 This only has to be done once.
 
 1. Run `sh scripts/gen-secrets.sh`
 
 > [!NOTE]
 > Once generated this script will not override secrets. Be careful when doing multiple tests.
 
-#### Configuring let's encrypt.
+#### Configuring let's encrypt
 
 > [!IMPORTANT]
 > Ensure you have password login available to the cluster. Let's encrypt will replace the API certificate in addition to the certificates to user with routes.
 
 Trustee requires a trusted CA issued certificate. Let's Encrypt is included for environments without a trusted cert on OpenShift's routes.
 
 If you need a Let's Encrypt certificate to be issued the `letsencrypt` application configuration needs to be changed as below.
+
 ```yaml
     ---
     # Default configuration, safe for ARO
@@ -140,13 +145,15 @@ Red Hat a demo platform. This allows easy access for Red Hat associates and part
    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=
       export TENANT=
       export SUBSCRIPTION=
       export RESOURCEGROUP=
+
   ```
 1. Ensure Let's encrypt 
 1. Run the wrapper install script 
@@ -171,12 +178,13 @@ Red Hat a demo platform. This allows easy access for Red Hat associates and part
     azure:
       type: Standard_D8s_v5
 ```
+
 1. `mkdir ./ocp-install && mv openshift-install.yaml ./ocp-install`
 2. `openshift-install create cluster --dir=./ocp-install`
 3. Once installed:
-  1. Login to `oc`
-  2. Configure Let's Encrypt (if required)
-  3. `./pattern.sh make install`
+1. Login to `oc`
+2. Configure Let's Encrypt (if required)
+3. `./pattern.sh make install`
 
 ### Multi cluster setup
 

rhdp/README.md

@@ -9,5 +9,5 @@ The scripts in this directory help users of that platform automate deployments.
 2. Download the credentials
 3. Load the credentials into your environment (e.g. using `direnv`)
 4. Launch the wrapper script from the repository root directory:
-   1.  `bash ./rhdp/wrapper.sh eastasia`
+   1. `bash ./rhdp/wrapper.sh eastasia`
    2. The wrapper script **requires** an azure region code this code SHOULD be the same as what was selected in RHDP.