Style

Admonition blocks such as [NOTE], [TIP], or [WARNING] can be used to emphasize important issues. However, don’t overuse them, as this can interfere with the flow of the text .
There should be no more than three admonitions on a page.

Use a descriptive title for admonitions.
For example:

In some articles, it may be necessary to show the author.
Authors can identify themselves after the section title as follows:

For section, this should be in the overview.

For non-ASCII characters, you should use HTML character entity markup.

If your audience includes macOS users, provide the appropriate key-naming terminology. Spell out Command, rather than abbreviating it. For example:

You should use title or headline case for all titles, including chapter, section, and sub-section titles.

For a detailed description of capitalization rules, see for example:

Use the emphasis styles, such as [classname]#ClassName# emphasis for class names and [methodname]#methodName()# for methods.

Place currency symbols before the numeric amount. For example:

In general, in the absence of other information, we assume that the dollar ($) symbol implies U.S. dollars. It isn’t necessary to specify this.

However, where it’s required to distinguish between dollar currencies of different states, it should be written as in the following examples:

No strict rule exists for forming country codes in this context. Make sure that it’s clear which country is being referred to.

In our documentation, we use the format <month> <day number>, <year>. We don’t use the ordinal abbreviation suffixes -st, -nd, -rd or -th. Nor do we write the word the between the month name and the day number. For example:

Avoid expressing dates using variations of the mm/dd/yyyy or dd/mm/yyyy formats. Different conventions for these formats are used around the world, so that the possibility of confusion and misunderstanding is high. Instead, write out dates using month names, as described earlier.

Write out the days of the week in full, if space allows this. Otherwise, abbreviate the names to three characters, as follows:

The euro symbol (€) is represented as € in AsciiDoc. In amounts of money, place the euro symbol immediately before the numeric quantity, in the same way as for, for example, the dollar or pound symbol.

You should use the word follows or following to introduce a list or code listing.
Examples are introduced with for example.
You should end the sentence with a colon (not a period).

For example:

Use empty parentheses at the end of method names to denote that they are methods. In general, don’t list parameter types for methods, unless this is required to mention a specific version of a method. It may also be necessary to specify a parameter when it’s relevant in the context. For example:

If you need to show the multiplication sign, use × (×), not the letter x. One case for using the multiplication sign is to refer to dimensions. There should be a non-breaking space on either side of the multiplication sign. For example:

In code, you need to use the symbol that’s required by the language you are using, which is generally the asterisk character (*).

Don’t use the # character to display a number. For example:

In technical documentation, we very often want to describe the procedures that are necessary to perform some task. Such procedures usually consist of a series of steps.

Usually, we start with a top-level sentence. For example:

Don’t start with an incomplete sentence at the top-level which is then completed by the text of each step. This structure obliges the reader to keep the top-level text in mind to interpret the subsequent text correctly. For example:

Use parallel structures in the steps that make up the procedure. In other words, structure each step in a similar way to the others.

Every page should have at least one screenshot. There should at least be a screenshot in an introduction or overview section.

The basic structure of a new section file is as follows:

8E813D10-01D3-441A-94F2-15D3CD6864C4