From 3444581e69979c382169bcbb14b4e0fcbdc84272 Mon Sep 17 00:00:00 2001
From: Arno Gaboury <arnaud.gaboury@gmail.com>
Date: Sat, 30 Jun 2018 15:46:11 +0200
Subject: [PATCH 1/2] Update _Index.md

1. Code inside a list must be inside <code>  code </code>
2. The command line `cat MyCert | base64 -d` let you quickly verify the certificate integrity.
---
 .../troubleshooting-ha/job-complete-status/_index.md           | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/content/rancher/v2.x/en/installation/troubleshooting-ha/job-complete-status/_index.md b/content/rancher/v2.x/en/installation/troubleshooting-ha/job-complete-status/_index.md
index 70bd8a3aee4..086079a2e8c 100644
--- a/content/rancher/v2.x/en/installation/troubleshooting-ha/job-complete-status/_index.md
+++ b/content/rancher/v2.x/en/installation/troubleshooting-ha/job-complete-status/_index.md
@@ -20,8 +20,9 @@ Usually something is printed along the lines of `error: error converting YAML to
 <b>Things to check</b>
 <ul>
 <ul>
-<li>Is each of the base64 encoded certificate string placed directly after the key, for example: `tls.crt: LS01...`, there should be no newline/space before, in between or after.</li>
+<li>Is each of the base64 encoded certificate string placed directly after the key, for example: <code>tls.crt: LS01...</code>, there should be no newline/space before, in between or after.</li>
 <li>Is the YAML properly formatted, each indentation should be 2 spaces as shown in the template files.</li>
+<li>Verify the integrity of your certificate by running this command <code>cat MyCertificate | base64 -d</code> on Linux, <code>cat MyCertificate | base64 -D</code> on Mac OS . If any error exists, the command output will tell you.
 </ul>
 </ul>
 

From 86860564d94e5fe98428c73b9d8a21b3462c0f84 Mon Sep 17 00:00:00 2001
From: Arno Gaboury <arnaud.gaboury@gmail.com>
Date: Sat, 30 Jun 2018 19:22:09 +0200
Subject: [PATCH 2/2] Update _index.md

not fully sure if it is what was asked, but I changed the <code> tags
---
 .../troubleshooting-ha/job-complete-status/_index.md          | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/content/rancher/v2.x/en/installation/troubleshooting-ha/job-complete-status/_index.md b/content/rancher/v2.x/en/installation/troubleshooting-ha/job-complete-status/_index.md
index 086079a2e8c..9482401d586 100644
--- a/content/rancher/v2.x/en/installation/troubleshooting-ha/job-complete-status/_index.md
+++ b/content/rancher/v2.x/en/installation/troubleshooting-ha/job-complete-status/_index.md
@@ -20,9 +20,9 @@ Usually something is printed along the lines of `error: error converting YAML to
 <b>Things to check</b>
 <ul>
 <ul>
-<li>Is each of the base64 encoded certificate string placed directly after the key, for example: <code>tls.crt: LS01...</code>, there should be no newline/space before, in between or after.</li>
+<li>Is each of the base64 encoded certificate string placed directly after the key, for example: `tls.crt: LS01...`, there should be no newline/space before, in between or after.</li>
 <li>Is the YAML properly formatted, each indentation should be 2 spaces as shown in the template files.</li>
-<li>Verify the integrity of your certificate by running this command <code>cat MyCertificate | base64 -d</code> on Linux, <code>cat MyCertificate | base64 -D</code> on Mac OS . If any error exists, the command output will tell you.
+<li>Verify the integrity of your certificate by running this command `cat MyCertificate | base64 -d` on Linux, `cat MyCertificate | base64 -D` on Mac OS . If any error exists, the command output will tell you.
 </ul>
 </ul>