@@ -480,7 +480,7 @@ Reader options {.options}
480480
481481`--base-header-level=`*NUMBER*
482482
483−: Specify the base level for headers (defaults to 1).
483+: Specify the base level for headings (defaults to 1).
484484
485485`--strip-empty-paragraphs`
486486
@@ -754,8 +754,8 @@ General writer options {.options}
754754`--toc-depth=`*NUMBER*
755755
756756: Specify the number of section levels to include in the table
757− of contents. The default is 3 (which means that level 1, 2, and 3
758− headers will be listed in the contents).
757+ of contents. The default is 3 (which means that level-1, 2, and 3
758+ headings will be listed in the contents).
759759
760760`--strip-comments`
761761
@@ -907,23 +907,23 @@ Options affecting specific writers {.options}
907907
908908`--atx-headers`
909909
910−: Use ATX-style headers in Markdown output. The default is
911− to use setext-style headers for levels 1-2, and then ATX headers.
912− (Note: for `gfm` output, ATX headers are always used.)
910+: Use ATX-style headings in Markdown output. The default is
911+ to use setext-style headings for levels 1 to 2, and then ATX headings.
912+ (Note: for `gfm` output, ATX headings are always used.)
913913 This option also affects markdown cells in `ipynb` output.
914914
915915`--top-level-division=[default|section|chapter|part]`
916916
917−: Treat top-level headers as the given division type in LaTeX, ConTeXt,
917+: Treat top-level headings as the given division type in LaTeX, ConTeXt,
918918 DocBook, and TEI output. The hierarchy order is part, chapter, then section;
919− all headers are shifted such that the top-level header becomes the specified
919+ all headings are shifted such that the top-level heading becomes the specified
920920 type. The default behavior is to determine the best division type via
921921 heuristics: unless other conditions apply, `section` is chosen. When the
922922 LaTeX document class is set to `report`, `book`, or `memoir` (unless the
923923 `article` option is specified), `chapter` is implied as the setting for this
924924 option. If `beamer` is the output format, specifying either `chapter` or
925− `part` will cause top-level headers to become `\part{..}`, while
926− second-level headers remain as their default type.
925+ `part` will cause top-level headings to become `\part{..}`, while
926+ second-level headings remain as their default type.
927927
928928`-N`, `--number-sections`
929929
@@ -936,10 +936,10 @@ Options affecting specific writers {.options}
936936
937937: Offset for section headings in HTML output (ignored in other
938938 output formats). The first number is added to the section number for
939− top-level headers, the second for second-level headers, and so on.
940− So, for example, if you want the first top-level header in your
939+ top-level headings, the second for second-level headings, and so on.
940+ So, for example, if you want the first top-level heading in your
941941 document to be numbered "6", specify `--number-offset=5`.
942− If your document starts with a level-2 header which you want to
942+ If your document starts with a level-2 heading which you want to
943943 be numbered "1.5", specify `--number-offset=1,4`.
944944 Offsets are 0 by default. Implies `--number-sections`.
945945
@@ -957,12 +957,12 @@ Options affecting specific writers {.options}
957957
958958`--slide-level=`*NUMBER*
959959
960−: Specifies that headers with the specified level create
961− slides (for `beamer`, `s5`, `slidy`, `slideous`, `dzslides`). Headers
960+: Specifies that headings with the specified level create
961+ slides (for `beamer`, `s5`, `slidy`, `slideous`, `dzslides`). Headings
962962 above this level in the hierarchy are used to divide the
963− slide show into sections; headers below this level create
963+ slide show into sections; headings below this level create
964964 subheads within a slide. Note that content that is
965− not contained under slide-level headers will not appear in
965+ not contained under slide-level headings will not appear in
966966 the slide show. The default is to set the slide level based
967967 on the contents of the document; see [Structuring the slide
968968 show].
@@ -971,8 +971,8 @@ Options affecting specific writers {.options}
971971
972972: Wrap sections in `<section>` tags (or `<div>` tags for `html4`),
973973 and attach identifiers to the enclosing `<section>` (or `<div>`)
974− rather than the header itself. See
975− [Header identifiers], below.
974+ rather than the heading itself. See
975+ [Heading identifiers], below.
976976
977977`--email-obfuscation=none`|`javascript`|`references`
978978
@@ -1098,8 +1098,8 @@ Options affecting specific writers {.options}
10981098 `.pptx` or `.potx` extension) are known to work, as are most
10991099 templates derived from these.
11001100
1101− The specific requirement is that the template should contain
1102− the following four layouts as its first four layouts:
1101+ The specific requirement is that the template should begin with
1102+ the following first four layouts:
11031103
11041104 1. Title Slide
11051105 2. Title and Content
@@ -1182,12 +1182,12 @@ Options affecting specific writers {.options}
11821182
11831183`--epub-chapter-level=`*NUMBER*
11841184
1185−: Specify the header level at which to split the EPUB into separate
1186− "chapter" files. The default is to split into chapters at level 1
1187− headers. This option only affects the internal composition of the
1185+: Specify the heading level at which to split the EPUB into separate
1186+ "chapter" files. The default is to split into chapters at level-1
1187+ headings. This option only affects the internal composition of the
11881188 EPUB, not the way chapters and sections are displayed to users. Some
11891189 readers may be slow if the chapter files are too large, so for large
1190− documents with few level 1 headers, one might want to use a chapter
1190+ documents with few level-1 headings, one might want to use a chapter
11911191 level of 2 or 3.
11921192
11931193`--epub-subdirectory=`*DIRNAME*
@@ -2039,13 +2039,13 @@ literally. In writing LaTeX, enabling `smart` tells pandoc
20392039to use the ligatures when possible; if `smart` is disabled
20402040pandoc will use unicode quotation mark and dash characters.
20412041
2042−Headers and sections
2043−--------------------
2042+Headings and sections
2043+---------------------
20442044
20452045#### Extension: `auto_identifiers` ####
20462046
2047−A header without an explicitly specified identifier will be
2048−automatically assigned a unique identifier based on the header text.
2047+A heading without an explicitly specified identifier will be
2048+automatically assigned a unique identifier based on the heading text.
20492049
20502050This extension can be enabled/disabled for the following formats:
20512051
@@ -2059,7 +2059,7 @@ enabled by default in
20592059: `markdown`, `muse`
20602060
20612061The default algorithm used to derive the identifier from the
2062−header text is:
2062+heading text is:
20632063
20642064 - Remove all formatting, links, etc.
20652065 - Remove all footnotes.
@@ -2073,9 +2073,9 @@ header text is:
20732073
20742074Thus, for example,
20752075
2076− Header Identifier
2076+ Heading Identifier
20772077 ------------------------------- ----------------------------
2078− `Header identifiers in HTML` `header-identifiers-in-html`
2078+ `Heading identifiers in HTML` `heading-identifiers-in-html`
20792079 `Maître d'hôtel` `maître-dhôtel`
20802080 `*Dogs*?--in *my* house?` `dogs--in-my-house`
20812081 `[HTML], [S5], or [RTF]?` `html-s5-or-rtf`
@@ -2083,7 +2083,7 @@ Thus, for example,
20832083 `33` `section`
20842084
20852085These rules should, in most cases, allow one to determine the identifier
2086−from the header text. The exception is when several headers have the
2086+from the heading text. The exception is when several headings have the
20872087same text; in this case, the first will get an identifier as described
20882088above; the second will get the same identifier with `-1` appended; the
20892089third with `-2`; and so on.
@@ -2097,7 +2097,7 @@ also make it easy to provide links from one section of a document to
20972097another. A link to this section, for example, might look like this:
20982098
20992099 See the section on
2100− [header identifiers](#header-identifiers-in-html-latex-and-context).
2100+ [heading identifiers](#heading-identifiers-in-html-latex-and-context).
21012101
21022102Note, however, that this method of providing links to sections works
21032103only in HTML, LaTeX, and ConTeXt formats.
@@ -2105,7 +2105,7 @@ only in HTML, LaTeX, and ConTeXt formats.
21052105If the `--section-divs` option is specified, then each section will
21062106be wrapped in a `section` (or a `div`, if `html4` was specified),
21072107and the identifier will be attached to the enclosing `<section>`
2108−(or `<div>`) tag rather than the header itself. This allows entire
2108+(or `<div>`) tag rather than the heading itself. This allows entire
21092109sections to be manipulated using JavaScript or treated differently in
21102110CSS.
21112111
@@ -2206,12 +2206,12 @@ This means that
22062206 - In Markdown input, "bird track" sections will be parsed as Haskell
22072207 code rather than block quotations. Text between `\begin{code}`
22082208 and `\end{code}` will also be treated as Haskell code. For
2209− ATX-style headers the character '=' will be used instead of '#'.
2209+ ATX-style headings the character '=' will be used instead of '#'.
22102210
22112211 - In Markdown output, code blocks with classes `haskell` and `literate`
22122212 will be rendered using bird tracks, and block quotations will be
22132213 indented one space, so they will not be treated as Haskell code.
2214− In addition, headers will be rendered setext-style (with underlines)
2214+ In addition, headings will be rendered setext-style (with underlines)
22152215 rather than ATX-style (with '#' characters). (This is because ghc
22162216 treats '#' characters in column 1 as introducing line numbers.)
22172217
@@ -2339,43 +2339,43 @@ Note: in multiline and grid table cells, this is the only way
23392339to create a hard line break, since trailing spaces in the cells
23402340are ignored.
23412341
2342−Headers
2343−-------
2342+Headings
2343+--------
23442344
2345−There are two kinds of headers: Setext and ATX.
2345+There are two kinds of headings: Setext and ATX.
23462346
2347−### Setext-style headers ###
2347+### Setext-style headings ###
23482348
2349−A setext-style header is a line of text "underlined" with a row of `=` signs
2350−(for a level one header) or `-` signs (for a level two header):
2349+A setext-style heading is a line of text "underlined" with a row of `=` signs
2350+(for a level-one heading) or `-` signs (for a level-two heading):
23512351
2352− A level-one header
2353− ==================
2352+ A level-one heading
2353+ ===================
23542354
2355− A level-two header
2356− ------------------
2355+ A level-two heading
2356+ -------------------
23572357
2358−The header text can contain inline formatting, such as emphasis (see
2358+The heading text can contain inline formatting, such as emphasis (see
23592359[Inline formatting], below).
23602360
23612361
2362−### ATX-style headers ###
2362+### ATX-style headings ###
23632363
2364−An ATX-style header consists of one to six `#` signs and a line of
2364+An ATX-style heading consists of one to six `#` signs and a line of
23652365text, optionally followed by any number of `#` signs. The number of
2366−`#` signs at the beginning of the line is the header level:
2366+`#` signs at the beginning of the line is the heading level:
23672367
2368− ## A level-two header
2368+ ## A level-two heading
23692369
2370− ### A level-three header ###
2370+ ### A level-three heading ###
23712371
2372−As with setext-style headers, the header text can contain formatting:
2372+As with setext-style headings, the heading text can contain formatting:
23732373
2374− # A level-one header with a [link](/url) and *emphasis*
2374+ # A level-one heading with a [link](/url) and *emphasis*
23752375
23762376#### Extension: `blank_before_header` ####
23772377
2378−Standard Markdown syntax does not require a blank line before a header.
2378+Standard Markdown syntax does not require a blank line before a heading.
23792379Pandoc does require this (except, of course, at the beginning of the
23802380document). The reason for the requirement is that it is all too easy for a
23812381`#` to end up at the beginning of a line by accident (perhaps through line
@@ -2387,29 +2387,29 @@ wrapping). Consider, for example:
23872387#### Extension: `space_in_atx_header` ####
23882388
23892389Many Markdown implementations do not require a space between the
2390−opening `#`s of an ATX header and the header text, so that
2391−`#5 bolt` and `#hashtag` count as headers. With this extension,
2390+opening `#`s of an ATX heading and the heading text, so that
2391+`#5 bolt` and `#hashtag` count as headings. With this extension,
23922392pandoc does require the space.
23932393
2394−### Header identifiers ###
2394+### Heading identifiers ###
23952395
23962396See also the [`auto_identifiers` extension](#extension-auto_identifiers) above.
23972397
23982398#### Extension: `header_attributes` ####
23992399
2400−Headers can be assigned attributes using this syntax at the end
2401−of the line containing the header text:
2400+Headings can be assigned attributes using this syntax at the end
2401+of the line containing the heading text:
24022402
24032403 {#identifier .class .class key=value key=value}
24042404
2405−Thus, for example, the following headers will all be assigned the identifier
2405+Thus, for example, the following headings will all be assigned the identifier
24062406`foo`:
24072407
2408− # My header {#foo}
2408+ # My heading {#foo}
24092409
2410− ## My header ## {#foo}
2410+ ## My heading ## {#foo}
24112411
2412− My other header {#foo}
2412+ My other heading {#foo}
24132413 ---------------
24142414
24152415(This syntax is compatible with [PHP Markdown Extra].)
@@ -2420,49 +2420,49 @@ classes, and key/value attributes are used in HTML and HTML-based formats such
24202420as EPUB and slidy. Identifiers are used for labels and link anchors in the
24212421LaTeX, ConTeXt, Textile, and AsciiDoc writers.
24222422
2423−Headers with the class `unnumbered` will not be numbered, even if
2423+Headings with the class `unnumbered` will not be numbered, even if
24242424`--number-sections` is specified. A single hyphen (`-`) in an attribute
24252425context is equivalent to `.unnumbered`, and preferable in non-English
24262426documents. So,
24272427
2428− # My header {-}
2428+ # My heading {-}
24292429
24302430is just the same as
24312431
2432− # My header {.unnumbered}
2432+ # My heading {.unnumbered}
24332433
24342434#### Extension: `implicit_header_references` ####
24352435
2436−Pandoc behaves as if reference links have been defined for each header.
2437−So, to link to a header
2436+Pandoc behaves as if reference links have been defined for each heading.
2437+So, to link to a heading
24382438
2439− # Header identifiers in HTML
2439+ # Heading identifiers in HTML
24402440
24412441you can simply write
24422442
2443− [Header identifiers in HTML]
2443+ [Heading identifiers in HTML]
24442444
24452445or
24462446
2447− [Header identifiers in HTML][]
2447+ [Heading identifiers in HTML][]
24482448
24492449or
24502450
2451− [the section on header identifiers][header identifiers in
2451+ [the section on heading identifiers][heading identifiers in
24522452 HTML]
24532453
24542454instead of giving the identifier explicitly:
24552455
2456− [Header identifiers in HTML](#header-identifiers-in-html)
2456+ [Heading identifiers in HTML](#heading-identifiers-in-html)
24572457
2458−If there are multiple headers with identical text, the corresponding
2458+If there are multiple headings with identical text, the corresponding
24592459reference will link to the first one only, and you will need to use explicit
24602460links to link to the others, as described above.
24612461
24622462Like regular reference links, these references are case-insensitive.
24632463
24642464Explicit link reference definitions always take priority over
2465−implicit header references. So, in the following example, the
2465+implicit heading references. So, in the following example, the
24662466link will point to `bar`, not to `#foo`:
24672467
24682468 # Foo
@@ -2476,7 +2476,7 @@ Block quotations
24762476
24772477Markdown uses email conventions for quoting blocks of text.
24782478A block quotation is one or more paragraphs or other block elements
2479−(such as lists or headers), with each line preceded by a `>` character
2479+(such as lists or headings), with each line preceded by a `>` character
24802480and an optional space. (The `>` need not start at the left margin, but
24812481it should not be indented more than three spaces.)
24822482
@@ -3027,7 +3027,7 @@ Simple tables look like this:
30273027
30283028 Table: Demonstration of simple table syntax.
30293029
3030−The headers and table rows must each fit on one line. Column
3030+The header and table rows must each fit on one line. Column
30313031alignments are determined by the position of the header text relative
30323032to the dashed line below it:[^4]
30333033
@@ -3046,7 +3046,7 @@ to the dashed line below it:[^4]
30463046The table must end with a blank line, or a line of dashes followed by
30473047a blank line.
30483048
3049−The column headers may be omitted, provided a dashed line is used
3049+The column header row may be omitted, provided a dashed line is used
30503050to end the table. For example:
30513051
30523052 ------- ------ ---------- -------
@@ -3055,13 +3055,13 @@ to end the table. For example:
30553055 1 1 1 1
30563056 ------- ------ ---------- -------
30573057
3058−When headers are omitted, column alignments are determined on the basis
3058+When the header row is omitted, column alignments are determined on the basis
30593059of the first line of the table body. So, in the tables above, the columns
30603060would be right, left, center, and right aligned, respectively.
30613061
30623062#### Extension: `multiline_tables` ####
30633063
3064−Multiline tables allow headers and table rows to span multiple lines
3064+Multiline tables allow header and table rows to span multiple lines
30653065of text (but cells that span multiple columns or rows of the table are
30663066not supported). Here is an example:
30673067
@@ -3083,7 +3083,7 @@ not supported). Here is an example:
30833083These work like simple tables, but with the following differences:
30843084
30853085 - They must begin with a row of dashes, before the header text
3086− (unless the headers are omitted).
3086+ (unless the header row is omitted).
30873087 - They must end with a row of dashes, then a blank line.
30883088 - The rows must be separated by blank lines.
30893089
@@ -3092,7 +3092,7 @@ the columns, and the writers try to reproduce these relative widths in
30923092the output. So, if you find that one of the columns is too narrow in the
30933093output, try widening it in the Markdown source.
30943094
3095−Headers may be omitted in multiline tables as well as simple tables:
3095+The header may be omitted in multiline tables as well as simple tables:
30963096
30973097 ----------- ------- --------------- -------------------------
30983098 First row 12.0 Example of a row that
@@ -3103,7 +3103,7 @@ Headers may be omitted in multiline tables as well as simple tables:
31033103 rows.
31043104 ----------- ------- --------------- -------------------------
31053105
3106− : Here's a multiline table without headers.
3106+ : Here's a multiline table without a header.
31073107
31083108It is possible for a multiline table to have just one row, but the row
31093109should be followed by a blank line (and then the row of dashes that ends
@@ -3879,7 +3879,7 @@ be omitted entirely:
38793879### Internal links ###
38803880
38813881To link to another section of the same document, use the automatically
3882−generated identifier (see [Header identifiers]). For example:
3882+generated identifier (see [Heading identifiers]). For example:
38833883
38843884 See the [Introduction](#introduction).
38853885
@@ -4236,8 +4236,8 @@ Otherwise, it will be placed at the end of the document.
42364236Generation of the bibliography can be suppressed by setting
42374237`suppress-bibliography: true` in the YAML metadata.
42384238
4239−If you wish the bibliography to have a section header, you can
4240−set `reference-section-title` in the metadata, or put the header
4239+If you wish the bibliography to have a section heading, you can
4240+set `reference-section-title` in the metadata, or put the heading
42414241at the beginning of the div with id `refs` (if you are using it)
42424242or at the end of your document:
42434243
@@ -4245,8 +4245,8 @@ or at the end of your document:
42454245
42464246 # References
42474247
4248−The bibliography will be inserted after this header. Note that
4249−the `unnumbered` class will be added to this header, so that the
4248+The bibliography will be inserted after this heading. Note that
4249+the `unnumbered` class will be added to this heading, so that the
42504250section will not be numbered.
42514251
42524252If you want to include items in the bibliography without actually
@@ -4414,8 +4414,8 @@ and image references. This extension should not be confused with the
44144414
44154415#### Extension: `mmd_header_identifiers` ####
44164416
4417−Parses multimarkdown style header identifiers (in square brackets,
4418−after the header but before any trailing `#`s in an ATX header).
4417+Parses multimarkdown style heading identifiers (in square brackets,
4418+after the heading but before any trailing `#`s in an ATX heading).
44194419
44204420#### Extension: `compact_definition_lists` ####
44214421
@@ -4572,11 +4572,11 @@ To produce a Powerpoint slide show, type
45724572Structuring the slide show
45734573--------------------------
45744574
4575−By default, the *slide level* is the highest header level in
4575+By default, the *slide level* is the highest heading level in
45764576the hierarchy that is followed immediately by content, and not another
4577−header, somewhere in the document. In the example above, level 1 headers
4578−are always followed by level 2 headers, which are followed by content,
4579−so 2 is the slide level. This default can be overridden using
4577+heading, somewhere in the document. In the example above, level-1 headings
4578+are always followed by level-2 headings, which are followed by content,
4579+so the slide level is 2. This default can be overridden using
45804580the `--slide-level` option.
45814581
45824582The document is carved up into slides according to the following
@@ -4584,15 +4584,15 @@ rules:
45844584
45854585 * A horizontal rule always starts a new slide.
45864586
4587− * A header at the slide level always starts a new slide.
4587+ * A heading at the slide level always starts a new slide.
45884588
4589− * Headers *below* the slide level in the hierarchy create
4590− headers *within* a slide.
4589+ * Headings *below* the slide level in the hierarchy create
4590+ headings *within* a slide.
45914591
4592− * Headers *above* the slide level in the hierarchy create
4592+ * Headings *above* the slide level in the hierarchy create
45934593 "title slides," which just contain the section title
45944594 and help to break the slide show into sections.
4595− Non-slide content under these headers will be included
4595+ Non-slide content under these headings will be included
45964596 on the title slide (for HTML slide shows) or in a
45974597 subsequent slide with the same title (for beamer).
45984598
@@ -4602,13 +4602,13 @@ rules:
46024602
46034603These rules are designed to support many different styles of slide show. If
46044604you don't care about structuring your slides into sections and subsections,
4605−you can just use level 1 headers for all each slide. (In that case, level 1
4605+you can just use level-1 headings for all each slide. (In that case, level-1
46064606will be the slide level.) But you can also structure the slide show into
46074607sections, as in the example above.
46084608
46094609Note: in reveal.js slide shows, if slide level is 2, a two-dimensional
4610−layout will be produced, with level 1 headers building horizontally
4611−and level 2 headers building vertically. It is not recommended that
4610+layout will be produced, with level-1 headings building horizontally
4611+and level-2 headings building vertically. It is not recommended that
46124612you use deeper nesting of section levels with reveal.js.
46134613
46144614Incremental lists
@@ -4690,9 +4690,9 @@ To style beamer slides, you can specify a `theme`, `colortheme`,
46904690
46914691 pandoc -t beamer habits.txt -V theme:Warsaw -o habits.pdf
46924692
4693−Note that header attributes will turn into slide attributes
4693+Note that heading attributes will turn into slide attributes
46944694(on a `<div>` or `<section>`) in HTML slide formats, allowing you
4695−to style individual slides. In beamer, the only header attribute
4695+to style individual slides. In beamer, the only heading attribute
46964696that affects slides is the `allowframebreaks` class, which sets the
46974697`allowframebreaks` option, causing multiple slides to be created
46984698if the content overfills the frame. This is recommended especially for
@@ -4743,7 +4743,7 @@ Frame attributes in beamer
47434743
47444744Sometimes it is necessary to add the LaTeX `[fragile]` option to
47454745a frame in beamer (for example, when using the `minted` environment).
4746−This can be forced by adding the `fragile` class to the header
4746+This can be forced by adding the `fragile` class to the heading
47474747introducing the slide:
47484748
47494749 # Fragile slide {.fragile}
@@ -4771,7 +4771,7 @@ and `parallaxBackgroundVertical` the same way and must also set
47714771
47724772To set an image for a particular reveal.js slide, add
47734773`{data-background-image="/path/to/image"}`
4774−to the first slide-level header on the slide (which may even be empty).
4774+to the first slide-level heading on the slide (which may even be empty).
47754775
47764776In reveal.js's overview mode, the parallaxBackgroundImage will show up
47774777only on the first slide.
@@ -4798,7 +4798,7 @@ Slide 1 has background_image.png as its background.
47984798
47994799## {data-background-image="/path/to/special_image.jpg"}
48004800
4801−Slide 2 has a special image for its background, even though the header has no content.
4801+Slide 2 has a special image for its background, even though the heading has no content.
48024802```
48034803
48044804Creating EPUBs with pandoc
@@ -4910,7 +4910,7 @@ The following fields are recognized:
49104910The `epub:type` attribute
49114911-------------------------
49124912
4913−For `epub3` output, you can mark up the header that corresponds to an EPUB
4913+For `epub3` output, you can mark up the heading that corresponds to an EPUB
49144914chapter using the [`epub:type` attribute][epub-type]. For example, to set
49154915the attribute to the value `prologue`, use this markdown:
49164916
@@ -5086,7 +5086,7 @@ Note that options and extensions that affect reading and
50865086writing of Markdown will also affect Markdown cells in ipynb
50875087notebooks. For example, `--wrap=preserve` will preserve
50885088soft line breaks in Markdown cells; `--atx-headers` will
5089−cause ATX style headers to be used; and `--preserve-tabs` will
5089+cause ATX-style headings to be used; and `--preserve-tabs` will
50905090prevent tabs from being turned to spaces.
50915091
50925092Syntax highlighting
@@ -5274,7 +5274,7 @@ application, here are some things to keep in mind:
52745274 If `raw_html` is enabled for the Markdown input, users can
52755275 inject arbitrary HTML. Even if `raw_html` is disabled,
52765276 users can include dangerous content in attributes for
5277− headers, spans, and code blocks. To be safe, you should
5277+ headings, spans, and code blocks. To be safe, you should
52785278 run all the generated HTML through an HTML sanitizer.
52795279
52805280Authors