fix: more markdown stuff

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

Author: butler54

README.md

@@ -20,7 +20,6 @@ Future work includes:
 2. Supporting multiple infrastructure providers
 3. Supporting a more sophisticated workload such as confidential AI inference with protected GPUs.
 
-
 ## Current constraints and assumptions
 
 - Only currently is known to work with `azure` as the provider of confidential vms via peer-pods.
@@ -50,14 +49,11 @@ The pattern has been tested on Azure for two installation methods:
 The pattern has been tested on Azure for one installation method:
 1. Self managed OpenShift install using the `openshift-install` CLI
 
-
-
 ## 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. 
 
-
 `values-simple.yaml`: or the `simple` cluster group is the default for the pattern.
 It deploys a hello-openshift application 3 times: 
 - A standard pod
@@ -66,7 +62,6 @@ It deploys a hello-openshift application 3 times:
 
 ## Setup instructions
 
-
 ### Default single cluster setup with `values-simple.yaml`
 
 The instructions here presume you have a cluster. See further down for provisioning instructions for a cluster.
@@ -78,7 +73,6 @@ The instructions here presume you have a cluster. See further down for provision
 > [!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.
@@ -93,12 +87,10 @@ This only has to be done once.
 > [!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
     letsencrypt:
@@ -158,7 +150,6 @@ Red Hat a demo platform. This allows easy access for Red Hat associates and part
 ### 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
 2. Get the openshift installer
 3. Login to azure locally.