diff --git a/source/cloud-native-platform/path-to-live/tls-certificates.html.md.erb b/source/cloud-native-platform/path-to-live/tls-certificates.html.md.erb
index 12721a85..2704fa2f 100644
--- a/source/cloud-native-platform/path-to-live/tls-certificates.html.md.erb
+++ b/source/cloud-native-platform/path-to-live/tls-certificates.html.md.erb
@@ -28,9 +28,13 @@ If your site is being hosted on:
 - [Azure CDN](https://docs.microsoft.com/en-us/azure/cdn/)
 
 Then you must use [Microsoft managed certificates](https://docs.microsoft.com/en-us/azure/frontdoor/front-door-custom-domain-https#option-1-default-use-a-certificate-managed-by-front-door)
+
 You can automatically generate/deploy an Azure-manged certificate by copying an existing site in [Azure Platform Terraform](https://github.com/hmcts/azure-platform-terraform/commit/f6655ecb98de678647e0adae1aeb7dc693a01cb4)
+
 Please note, if the certificate status on 'domains' under Frontdoor in Azure portal does not show as 'deployed', you will need to manually validate the certificate by creating a TXT record on Azure-public-DNS like in this [example PR](https://github.com/hmcts/azure-public-dns/pull/1963)
+
 You can view the TXT record that needs created by clicking on the status under 'validation state'
+
 <img src="../../images/validate-dns.png" alt="Domain validation TXT record" width="500"/>
 
 ## Manual certificate requests