MANUAL: use level-3 headings for extensions (to avoid gaps).

MANUAL.txt

@@ -3339,7 +3339,7 @@ options like `--markdown-headings`).
 
 ## Typography
 
-#### Extension: `smart` ####
+### Extension: `smart` ###
 
 Interpret straight quotes as curly quotes, `---` as em-dashes,
 `--` as en-dashes, and `...` as ellipses. Nonbreaking spaces are
@@ -3372,7 +3372,7 @@ pandoc will use unicode quotation mark and dash characters.
 
 ## Headings and sections
 
-#### Extension: `auto_identifiers` ####
+### Extension: `auto_identifiers` ###
 
 A heading without an explicitly specified identifier will be
 automatically assigned a unique identifier based on the heading text.
@@ -3439,13 +3439,13 @@ and the identifier will be attached to the enclosing `<section>`
 sections to be manipulated using JavaScript or treated differently in
 CSS.
 
-#### Extension: `ascii_identifiers` ####
+### Extension: `ascii_identifiers` ###
 
 Causes the identifiers produced by `auto_identifiers` to be pure ASCII.
 Accents are stripped off of accented Latin letters, and non-Latin
 letters are omitted.
 
-#### Extension: `gfm_auto_identifiers` ####
+### Extension: `gfm_auto_identifiers` ###
 
 Changes the algorithm used by `auto_identifiers` to conform to
 GitHub's method.  Spaces are converted to dashes (`-`),
