---
title: "Formatting"
description: "To help users get through content more effectively and to draw attention to important information throughout the content, we use the following formatting in Veeam technical documentation."
canonical: "https://helpcenter.veeam.com/docs/styleguide/tw/formatting.html"
breadcrumb: "Style Guide > Formatting"
dateModified: "2026-09-03"
---

# Formatting

To help users get through content more effectively and to draw attention to important information throughout the content, we use the following formatting in Veeam technical documentation.

## Bold

Use **bold** formatting for static interface elements: wizard names, window names, buttons, links, options, check boxes, step names, list names, icon names, menu names, pane names, tab names, toolbar names, ribbon names and view names. Also, use bold formatting to describe report output: report names, section names and table names. 

::: important

To emphasize a key or a combination of keys pressed on the keyboard, include the key or the combination of keys in square brackets and do not use any formatting. For key combinations, do not insert spaces between keys and the plus sign.

:::

## Italic

Use *italic* formatting for selectable interface elements (that is, drop-down list options, object types) and input data you enter (that is, object names, parameter names, parameter values, field values). Also, use italic formatting for error messages, section names if referencing an external document, and [state and status](state.md) names.

## Courier

Use `courier` formatting for anything that can be copied/pasted into a command line: URL paths, folder names, file names, utility names, syntax, variables, parameters and properties.

## Examples

1. Complete the [**New Orchestration Plan**]{.mdhl-correct} [wizard]{.mdhl-correct}. 
2. At the [**Scope**]{.mdhl-correct} [step]{.mdhl-correct}, in the [**Available Scopes**]{.mdhl-correct} [list]{.mdhl-correct}, select a scope for which you want to create the plan.
3. At the [**Virtual Machines**]{.mdhl-correct} [step]{.mdhl-correct} of the wizard, [click]{.mdhl-correct} [**Exclusions**]{.mdhl-correct}.
4. On the [**Home**]{.mdhl-correct} [tab]{.mdhl-correct}, [click]{.mdhl-correct} [**Backup Job**]{.mdhl-correct} [>]{.mdhl-correct} [**Virtual machine**]{.mdhl-correct} [>]{.mdhl-correct} [**VMware vSphere**]{.mdhl-correct}.
5. Use the toolbar at the top right corner of the window to switch between [views:]{.mdhl-correct} [**Hosts and Clusters**]{.mdhl-correct}[,]{.mdhl-correct} [**VMs and Templates**]{.mdhl-correct}[,]{.mdhl-correct} [**Datastores and VMs**]{.mdhl-correct}[,]{.mdhl-correct} [**VMs and Tags**]{.mdhl-correct}.
6. Click the [**Schedule**]{.mdhl-correct} [icon]{.mdhl-correct} next to the [**Start testing on the following day and time**]{.mdhl-correct} [field]{.mdhl-correct}, configure the necessary schedule, and [click]{.mdhl-correct} [**Apply**]{.mdhl-correct}.
7. Select the [**Limit maximum concurrent tasks**]{.mdhl-correct} [check box]{.mdhl-correct} and specify the maximum allowed number of concurrent tasks for the backup repository.
8. To run the job at a specific time every day, select the [**Daily at this time**]{.mdhl-correct} [option]{.mdhl-correct}.
9. Click the [**Pick resource pool for selected VMs**]{.mdhl-correct} [link]{.mdhl-correct}.
10. In the [**Choose Resource Pool**]{.mdhl-correct} [window]{.mdhl-correct}, [click]{.mdhl-correct} [**Add VM**]{.mdhl-correct}.
11. Use the [**Up**]{.mdhl-correct} [and]{.mdhl-correct} [**Down**]{.mdhl-correct} [buttons]{.mdhl-correct} on the right to move the VM or VM container up and down in the list.
12. You can click the name of an undersized VM in the [**RAM analysis**]{.mdhl-correct} [table]{.mdhl-correct} to drill down to performance details for this VM.
13. From the [**Performance Modeling Based On**]{.mdhl-correct} [drop-down list]{.mdhl-correct}, [select]{.mdhl-correct} [*Average Usage*]{.mdhl-correct}.
14. In the [**Top N Count**]{.mdhl-correct} [field]{.mdhl-correct}, [enter]{.mdhl-correct} [*10*]{.mdhl-correct}.
15. When configuring global email notification settings, make sure you select an event type on which you want to receive reports. You can [select]{.mdhl-correct} any of the following event types: [*Success*]{.mdhl-correct}[,]{.mdhl-correct} [*Warning*]{.mdhl-correct} [or]{.mdhl-correct} [*Error*]{.mdhl-correct}.
16. If none of the conditions listed in the [**Extent state**]{.mdhl-correct} [column]{.mdhl-correct} is true, the report status will be shown as [*Success*]{.mdhl-correct}.
17. This action will interrupt plan execution. Currently executing steps will be completed, then the plan will enter the [*Halted*]{.mdhl-correct} [state]{.mdhl-correct}.
18. If a Veeam Agent backup job managed by the backup server fails to complete successfully, you will encounter the following [error:]{.mdhl-correct} [*Failed to start backup job Error: Unknown invoker method: 2757*]{.mdhl-correct}.
19. In a web browser, navigate to the Orchestrator UI [web address]{.mdhl-correct}. The address consists of an FQDN of the Orchestrator server and the website port specified during installation: [`https://<hostname>:<port>`]{.mdhl-correct}
20. To define a list of exclusions, you can use environmental [variables]{.mdhl-correct} such as [`%TEMP%`]{.mdhl-correct} and [`%windir%`]{.mdhl-correct}.
21. The antivirus software described in the [`AntivirusInfos.xml`]{.mdhl-correct} [file]{.mdhl-correct}. Veeam Backup & Replication creates this configuration file on every machine with the Mount Server role and stores the file in the [`%ProgramFiles%\Common Files\Veeam\Backup and Replication\Mount Service`]{.mdhl-correct} [folder]{.mdhl-correct}.
22. To retrieve a representation of an Orchestrator scope, send the HTTP GET request to the URL of the [`/Scopes/{id}`]{.mdhl-correct} [resource]{.mdhl-correct}.

    ```
    GET https://<hostname>:<port>/v2/Sites/{siteId}/Scopes/{id}
    ```