fix: more markdown cleanup

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

Author: butler54

README.md

@@ -1,14 +1,15 @@
 # coco-pattern
+
 This is a validated pattern for deploying confidential containers on OpenShift.
 
-The target operating model has two clusters: 
+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 
+- 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**
 
-On the platform a 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.

charts/all/letsencrypt/README.md

@@ -7,7 +7,8 @@
 Cert-manager needs the azure resource group for a zone in order to manage the DNS.
 Unfortunately this is a little tricky to get.
 
-To get this running on azure two compromises have been made
+To get this running on azure three compromises have been made:
+
 1. The required information (managed_zone_name and managed_zone resource group) can be obtained via the ansible imperative framework.
 
 2. The imperative framework is limited terms of feedback / logging. Please test carefully.