using-vol-services../source/using-vol-services.html.md.erb
(the host page) and ../source/_using-vol-services.html.md.erb
(the partial that holds its content), cloudfoundry/docs-dev-guide../published/using-vol-services.html)using-vol-services.notes<%= vars.external_vol_win_note %>,
whose value in the book’s variables is a whole note:
<p class="note"><span class="note__title"><strong>Note</strong></span> NFS and SMB volume services are available for Linux cells only. …</p>
(template_variables.yml L176).
R-07 notes and admonitions names
this case. 12 values in the book hold a note; 7 are used by pages
(survey).<li> of the step’s “Where:” list, and the next sits
in the step itself, after that list. 41 of the book’s notes are in lists.`vers=3.0`) between <code> elements. The
published page renders it as code, because inside a list item the note is
part of a paragraph whose text is read as Markdown (published copy, line
786). Two notes in the book do this.> in a note: two <br> and <code>>= v7.1.48</code>.| # | Kind | Title | Sits in | Holds | Source |
|---|---|---|---|---|---|
| 1 | note | Note | the introduction, before the first h2 |
1 sentence pair; the whole note is the variable’s value | _using-vol-services L5 |
| 2 | note | Note | “Create and use NFS volume services” (h2), last block |
1 sentence | L237-L240 |
| 3 | important | Important | “Create an NFS volume service” (h3), step 1, inside the second item of the “Where:” list |
1 sentence, 1 code span | L257-L260 |
| 4 | important | Important | the same step, after the “Where:” list | 3 lines joined by <br>, 3 code spans (one written in Markdown) |
L266-L271 |
The notes check reads the place of notes 3 and 4 as list.
>= survives.<ul> becomes a Markdown list (or the tool’s own list), so that
note 3, inside it, can be the tool’s own admonition. The items and their
words do not change. Passthrough keeps the HTML.