diff --git a/en-US/C.xml b/en-US/C.xml index bee0b62..4084c54 100644 --- a/en-US/C.xml +++ b/en-US/C.xml @@ -332,16 +332,23 @@ - command line, command prompt, command-line + command line, command-line, command prompt - For an explanation of how to use these terms, refer to the appropriate entries in IBM Style + Use "command line" to refer to the place where commands are entered. + Use "command line" as a noun, and use "command-line" as an adjective. + + + For more details about how to use these terms, refer to the appropriate entries in IBM Style . + + Refer also to and to . + diff --git a/en-US/D.xml b/en-US/D.xml index ee4e3b3..bb8f48e 100644 --- a/en-US/D.xml +++ b/en-US/D.xml @@ -23,19 +23,9 @@ dash - In technical publications, IBM Style - - - - - recommends not to use em dashes. Use a colon or other suitable punctuation. - En dashes are used to show a range. - Refer to Dashes in IBM Style - - - - - . + Use a dash to show a range, such as for page numbers, letters, pages, or dates. + Otherwise, do not use dashes in technical content. + Instead, use other punctuation marks, such as commas, parentheses, or a colon. diff --git a/en-US/Design.xml b/en-US/Design.xml index 9753ef7..ae9c7c9 100644 --- a/en-US/Design.xml +++ b/en-US/Design.xml @@ -529,16 +529,49 @@ The ARN in the preceding output is different on your system. 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 Hat uses the ...output omitted... notation, starting and ending with an ellipsis, and highlighted in italics. + For omitting horizontal lines of output, Red Hat uses the ...output omitted... notation, starting and ending with an ellipsis, and highlighted in italics. -Notation for Excluding Part of Output +Notation for Omitting Horizontal Output [student@workstation image]$ podman build --layers=false -t nexus . STEP 1: FROM ubi8/ubi:8.3 Getting image source signatures ...output omitted... STEP 14: COMMIT ...output omitted... localhost/nexus:latest + + + + For omitting vertical columns of output, use a consistent notation such as an ellipsis (...). + + +Notation for Omitting Vertical Output + [user@host ~]$ oc get csv +NAME DISPLAY ... +barbican-operator.v1.0.0 Barbican Operator ... +cinder-operator.v1.0.0 Cinder Operator ... +designate-operator.v1.0.0 Designate Operator ... +glance-operator.v1.0.0 Glance Operator ... +heat-operator.v1.0.0 Heat Operator ... +horizon-operator.v1.0.0 Horizon Operator ... +...output omitted... + diff --git a/en-US/E.xml b/en-US/E.xml index e8e5754..bf7cb4f 100644 --- a/en-US/E.xml +++ b/en-US/E.xml @@ -46,7 +46,7 @@ - + enter diff --git a/en-US/S.xml b/en-US/S.xml index bd073ff..1b40ac8 100644 --- a/en-US/S.xml +++ b/en-US/S.xml @@ -299,7 +299,13 @@ shell prompt - Refers to the character at the beginning of the command line, and indicates that the shell is ready to accept commands. Do not use "command prompt", "terminal", or "shell". + Refers to the character at the beginning of the command line, and indicates that the shell is ready to accept commands. Do not use "command prompt" or "shell". + + + For example, "If you enter your username and password correctly, then you log in and get a shell prompt." + + + Refer also to and to . diff --git a/en-US/T.xml b/en-US/T.xml index f56a4e1..b966f4c 100644 --- a/en-US/T.xml +++ b/en-US/T.xml @@ -92,16 +92,32 @@ terminal - n. Do not use to describe where to type commands. Use "command line" instead. + n. Use "terminal" to refer to a text-based interface where typed instructions are entered, or to refer to a session of this type. - + + For example, "Open a terminal and log in to your OpenShift cluster", or "The exercise file captures any error messages from your terminal". + + + + Use "command line" instead to refer to the place where commands are entered. + + + For example, "Copy the command from the web console and paste it on the command line." + + + Refer also to and to . + + +