Lines Matching refs:body

32 writing rST documentation elsewhere, or for enriching the body of
82     content body, both, or neither.
93     the body.
96   * All items will be generated with the form: "argument -- body"
109     argument, but not the body.
112   * All items will be generated with the form "name (type) -- body"
127 :availability: This field list is available in the body of Command,
152 :availability: This field list is only available in the body of the
183 :availability: This field list is only available in the body of the
219 :availability: This field list is only available in the body of the
250 :availability: This field list is only available in the body of the Enum
277 :availability: This field list is only available in the body of the
306 :availability: This field list is available in the body of Event or
461      Content body, arbitrary rST is allowed here.
511 does not take a content body, nor any options. All subsequent QAPI
533 a content body, but it can be omitted. All subsequent QAPI directives
555 Sphinx or QAPI options, and the documentation body may contain
590 Sphinx or QAPI options, and the documentation body may contain
625 Sphinx or QAPI options, and the documentation body may contain
659 documentation body may contain ``:memb:`` or ``:feat:`` info field list
692 standard Sphinx or QAPI options, and the documentation body may contain