Skip to content

Commit e0b67b3

Browse files
authored
replace example
1 parent 68facec commit e0b67b3

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

supplementary_style_guide/style_guidelines/release-notes.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,7 @@ With this update, the X component has been removed from the Y package."
5151
Introduce each release note with a heading that summarizes the release note. This practice helps customers to quickly determine if the release note is relevant to them.
5252

5353
* The heading can, but does not need to be, a full sentence. Do not use a period at the end of the heading.
54-
* Use _sentence-style capitalization_, not _title case_. If necessary, headings can start with a lowercase letter in the case of a lowercase component name. For example: "```start``` does not start the computer when `donotstop` is stopped".
54+
* Use _sentence-style capitalization_, not _title case_. If necessary, headings can start with a lowercase letter in the case of a lowercase component name. For example: "```nvme-cli``` and `cryptsetup` are now available for Opal automation on NVMe SEDs".
5555

5656
* Write headings that are informative and specific without being overly long or too short. Adhere to the following guidelines:
5757
** Keep the heading under 120 characters.

0 commit comments

Comments
 (0)