https://fortinetcloudcse.github.io/UserRepo/02hugo/9_commands_and_output.htmlCommands and expected output style Use plain markdown code fences — no shortcode nesting. Follow this style for every command/output pair: No $ prompt in the command. One command per block, preceded by a sentence that says what it does. Introduce the output with “The output is similar to:”. Use [...] for elided lines in long output. Reserve tabs for genuine alternatives (e.g. bash vs PowerShell) — not for hiding output. run= targets Add {run="<target>"} to a bash, sh, shell or text fence to get a coloured header badge. Five targets get a fixed colour and label — bastion, local, pod, browser (each reads “Run on: <Target>”) and chatbot (reads “Ask the chatbot”, see below); anything else gets a neutral badge.Hugoen-US