Document conventions
Typographical conventions
Fortinet documentation uses the following typographical conventions:
Table 2: Typographical conventions in Fortinet technical documentation
Convention | Example |
|
|
| |
Button, menu, text box, | From Minimum log level, select Notification. | |
field, or check box label |
|
|
|
|
|
CLI input | config system dns |
|
| set primary <address_ipv4> | |
| end |
|
CLI output | ||
| comments | : (null) |
| opmode | : nat |
Emphasis | HTTP connections are not secure and can be intercepted by a third | |
| party. |
|
File content | <HTML><HEAD><TITLE>Firewall | |
| Authentication</TITLE></HEAD> | |
| <BODY><H4>You must authenticate to use this | |
| service.</H4> |
|
Hyperlink | Visit the Fortinet Technical Support web site, | |
| https://support.fortinet.com. | |
Keyboard entry | Type a name for the remote VPN peer or client, such as | |
| Central_Office_1. |
|
Navigation | Go to VPN > IPSEC > Auto Key (IKE). | |
|
| |
Publication | For details, see the FortiOS Handbook. | |
|
|
|
CLI command syntax conventions
This guide uses the following conventions to describe the syntax to use when entering commands in the Command Line Interface (CLI).
Brackets, braces, and pipes are used to denote valid permutations of the syntax. Constraint notations, such as <address_ipv4>, indicate which data types or string patterns are acceptable value input.
FortiGate Voice Version 4.0 MR1 Administration Guide