From a862a12b7ce9dabda6e511770daac3bf1c3b0970 Mon Sep 17 00:00:00 2001
From: Julian Cable <jcable@redhat.com>
Date: Thu, 13 Jul 2023 18:41:39 +0100
Subject: [PATCH 1/3] Added guidance on omitting part of an output

---
 en-US/Design.xml | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

diff --git a/en-US/Design.xml b/en-US/Design.xml
index a44f92d..9d50bde 100644
--- a/en-US/Design.xml
+++ b/en-US/Design.xml
@@ -475,6 +475,25 @@ $ vi myFile.txt
 --initial-dashboard-password=DASHBOARD_PASSWORD --dashboard-password-noupdate \
 --allow-fqdn-hostname</screen>
 
+</example>
+
+	</section>
+
+			 <section>
+				<title>Omitting Part of Output</title>
+          <para>
+            For the sake of brevity, do not show all output to the user in all cases, but only those parts of any output that are relevant to the context that is described. 
+			Where output is not included, place a marker to show that information is purposely excluded.
+			When shortening the output, use the <emphasis>...output omitted...</emphasis> notation, starting and ending with an ellipsis, and highlight it in italics.
+          </para>
+
+<example><title>Notation for Excluding Part of Output</title>
+<screen>[student@workstation image]$ podman build --layers=false -t nexus .
+STEP 1: FROM ubi8/ubi:8.3
+Getting image source signatures
+<emphasis>...output omitted...</emphasis>
+STEP 14: COMMIT <emphasis>...output omitted...</emphasis> localhost/nexus:latest</screen>
+
 </example>
 
 	</section>

From 301dde4460936313b57b66a2c2641a6bfd7921ce Mon Sep 17 00:00:00 2001
From: Julian Cable <jcable@redhat.com>
Date: Fri, 14 Jul 2023 10:03:15 +0100
Subject: [PATCH 2/3] Updated wording

---
 en-US/Design.xml | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/en-US/Design.xml b/en-US/Design.xml
index 9d50bde..4fa3561 100644
--- a/en-US/Design.xml
+++ b/en-US/Design.xml
@@ -484,7 +484,8 @@ $ vi myFile.txt
           <para>
             For the sake of brevity, do not show all output to the user in all cases, but only those parts of any output that are relevant to the context that is described. 
 			Where output is not included, place a marker to show that information is purposely excluded.
-			When shortening the output, use the <emphasis>...output omitted...</emphasis> notation, starting and ending with an ellipsis, and highlight it in italics.
+			When shortening the output, use a consistent notation.
+			Red{nbsp} uses the <emphasis>...output omitted...</emphasis> notation, starting and ending with an ellipsis, and highlighted in italics.
           </para>
 
 <example><title>Notation for Excluding Part of Output</title>

From 0e71014d77a4793feadacd3c62ec246777ab86b3 Mon Sep 17 00:00:00 2001
From: Julian Cable <jcable@redhat.com>
Date: Fri, 14 Jul 2023 11:50:34 +0100
Subject: [PATCH 3/3] Typo fix

---
 en-US/Design.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/en-US/Design.xml b/en-US/Design.xml
index 4fa3561..66aca59 100644
--- a/en-US/Design.xml
+++ b/en-US/Design.xml
@@ -485,7 +485,7 @@ $ vi myFile.txt
             For the sake of brevity, do not show all output to the user in all cases, but only those parts of any output that are relevant to the context that is described. 
 			Where output is not included, place a marker to show that information is purposely excluded.
 			When shortening the output, use a consistent notation.
-			Red{nbsp} uses the <emphasis>...output omitted...</emphasis> notation, starting and ending with an ellipsis, and highlighted in italics.
+			Red{nbsp}Hat uses the <emphasis>...output omitted...</emphasis> notation, starting and ending with an ellipsis, and highlighted in italics.
           </para>
 
 <example><title>Notation for Excluding Part of Output</title>