Lines Matching refs:content

12 Zephyr Project content is written using the `reStructuredText`_ markup
15 view this content either in its raw form as .rst markup files, or (with
17 to generate the documentation in HTML or PDF format. The HTML content can
18 then be viewed using a web browser. This same .rst content is served by the
51    some content goes here
110 content::
138 apply to the next non-comment element (e.g., paragraph), or to content
270 link to the "raw" content,
315 The content immediately following
404 line of the code-block body, and the body content is indented three
438 paragraph with a double colon (``::``) and indent the code block content
440 highlighting package makes a best guess at the type of content in the
470 Indenting is significant in reST file content, and using spaces is
471 preferred.  Extra indenting can (unintentionally) change the way content
472 is rendered too.  For lists and directives, indent the content text to
508 content to the reader via a tabbed interface. When the reader clicks on
509 a tab, the content for that tab is displayed, for example::
575 in the Zephyr setup.  Within a tab, you can have most any content *other