Scribd
Upload
21K views1 page

JEX-LAB-GUIDE-pdf 8

This document outlines conventions used to distinguish different types of text in course documentation, including: 1) Text appearing in command-line interfaces (CLI) or graphical user interfaces (GUI) is distinguished from chapter text using specific fonts. 2) Input text that must be entered by the user is shown in bold, while output text is normal style. 3) Syntax variables that are already defined are shown in a CLI/GUI variable style, while undefined variables requiring user input are in a CLI/GUI undefined style.

Uploaded by

Santiago Canale
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
21K views1 page

JEX-LAB-GUIDE-pdf 8

This document outlines conventions used to distinguish different types of text in course documentation, including: 1) Text appearing in command-line interfaces (CLI) or graphical user interfaces (GUI) is distinguished from chapter text using specific fonts. 2) Input text that must be entered by the user is shown in bold, while output text is normal style. 3) Syntax variables that are already defined are shown in a CLI/GUI variable style, while undefined variables requiring user input are in a CLI/GUI undefined style.

Uploaded by

Santiago Canale
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

Document Conventions

CU and GUI Text


Frequently t!1roughout this course, we refer to text that appears in a command-iine interface (CU)
or a grapl1ical user interface (GUI). To make the language of these documents easier to read, we
distinguish GUI and CLI text from chapter text according to the following table.

Style Description Usage Example

Franklin Gothic Normal text Most of what you read in the Lab Guide
and Student Guide.

Courier New Console text:


commit complete
Screen captures
Noncommand-related Exiting configuration mode
syntax

GUI text elements:


Select File > Open, and then click
Menu names Configuration.conf inthe
Filename text box.
Text field entry

Input Text Versus Output Text


You will also frequently see cases where you must enter input text yourself. Often these instances
will be shown in the context of where you must enter them. We use bold style to distinguish text
that is input versus text that is simply displayed.

Style Description Usage Example

Normal CLI No distinguishing variant. Physical interface: fxpO,


Enabled
Normal GUI
View configuration history by clicl\ing
Configuration > History.

CLI Input Text that you must enter. lab@San_Jose> show route
GUI Input Select File > Save, and type
config. ini in the Filename field.

Defined and Undefined Syntax Variables


Finally, tl1is course distinguishes between regular text and syntax variables, and it also
distinguishes between syntax variables where the value is already assigned (defined variables) and
syntax variables where you must assign the value (undefined variables). Note that these styles can
be combined with tl1e input style as well.

Style Description Usage Example

CLI Variable Text where variable value is policy my-peers


already assigned.
GUI Variable

Click my-peers in the dialog.

CLI Undefined Text where the variable's value Type set policy policy-name.
is the user's discretion and text
ping 10.0.x.y
where the variable's value as
GUI Undefined shown in the lab guide might Select File > Save, and type
differ from the value the user filename in the Filename field.
must input.

viii • Document Conventions www.juniper.net

You might also like