@@ -3506,7 +3506,7 @@ their respective sections of [Pandoc's Markdown]:
 
 ## Literate Haskell support
 
-#### Extension: `literate_haskell` ####
+### Extension: `literate_haskell` ###
 
 Treat the document as literate Haskell source.
 
@@ -3567,7 +3567,7 @@ picked up by the Haskell compiler.
 
 ## Other extensions
 
-#### Extension: `empty_paragraphs` ####
+### Extension: `empty_paragraphs` ###
 
 Allows empty paragraphs.  By default empty paragraphs are
 omitted.
@@ -3580,7 +3580,7 @@ input formats
 output formats
 :  `docx`, `odt`, `opendocument`, `html`, `latex`
 
-#### Extension: `native_numbering` ####
+### Extension: `native_numbering` ###
 
 Enables native numbering of figures and tables. Enumeration
 starts at 1.
@@ -3590,7 +3590,7 @@ This extension can be enabled/disabled for the following formats:
 output formats
 :  `odt`, `opendocument`, `docx`
 
-#### Extension: `xrefs_name` ####
+### Extension: `xrefs_name` ###
 
 Links to headings, figures and tables inside the document are
 substituted with cross-references that will use the name or caption
@@ -3607,7 +3607,7 @@ This extension can be enabled/disabled for the following formats:
 output formats
 :  `odt`, `opendocument`
 
-#### Extension: `xrefs_number` ####
+### Extension: `xrefs_number` ###
 
 Links to headings, figures and tables inside the document are
 substituted with cross-references that will use the number
@@ -3627,7 +3627,7 @@ This extension can be enabled/disabled for the following formats:
 output formats
 :  `odt`, `opendocument`
 
-#### Extension: `styles` #### {#ext-styles}
+### Extension: `styles` ### {#ext-styles}
 
 When converting from docx, read all docx styles as divs (for
 paragraph styles) and spans (for character styles) regardless
@@ -3638,12 +3638,12 @@ Disabled by default.
 input formats
 :  `docx`
 
-#### Extension: `amuse` ####
+### Extension: `amuse` ###
 
 In the `muse` input format, this enables Text::Amuse
 extensions to Emacs Muse markup.
 
-#### Extension: `raw_markdown` ####
+### Extension: `raw_markdown` ###
 
 In the `ipynb` input format, this causes Markdown cells
 to be included as raw Markdown blocks (allowing lossless
@@ -3674,14 +3674,14 @@ alphabetical markers for ordered lists to be parsed in addition to arabic ones.
 Note that for Org, this does not include roman numerals or the `#` placeholder
 that are enabled by the extension in Pandoc's Markdown.
 
-#### Extension: `element_citations` ####
+### Extension: `element_citations` ###
 
 In the `jats` output formats, this causes reference items to
 be replaced with `<element-citation>` elements. These
 elements are not influenced by CSL styles, but all information
 on the item is included in tags.
 
-#### Extension: `ntb` ####
+### Extension: `ntb` ###
 
 In the `context` output format this enables the use of [Natural Tables
 (TABLE)](https://wiki.contextgarden.net/TABLE) instead of the default
@@ -3689,7 +3689,7 @@ In the `context` output format this enables the use of [Natural Tables
 Natural tables allow more fine-grained global customization but come
 at a performance penalty compared to extreme tables.
 
-#### Extension: `tagging` ####
+### Extension: `tagging` ###
 
 Enabling this extension with `context` output will produce markup
 suitable for the production of tagged PDFs. This includes
@@ -3735,7 +3735,7 @@ A paragraph is one or more lines of text followed by one or more blank lines.
 Newlines are treated as spaces, so you can reflow your paragraphs as you like.
 If you need a hard line break, put two or more spaces at the end of a line.
 
-#### Extension: `escaped_line_breaks` ####
+### Extension: `escaped_line_breaks` ###
 
 A backslash followed by a newline is also a hard line break.
 Note:  in multiline and grid table cells, this is the only way
@@ -3775,7 +3775,7 @@ As with setext-style headings, the heading text can contain formatting:
 
     # A level-one heading with a [link](/url) and *emphasis*
 
-#### Extension: `blank_before_header` ####
+### Extension: `blank_before_header` ###
 
 Original Markdown syntax does not require a blank line before a heading.
 Pandoc does require this (except, of course, at the beginning of the
@@ -3786,7 +3786,7 @@ wrapping). Consider, for example:
     I like several of their flavors of ice cream:
     #22, for example, and #5.
 
-#### Extension: `space_in_atx_header` ####
+### Extension: `space_in_atx_header` ###
 
 Many Markdown implementations do not require a space between the
 opening `#`s of an ATX heading and the heading text, so that
@@ -3798,7 +3798,7 @@ pandoc does require the space.
 See also the [`auto_identifiers`
 extension](#extension-auto_identifiers) above.
 
-#### Extension: `header_attributes` ####
+### Extension: `header_attributes` ###
 
 Headings can be assigned attributes using this syntax at the end
 of the line containing the heading text:
@@ -3839,7 +3839,7 @@ the heading will not be included in a table of contents.
 (Currently this feature is only implemented for certain
 formats: those based on LaTeX and HTML, PowerPoint, and RTF.)
 
-#### Extension: `implicit_header_references` ####
+### Extension: `implicit_header_references` ###
 
 Pandoc behaves as if reference links have been defined for each heading.
 So, to link to a heading
@@ -3916,7 +3916,7 @@ block in a block quote, you need five spaces after the `>`:
 
     >     code
 
-#### Extension: `blank_before_blockquote` ####
+### Extension: `blank_before_blockquote` ###
 
 Original Markdown syntax does not require a blank line before a
 block quote.  Pandoc does require this (except, of course, at
@@ -3950,7 +3950,7 @@ Note: blank lines in the verbatim text need not begin with four spaces.
 
 ### Fenced code blocks ###
 
-#### Extension: `fenced_code_blocks` ####
+### Extension: `fenced_code_blocks` ###
 
 In addition to standard indented code blocks, pandoc supports
 *fenced* code blocks.  These begin with a row of three or more
@@ -3976,12 +3976,12 @@ row of tildes or backticks at the start and end:
     ~~~~~~~~~~
     ~~~~~~~~~~~~~~~~
 
-#### Extension: `backtick_code_blocks` ####
+### Extension: `backtick_code_blocks` ###
 
 Same as `fenced_code_blocks`, but uses backticks (`` ` ``) instead of tildes
 (`~`).
 
-#### Extension: `fenced_code_attributes` ####
+### Extension: `fenced_code_attributes` ###
 
 Optionally, you may attach attributes to fenced or backtick code block using
 this syntax:
@@ -4052,7 +4052,7 @@ below.
 
 ## Line blocks
 
-#### Extension: `line_blocks` ####
+### Extension: `line_blocks` ###
 
 A line block is a sequence of lines beginning with a vertical bar (`|`)
 followed by a space.  The division into lines will be preserved in
@@ -4192,7 +4192,7 @@ and this one:
     7.  two
     1.  three
 
-#### Extension: `fancy_lists` ####
+### Extension: `fancy_lists` ###
 
 Unlike original Markdown, pandoc allows ordered list items to be marked
 with uppercase and lowercase letters and roman numerals, in addition to
@@ -4225,7 +4225,7 @@ ordered list marker in place of a numeral:
 
 Note:  the '`#`' ordered list marker doesn't work with `commonmark`.
 
-#### Extension: `startnum` ####
+### Extension: `startnum` ###
 
 Pandoc also pays attention to the type of list marker used, and to the
 starting number, and both of these are preserved where possible in the
@@ -4254,7 +4254,7 @@ If default list markers are desired, use `#.`:
     #.  two
     #.  three
 
-#### Extension: `task_lists` ####
+### Extension: `task_lists` ###
 
 Pandoc supports task lists, using the syntax of GitHub-Flavored Markdown.
 
@@ -4263,7 +4263,7 @@ Pandoc supports task lists, using the syntax of GitHub-Flavored Markdown.
 
 ### Definition lists ###
 
-#### Extension: `definition_lists` ####
+### Extension: `definition_lists` ###
 
 Pandoc supports definition lists, using the syntax of
 [PHP Markdown Extra] with some extensions.[^3]
@@ -4323,7 +4323,7 @@ extension][Extension: `compact_definition_lists`].)
 
 ### Numbered example lists ###
 
-#### Extension: `example_lists` ####
+### Extension: `example_lists` ###
 
 The special list marker `@` can be used for sequentially numbered
 examples. The first list item with a `@` marker will be numbered '1',
@@ -4426,14 +4426,14 @@ Four kinds of tables may be used. The first three kinds presuppose the use of
 a fixed-width font, such as Courier. The fourth kind can be used with
 proportionally spaced fonts, as it does not require lining up columns.
 
-#### Extension: `table_captions` ####
+### Extension: `table_captions` ###
 
 A caption may optionally be provided with all 4 kinds of tables (as
 illustrated in the examples below). A caption is a paragraph beginning
 with the string `Table:` (or `table:` or just `:`), which will be stripped
 off. It may appear either before or after the table.
 
-#### Extension: `simple_tables` ####
+### Extension: `simple_tables` ###
 
 Simple tables look like this:
 
@@ -4477,7 +4477,7 @@ When the header row is omitted, column alignments are determined on the basis
 of the first line of the table body. So, in the tables above, the columns
 would be right, left, center, and right aligned, respectively.
 
-#### Extension: `multiline_tables` ####
+### Extension: `multiline_tables` ###
 
 Multiline tables allow header and table rows to span multiple lines
 of text (but cells that span multiple columns or rows of the table are
@@ -4527,7 +4527,7 @@ It is possible for a multiline table to have just one row, but the row
 should be followed by a blank line (and then the row of dashes that ends
 the table), or the table may be interpreted as a simple table.
 
-#### Extension: `grid_tables` ####
+### Extension: `grid_tables` ###
 
 Grid tables look like this:
 
@@ -4607,7 +4607,7 @@ The foot must always be placed at the very bottom of the table.
 Grid tables can be created easily using Emacs' table-mode
 (`M-x table-insert`).
 
-#### Extension: `pipe_tables` ####
+### Extension: `pipe_tables` ###
 
 Pipe tables look like this:
 
@@ -4663,7 +4663,7 @@ you'll need to add colons as above.
 
 ## Metadata blocks
 
-#### Extension: `pandoc_title_block` ####
+### Extension: `pandoc_title_block` ###
 
 If the file begins with a title block
 
@@ -4751,7 +4751,7 @@ will also have "Pandoc User Manuals" in the footer.
 
 will also have "Version 4.0" in the header.
 
-#### Extension: `yaml_metadata_block` ####
+### Extension: `yaml_metadata_block` ###
 
 A [YAML] metadata block is a valid YAML object, delimited by a line of three
 hyphens (`---`) at the top and a line of three hyphens (`---`) or three dots
@@ -4884,7 +4884,7 @@ following restrictions apply:
 
 ## Backslash escapes
 
-#### Extension: `all_symbols_escapable` ####
+### Extension: `all_symbols_escapable` ###
 
 Except inside a code block or inline code, any punctuation or space
 character preceded by a backslash will be treated literally, even if it
@@ -4941,7 +4941,7 @@ will not trigger emphasis:
 
     This is * not emphasized *, and \*neither is this\*.
 
-#### Extension: `intraword_underscores` ####
+### Extension: `intraword_underscores` ###
 
 Because `_` is sometimes used inside words and identifiers,
 pandoc does not interpret a `_` surrounded by alphanumeric
@@ -4952,7 +4952,7 @@ just part of a word, use `*`:
 
 ### Strikeout ###
 
-#### Extension: `strikeout` ####
+### Extension: `strikeout` ###
 
 To strike out a section of text with a horizontal line, begin and end it
 with `~~`. Thus, for example,
@@ -4962,7 +4962,7 @@ with `~~`. Thus, for example,
 
 ### Superscripts and subscripts ###
 
-#### Extension: `superscript`, `subscript` ####
+### Extension: `superscript`, `subscript` ###
 
 Superscripts may be written by surrounding the superscripted text by `^`
 characters; subscripts may be written by surrounding the subscripted
@@ -5001,7 +5001,7 @@ work in verbatim contexts:
 
     This is a backslash followed by an asterisk: `\*`.
 
-#### Extension: `inline_code_attributes` ####
+### Extension: `inline_code_attributes` ###
 
 Attributes can be attached to verbatim text, just as with
 [fenced code blocks]:
@@ -5051,7 +5051,7 @@ This will work in all output formats that support highlighting.
 
 ## Math
 
-#### Extension: `tex_math_dollars` ####
+### Extension: `tex_math_dollars` ###
 
 Anything between two `$` characters will be treated as TeX math.  The
 opening `$` must have a non-space character immediately to its right,
@@ -5128,7 +5128,7 @@ HTML, Slidy, DZSlides, S5, EPUB
 
 ## Raw HTML
 
-#### Extension: `raw_html` ####
+### Extension: `raw_html` ###
 
 Markdown allows you to insert raw HTML (or DocBook) anywhere in a document
 (except verbatim contexts, where `<`, `>`, and `&` are interpreted
@@ -5149,7 +5149,7 @@ Otherwise, plain-text fallbacks will be used. Note that even if
 `raw_html` is disabled, tables will be rendered with HTML syntax if
 they cannot use pipe syntax.
 
-#### Extension: `markdown_in_html_blocks` ####
+### Extension: `markdown_in_html_blocks` ###
 
 Original Markdown allows you to include HTML "blocks":  blocks
 of HTML between balanced tags that are separated from the surrounding text
@@ -5187,21 +5187,21 @@ Markdown with HTML block elements.  For example, one can surround
 a block of Markdown text with `<div>` tags without preventing it
 from being interpreted as Markdown.
 
-#### Extension: `native_divs` ####
+### Extension: `native_divs` ###
 
 Use native pandoc `Div` blocks for content inside `<div>` tags.
 For the most part this should give the same output as
 `markdown_in_html_blocks`, but it makes it easier to write pandoc
 filters to manipulate groups of blocks.
 
-#### Extension: `native_spans` ####
+### Extension: `native_spans` ###
 
 Use native pandoc `Span` blocks for content inside `<span>` tags.
 For the most part this should give the same output as `raw_html`,
 but it makes it easier to write pandoc filters to manipulate groups
 of inlines.
 
-#### Extension: `raw_tex` ####
+### Extension: `raw_tex` ###
 
 In addition to raw HTML, pandoc allows raw LaTeX, TeX, and ConTeXt to be
 included in a document. Inline TeX commands will be preserved and passed
@@ -5231,7 +5231,7 @@ Emacs Org mode, and ConTeXt.
 
 ### Generic raw attribute ###
 
-#### Extension: `raw_attribute` ####
+### Extension: `raw_attribute` ###
 
 Inline spans and fenced code blocks with a special
 kind of attribute will be parsed as raw content with the
@@ -5274,7 +5274,7 @@ The raw attribute cannot be combined with regular attributes.
 
 ## LaTeX macros
 
-#### Extension: `latex_macros` ####
+### Extension: `latex_macros` ###
 
 When this extension is enabled, pandoc will parse LaTeX
 macro definitions and apply the resulting macros to all LaTeX
@@ -5382,7 +5382,7 @@ though not in most other implementations:
     >
     > [quote]: /foo
 
-#### Extension: `shortcut_reference_links` ####
+### Extension: `shortcut_reference_links` ###
 
 In a *shortcut* reference link, the second pair of brackets may
 be omitted entirely:
@@ -5418,7 +5418,7 @@ The link text will be used as the image's alt text:
 
     [movie reel]: movie.gif
 
-#### Extension: `implicit_figures` ####
+### Extension: `implicit_figures` ###
 
 An image with nonempty alt text, occurring by itself in a
 paragraph, will be rendered as a figure with a caption.  The
@@ -5441,7 +5441,7 @@ Note that in reveal.js slide shows, an image in a paragraph
 by itself that has the `r-stretch` class will fill the screen,
 and the caption and figure tags will be omitted.
 
-#### Extension: `link_attributes` ####
+### Extension: `link_attributes` ###
 
 Attributes can be set on links and images:
 
@@ -5497,7 +5497,7 @@ be used as part of Markdown to create native `Div` and `Span`
 elements in the pandoc AST (as opposed to raw HTML).
 However, there is also nicer syntax available:
 
-#### Extension: `fenced_divs` ####
+### Extension: `fenced_divs` ###
 
 Allow special fenced syntax for native `Div` blocks.  A Div
 starts with a fence containing at least three consecutive
@@ -5541,7 +5541,7 @@ it can be helpful for visual clarity to use fences of different
 lengths to distinguish nested divs from their parents.
 
 
-#### Extension: `bracketed_spans` ####
+### Extension: `bracketed_spans` ###
 
 A bracketed sequence of inlines, as one would use to begin
 a link, will be treated as a `Span` with attributes if it is
@@ -5551,7 +5551,7 @@ followed immediately by attributes:
 
 ## Footnotes
 
-#### Extension: `footnotes` ####
+### Extension: `footnotes` ###
 
 Pandoc's Markdown allows footnotes, using the following syntax:
 
@@ -5584,7 +5584,7 @@ document.  They may appear anywhere except inside other block elements
 separated from surrounding content (including other footnotes)
 by blank lines.
 
-#### Extension: `inline_notes` ####
+### Extension: `inline_notes` ###
 
 Inline footnotes are also allowed (though, unlike regular notes,
 they cannot contain multiple paragraphs).  The syntax is as follows:
@@ -5597,7 +5597,7 @@ Inline and regular footnotes may be mixed freely.
 
 ## Citation syntax
 
-#### Extension: `citations` ####
+### Extension: `citations` ###
 
 To cite a bibliographic item with an identifier foo, use the
 syntax `@foo`.  Normal citations should be included in square
@@ -5706,7 +5706,7 @@ in pandoc, but may be enabled by adding `+EXTENSION` to the format
 name, where `EXTENSION` is the name of the extension.  Thus, for
 example, `markdown+hard_line_breaks` is Markdown with hard line breaks.
 
-#### Extension: `rebase_relative_paths` ####
+### Extension: `rebase_relative_paths` ###
 
 Rewrite relative paths for Markdown links and images, depending
 on the path of the file containing the link or image link.  For
@@ -5737,14 +5737,14 @@ be rewritten relative to the file containing the link
 reference definition, not the file containing the reference link
 or image itself, if these differ.
 
-#### Extension: `mark` ####
+### Extension: `mark` ###
 
 To highlight out a section of text, begin and end it with
 with `==`. Thus, for example,
 
     This ==is deleted text.==
 
-#### Extension: `attributes` ####
+### Extension: `attributes` ###
 
 Allows attributes to be attached to any inline or block-level
 element when parsing `commonmark`.
@@ -5776,50 +5776,50 @@ Note that pandoc's AST does not currently allow attributes
 to be attached to arbitrary elements.  Hence a Span or Div
 container will be added if needed.
 
-#### Extension: `old_dashes` ####
+### Extension: `old_dashes` ###
 
 Selects the pandoc <= 1.8.2.1 behavior for parsing smart dashes:
 `-` before a numeral is an en-dash, and `--` is an em-dash.
 This option only has an effect if `smart` is enabled. It is
 selected automatically for `textile` input.
 
-#### Extension: `angle_brackets_escapable` ####
+### Extension: `angle_brackets_escapable` ###
 
 Allow `<` and `>` to be backslash-escaped, as they can be in
 GitHub flavored Markdown but not original Markdown.  This is
 implied by pandoc's default `all_symbols_escapable`.
 
-#### Extension: `lists_without_preceding_blankline` ####
+### Extension: `lists_without_preceding_blankline` ###
 
 Allow a list to occur right after a paragraph, with no intervening
 blank space.
 
-#### Extension: `four_space_rule` ####
+### Extension: `four_space_rule` ###
 
 Selects the pandoc <= 2.0 behavior for parsing lists, so that
 four spaces indent are needed for list item continuation
 paragraphs.
 
-#### Extension: `spaced_reference_links` ####
+### Extension: `spaced_reference_links` ###
 
 Allow whitespace between the two components of a reference link,
 for example,
 
     [foo] [bar].
 
-#### Extension: `hard_line_breaks` ####
+### Extension: `hard_line_breaks` ###
 
 Causes all newlines within a paragraph to be interpreted as hard line
 breaks instead of spaces.
 
-#### Extension: `ignore_line_breaks` ####
+### Extension: `ignore_line_breaks` ###
 
 Causes newlines within a paragraph to be ignored, rather than being
 treated as spaces or as hard line breaks.  This option is intended for
 use with East Asian languages where spaces are not used between words,
 but text is divided into lines for readability.
 
-#### Extension: `east_asian_line_breaks` ####
+### Extension: `east_asian_line_breaks` ###
 
 Causes newlines within a paragraph to be ignored, rather than
 being treated as spaces or as hard line breaks, when they occur
@@ -5827,11 +5827,11 @@ between two East Asian wide characters.  This is a better choice
 than `ignore_line_breaks` for texts that include a mix of East
 Asian wide characters and other characters.
 
-#### Extension: `emoji` ####
+### Extension: `emoji` ###
 
 Parses textual emojis like `:smile:` as Unicode emoticons.
 
-#### Extension: `tex_math_gfm` ####
+### Extension: `tex_math_gfm` ###
 
 Supports two GitHub-specific formats for math.
 Inline math: ``$`e=mc^2`$``.
@@ -5844,26 +5844,26 @@ e=mc^2
 ```
 ````
 
-#### Extension: `tex_math_single_backslash` ####
+### Extension: `tex_math_single_backslash` ###
 
 Causes anything between `\(` and `\)` to be interpreted as inline
 TeX math, and anything between `\[` and `\]` to be interpreted
 as display TeX math.  Note: a drawback of this extension is that
 it precludes escaping `(` and `[`.
 
-#### Extension: `tex_math_double_backslash` ####
+### Extension: `tex_math_double_backslash` ###
 
 Causes anything between `\\(` and `\\)` to be interpreted as inline
 TeX math, and anything between `\\[` and `\\]` to be interpreted
 as display TeX math.
 
-#### Extension: `markdown_attribute` ####
+### Extension: `markdown_attribute` ###
 
 By default, pandoc interprets material inside block-level tags as Markdown.
 This extension changes the behavior so that Markdown is only parsed
 inside block-level tags if the tags have the attribute `markdown=1`.
 
-#### Extension: `mmd_title_block` ####
+### Extension: `mmd_title_block` ###
 
 Enables a [MultiMarkdown] style title block at the top of
 the document, for example:
@@ -5878,7 +5878,7 @@ See the MultiMarkdown documentation for details.  If `pandoc_title_block` or
 `yaml_metadata_block` is enabled, it will take precedence over
 `mmd_title_block`.
 
-#### Extension: `abbreviations` ####
+### Extension: `abbreviations` ###
 
 Parses PHP Markdown Extra abbreviation keys, like
 
@@ -5888,7 +5888,7 @@ Note that the pandoc document model does not support
 abbreviations, so if this extension is enabled, abbreviation keys are
 simply skipped (as opposed to being parsed as paragraphs).
 
-#### Extension: `alerts` ####
+### Extension: `alerts` ###
 
 Supports [GitHub-style Markdown alerts], like
 
@@ -5897,12 +5897,12 @@ Supports [GitHub-style Markdown alerts], like
 
   [GitHub-style Markdown alerts]: https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#alerts
 
-#### Extension: `autolink_bare_uris` ####
+### Extension: `autolink_bare_uris` ###
 
 Makes all absolute URIs into links, even when not surrounded by
 pointy braces `<...>`.
 
-#### Extension: `mmd_link_attributes` ####
+### Extension: `mmd_link_attributes` ###
 
 Parses MultiMarkdown-style key-value attributes on link
 and image references. This extension should not be confused with the
@@ -5913,12 +5913,12 @@ and image references. This extension should not be confused with the
     [ref]: https://path.to/image "Image title" width=20px height=30px
            id=myId class="myClass1 myClass2"
 
-#### Extension: `mmd_header_identifiers` ####
+### Extension: `mmd_header_identifiers` ###
 
 Parses MultiMarkdown-style heading identifiers (in square brackets,
 after the heading but before any trailing `#`s in an ATX heading).
 
-#### Extension: `compact_definition_lists` ####
+### Extension: `compact_definition_lists` ###
 
 Activates the definition list syntax of pandoc 1.12.x and earlier.
 This syntax differs from the one described above under [Definition lists]
@@ -5945,7 +5945,7 @@ in several respects:
     we must either disallow lazy wrapping or require a blank line between
     list items.
 
-#### Extension: `gutenberg` ####
+### Extension: `gutenberg` ###
 
 Use [Project Gutenberg] conventions for `plain` output:
 all-caps for strong emphasis, surround by underscores
@@ -5953,14 +5953,14 @@ for regular emphasis, add extra blank space around headings.
 
   [Project Gutenberg]: https://www.gutenberg.org
 
-#### Extension: `sourcepos` ####
+### Extension: `sourcepos` ###
 
 Include source position attributes when parsing `commonmark`.
 For elements that accept attributes, a `data-pos` attribute
 is added; other elements are placed in a surrounding
 Div or Span element with a `data-pos` attribute.
 
-#### Extension: `short_subsuperscripts` ####
+### Extension: `short_subsuperscripts` ###
 
 Parse MultiMarkdown-style subscripts and superscripts, which start with
 a '~' or '^' character, respectively, and include the alphanumeric sequence
@@ -5972,7 +5972,7 @@ or
 
     Oxygen is O~2.
 
-#### Extension: `wikilinks_title_after_pipe` ####
+### Extension: `wikilinks_title_after_pipe` ###
 
 Pandoc supports multiple Markdown wikilink syntaxes, regardless of
 whether the title is before or after the pipe.