@@ -26,32 +26,32 @@ markup], [Haddock markup], [OPML], [Emacs Org mode], [DocBook],
2626[reveal.js] or [S5] HTML slide shows. It can also produce [PDF] output
2727on systems where LaTeX or ConTeXt is installed.
2828
29−Pandoc's enhanced version of markdown includes syntax for [footnotes],
29+Pandoc's enhanced version of Markdown includes syntax for [footnotes],
3030[tables], flexible [ordered lists], [definition lists], [fenced code blocks],
3131[superscripts and subscripts], [strikeout], [metadata blocks], automatic tables of
32−contents, [embedded LaTeX math][Math rendering in HTML], [citations], and [markdown inside HTML block
32+contents, [embedded LaTeX math][Math rendering in HTML], [citations], and [Markdown inside HTML block
3333elements][Extension: `markdown_in_html_blocks`]. (These enhancements, described below under
34−[Pandoc's markdown], can be disabled using the
34+[Pandoc's Markdown], can be disabled using the
3535`markdown_strict` input or output format.)
3636
37−In contrast to most existing tools for converting markdown to HTML, which
38−use regex substitutions, Pandoc has a modular design: it consists of a
37+In contrast to most existing tools for converting Markdown to HTML, which
38+use regex substitutions, pandoc has a modular design: it consists of a
3939set of readers, which parse text in a given format and produce a native
4040representation of the document, and a set of writers, which convert
4141this native representation into a target format. Thus, adding an input
4242or output format requires only adding a reader or writer.
4343
44−Because Pandoc's intermediate representation of a document is less
44+Because pandoc's intermediate representation of a document is less
4545expressive than many of the formats it converts between, one should
4646not expect perfect conversions between every format and every other.
4747Pandoc attempts to preserve the structural elements of a document, but
4848not formatting details such as margin size. And some document elements,
49−such as complex tables, may not fit into Pandoc's simple document
50−model. While conversions from Pandoc's Markdown to all formats aspire
51−to be perfect, conversions from formats more expressive than Pandoc's
49+such as complex tables, may not fit into pandoc's simple document
50+model. While conversions from pandoc's Markdown to all formats aspire
51+to be perfect, conversions from formats more expressive than pandoc's
5252Markdown can be expected to be lossy.
5353
54−[markdown]: http://daringfireball.net/projects/markdown/
54+[Markdown]: http://daringfireball.net/projects/markdown/
5555[CommonMark]: http://commonmark.org
5656[PHP Markdown Extra]: https://michelf.ca/projects/php-markdown/extra/
5757[GitHub-Flavored Markdown]: https://help.github.com/articles/github-flavored-markdown/
@@ -124,11 +124,11 @@ The format of the input and output can be specified explicitly using
124124command-line options. The input format can be specified using the
125125`-r/--read` or `-f/--from` options, the output format using the
126126`-w/--write` or `-t/--to` options. Thus, to convert `hello.txt` from
127−markdown to LaTeX, you could type:
127+Markdown to LaTeX, you could type:
128128
129129 pandoc -f markdown -t latex hello.txt
130130
131−To convert `hello.html` from HTML to markdown:
131+To convert `hello.html` from HTML to Markdown:
132132
133133 pandoc -f html -t markdown hello.html
134134
@@ -143,12 +143,12 @@ the input and output filenames. Thus, for example,
143143
144144 pandoc -o hello.tex hello.txt
145145
146−will convert `hello.txt` from markdown to LaTeX. If no output file
146+will convert `hello.txt` from Markdown to LaTeX. If no output file
147147is specified (so that output goes to *stdout*), or if the output file's
148148extension is unknown, the output format will default to HTML.
149149If no input file is specified (so that input comes from *stdin*), or
150150if the input files' extensions are unknown, the input format will
151−be assumed to be markdown unless explicitly specified.
151+be assumed to be Markdown unless explicitly specified.
152152
153153Pandoc uses the UTF-8 character encoding for both input and output.
154154If your local character encoding is not UTF-8, you
@@ -252,10 +252,10 @@ General options
252252
253253: Specify input format. *FORMAT* can be `native` (native Haskell),
254254 `json` (JSON version of native AST), `markdown` (pandoc's
255− extended markdown), `markdown_strict` (original unextended
256− markdown), `markdown_phpextra` (PHP Markdown Extra),
255+ extended Markdown), `markdown_strict` (original unextended
256+ Markdown), `markdown_phpextra` (PHP Markdown Extra),
257257 `markdown_github` (GitHub-Flavored Markdown),
258− `commonmark` (CommonMark markdown), `textile` (Textile), `rst`
258+ `commonmark` (CommonMark Markdown), `textile` (Textile), `rst`
259259 (reStructuredText), `html` (HTML), `docbook` (DocBook), `t2t`
260260 (txt2tags), `docx` (docx), `odt` (ODT), `epub` (EPUB), `opml` (OPML),
261261 `org` (Emacs Org mode), `mediawiki` (MediaWiki markup), `twiki` (TWiki
@@ -266,20 +266,20 @@ General options
266266 syntax extensions can be individually enabled or disabled by
267267 appending `+EXTENSION` or `-EXTENSION` to the format name. So, for
268268 example, `markdown_strict+footnotes+definition_lists` is strict
269− markdown with footnotes and definition lists enabled, and
270− `markdown-pipe_tables+hard_line_breaks` is pandoc's markdown
269+ Markdown with footnotes and definition lists enabled, and
270+ `markdown-pipe_tables+hard_line_breaks` is pandoc's Markdown
271271 without pipe tables and with hard line breaks. See [Pandoc's
272− markdown], below, for a list of extensions and
272+ Markdown], below, for a list of extensions and
273273 their names.
274274
275275`-t` *FORMAT*, `-w` *FORMAT*, `--to=`*FORMAT*, `--write=`*FORMAT*
276276
277277: Specify output format. *FORMAT* can be `native` (native Haskell),
278278 `json` (JSON version of native AST), `plain` (plain text),
279− `markdown` (pandoc's extended markdown), `markdown_strict`
280− (original unextended markdown), `markdown_phpextra` (PHP Markdown
279+ `markdown` (pandoc's extended Markdown), `markdown_strict`
280+ (original unextended Markdown), `markdown_phpextra` (PHP Markdown
281281 Extra), `markdown_github` (GitHub-Flavored
282− Markdown), `commonmark` (CommonMark markdown), `rst`
282+ Markdown), `commonmark` (CommonMark Markdown), `rst`
283283 (reStructuredText), `html` (XHTML), `html5` (HTML5), `latex`
284284 (LaTeX), `beamer` (LaTeX beamer slide show), `context` (ConTeXt),
285285 `man` (groff man), `mediawiki` (MediaWiki markup), `dokuwiki`
@@ -360,9 +360,9 @@ Reader options
360360
361361: Parse untranslatable HTML codes and LaTeX environments as raw HTML
362362 or LaTeX, instead of ignoring them. Affects only HTML and LaTeX
363− input. Raw HTML can be printed in markdown, reStructuredText, HTML,
363+ input. Raw HTML can be printed in Markdown, reStructuredText, HTML,
364364 Slidy, Slideous, DZSlides, reveal.js, and S5 output; raw LaTeX
365− can be printed in markdown, reStructuredText, LaTeX, and ConTeXt output.
365+ can be printed in Markdown, reStructuredText, LaTeX, and ConTeXt output.
366366 The default is for the readers to omit untranslatable HTML codes and
367367 LaTeX environments. (The LaTeX reader does pass through untranslatable
368368 LaTeX *commands*, even if `-R` is not specified.)
@@ -397,12 +397,12 @@ Reader options
397397: Specify a default extension to use when image paths/URLs have no
398398 extension. This allows you to use the same source for formats that
399399 require different kinds of images. Currently this option only affects
400− the markdown and LaTeX readers.
400+ the Markdown and LaTeX readers.
401401
402402`--filter=`*EXECUTABLE*
403403
404404: Specify an executable to be used as a filter transforming the
405− Pandoc AST after the input is parsed and before the output is
405+ pandoc AST after the input is parsed and before the output is
406406 written. The executable should read JSON from stdin and write
407407 JSON to stdout. The JSON must be formatted like pandoc's own
408408 JSON input and output. The name of the output format will be
@@ -616,12 +616,12 @@ Options affecting specific writers
616616
617617`--reference-links`
618618
619−: Use reference-style links, rather than inline links, in writing markdown
619+: Use reference-style links, rather than inline links, in writing Markdown
620620 or reStructuredText. By default inline links are used.
621621
622622`--atx-headers`
623623
624−: Use ATX-style headers in markdown and asciidoc output. The default is
624+: Use ATX-style headers in Markdown and asciidoc output. The default is
625625 to use setext-style headers for levels 1-2, and then ATX headers.
626626
627627`--chapters`
@@ -697,7 +697,7 @@ Options affecting specific writers
697697`--id-prefix=`*STRING*
698698
699699: Specify a prefix to be added to all automatically generated identifiers
700− in HTML and DocBook output, and to footnote numbers in markdown output.
700+ in HTML and DocBook output, and to footnote numbers in Markdown output.
701701 This is useful for preventing duplicate identifiers when generating
702702 fragments to be included in other pages.
703703
@@ -754,7 +754,7 @@ Options affecting specific writers
754754
755755: Use the specified image as the EPUB cover. It is recommended
756756 that the image be less than 1000px in width and height. Note that
757− in a markdown source document you can also specify `cover-image`
757+ in a Markdown source document you can also specify `cover-image`
758758 in a YAML metadata block (see [EPUB Metadata], below).
759759
760760`--epub-metadata=`*FILE*
@@ -774,7 +774,7 @@ Options affecting specific writers
774774 id="BookId">` (a randomly generated UUID). Any of these may be
775775 overridden by elements in the metadata file.
776776
777− Note: if the source document is markdown, a YAML metadata block
777+ Note: if the source document is Markdown, a YAML metadata block
778778 in the document can be used instead. See below under
779779 [EPUB Metadata].
780780
@@ -963,13 +963,13 @@ Options for wrapper scripts
963963 with the `-o` option, or `-` (for *stdout*) if no output file was
964964 specified. The remaining lines contain the command-line arguments,
965965 one per line, in the order they appear. These do not include regular
966− Pandoc options and their arguments, but do include any options appearing
966+ pandoc options and their arguments, but do include any options appearing
967967 after a `--` separator at the end of the line.
968968
969969`--ignore-args`
970970
971971: Ignore command-line arguments (for use in wrapper scripts).
972− Regular Pandoc options are not ignored. Thus, for example,
972+ Regular pandoc options are not ignored. Thus, for example,
973973
974974 pandoc --ignore-args -o foo.html -s foo.txt -- -e latin1
975975
@@ -1332,18 +1332,18 @@ pandoc release.
13321332
13331333[pandoc-templates]: https://github.com/jgm/pandoc-templates
13341334
1335−Pandoc's markdown
1335+Pandoc's Markdown
13361336=================
13371337
13381338Pandoc understands an extended and slightly revised version of
1339−John Gruber's [markdown] syntax. This document explains the syntax,
1340−noting differences from standard markdown. Except where noted, these
1339+John Gruber's [Markdown] syntax. This document explains the syntax,
1340+noting differences from standard Markdown. Except where noted, these
13411341differences can be suppressed by using the `markdown_strict` format instead
13421342of `markdown`. An extensions can be enabled by adding `+EXTENSION`
13431343to the format name and disabled by adding `-EXTENSION`. For example,
1344−`markdown_strict+footnotes` is strict markdown with footnotes
1344+`markdown_strict+footnotes` is strict Markdown with footnotes
13451345enabled, while `markdown-footnotes-pipe_tables` is pandoc's
1346−markdown without footnotes or pipe tables.
1346+Markdown without footnotes or pipe tables.
13471347
13481348Philosophy
13491349----------
@@ -1360,7 +1360,7 @@ This principle has guided pandoc's decisions in finding syntax for
13601360tables, footnotes, and other extensions.
13611361
13621362There is, however, one respect in which pandoc's aims are different
1363−from the original aims of markdown. Whereas markdown was originally
1363+from the original aims of Markdown. Whereas Markdown was originally
13641364designed with HTML generation in mind, pandoc is designed for multiple
13651365output formats. Thus, while pandoc allows the embedding of raw HTML,
13661366it discourages it, and provides other, non-HTMLish ways of representing
@@ -1417,7 +1417,7 @@ As with setext-style headers, the header text can contain formatting:
14171417
14181418#### Extension: `blank_before_header` ####
14191419
1420−Standard markdown syntax does not require a blank line before a header.
1420+Standard Markdown syntax does not require a blank line before a header.
14211421Pandoc does require this (except, of course, at the beginning of the
14221422document). The reason for the requirement is that it is all too easy for a
14231423`#` to end up at the beginning of a line by accident (perhaps through line
@@ -1589,7 +1589,7 @@ block in a block quote, you need five spaces after the `>`:
15891589
15901590#### Extension: `blank_before_blockquote` ####
15911591
1592−Standard markdown syntax does not require a blank line before a block
1592+Standard Markdown syntax does not require a blank line before a block
15931593quote. Pandoc does require this (except, of course, at the beginning of the
15941594document). The reason for the requirement is that it is all too easy for a
15951595`>` to end up at the beginning of a line by accident (perhaps through line
@@ -1623,7 +1623,7 @@ Note: blank lines in the verbatim text need not begin with four spaces.
16231623
16241624#### Extension: `fenced_code_blocks` ####
16251625
1626−In addition to standard indented code blocks, Pandoc supports
1626+In addition to standard indented code blocks, pandoc supports
16271627*fenced* code blocks. These begin with a row of three or more
16281628tildes (`~`) and end with a row of tildes that must be at least as long as
16291629the starting row. Everything between these lines is treated as code. No
@@ -1708,7 +1708,7 @@ Line blocks
17081708A line block is a sequence of lines beginning with a vertical bar (`|`)
17091709followed by a space. The division into lines will be preserved in
17101710the output, as will any leading spaces; otherwise, the lines will
1711−be formatted as markdown. This is useful for verse and addresses:
1711+be formatted as Markdown. This is useful for verse and addresses:
17121712
17131713 | The limerick packs laughs anatomical
17141714 | In space that is quite economical.
@@ -1762,7 +1762,7 @@ line (after the bullet):
17621762 list item.
17631763 * and my second.
17641764
1765−But markdown also allows a "lazy" format:
1765+But Markdown also allows a "lazy" format:
17661766
17671767 * here is my first
17681768 list item.
@@ -1798,7 +1798,7 @@ one tab:
17981798 + broccoli
17991799 + chard
18001800
1801−As noted above, markdown allows you to write list items "lazily," instead of
1801+As noted above, Markdown allows you to write list items "lazily," instead of
18021802indenting continuation lines. However, if there are multiple paragraphs or
18031803other blocks in a list item, the first line of each must be indented.
18041804
@@ -1812,18 +1812,18 @@ other blocks in a list item, the first line of each must be indented.
18121812 list item.
18131813
18141814**Note:** Although the four-space rule for continuation paragraphs
1815−comes from the official [markdown syntax guide], the reference implementation,
1815+comes from the official [Markdown syntax guide], the reference implementation,
18161816`Markdown.pl`, does not follow it. So pandoc will give different results than
18171817`Markdown.pl` when authors have indented continuation paragraphs fewer than
18181818four spaces.
18191819
1820−The [markdown syntax guide] is not explicit whether the four-space
1820+The [Markdown syntax guide] is not explicit whether the four-space
18211821rule applies to *all* block-level content in a list item; it only
18221822mentions paragraphs and code blocks. But it implies that the rule
18231823applies to all block-level content (including nested lists), and
18241824pandoc interprets it that way.
18251825
1826− [markdown syntax guide]:
1826+ [Markdown syntax guide]:
18271827 http://daringfireball.net/projects/markdown/syntax#list
18281828
18291829### Ordered lists ###
@@ -1831,7 +1831,7 @@ pandoc interprets it that way.
18311831Ordered lists work just like bulleted lists, except that the items
18321832begin with enumerators rather than bullets.
18331833
1834−In standard markdown, enumerators are decimal numbers followed
1834+In standard Markdown, enumerators are decimal numbers followed
18351835by a period and a space. The numbers themselves are ignored, so
18361836there is no difference between this list:
18371837
@@ -1847,7 +1847,7 @@ and this one:
18471847
18481848#### Extension: `fancy_lists` ####
18491849
1850−Unlike standard markdown, Pandoc allows ordered list items to be marked
1850+Unlike standard Markdown, pandoc allows ordered list items to be marked
18511851with uppercase and lowercase letters and roman numerals, in addition to
18521852arabic numerals. List markers may be enclosed in parentheses or followed by a
18531853single right-parentheses or period. They must be separated from the
@@ -1934,7 +1934,7 @@ A term may have multiple definitions, and each definition may consist of one or
19341934more block elements (paragraph, code block, list, etc.), each indented four
19351935spaces or one tab stop. The body of the definition (including the first line,
19361936aside from the colon or tilde) should be indented four spaces. However,
1937−as with other markdown lists, you can "lazily" omit indentation except
1937+as with other Markdown lists, you can "lazily" omit indentation except
19381938at the beginning of a paragraph or other block element:
19391939
19401940 Term 1
@@ -2006,14 +2006,14 @@ cases" involving lists. Consider this source:
20062006 + Third
20072007
20082008Pandoc transforms this into a "compact list" (with no `<p>` tags around
2009−"First", "Second", or "Third"), while markdown puts `<p>` tags around
2009+"First", "Second", or "Third"), while Markdown puts `<p>` tags around
20102010"Second" and "Third" (but not "First"), because of the blank space
20112011around "Third". Pandoc follows a simple rule: if the text is followed by
20122012a blank line, it is treated as a paragraph. Since "Second" is followed
20132013by a list, and not a blank line, it isn't treated as a paragraph. The
20142014fact that the list is followed by a blank line is irrelevant. (Note:
20152015Pandoc works this way even when the `markdown_strict` format is specified. This
2016−behavior is consistent with the official markdown syntax description,
2016+behavior is consistent with the official Markdown syntax description,
20172017even though it is different from that of `Markdown.pl`.)
20182018
20192019
@@ -2026,7 +2026,7 @@ What if you want to put an indented code block after a list?
20262026
20272027 { my code block }
20282028
2029−Trouble! Here pandoc (like other markdown implementations) will treat
2029+Trouble! Here pandoc (like other Markdown implementations) will treat
20302030`{ my code block }` as the second paragraph of item two, and not as
20312031a code block.
20322032
@@ -2154,7 +2154,7 @@ These work like simple tables, but with the following differences:
21542154In multiline tables, the table parser pays attention to the widths of
21552155the columns, and the writers try to reproduce these relative widths in
21562156the output. So, if you find that one of the columns is too narrow in the
2157−output, try widening it in the markdown source.
2157+output, try widening it in the Markdown source.
21582158
21592159Headers may be omitted in multiline tables as well as simple tables:
21602160
@@ -2231,7 +2231,7 @@ output, the cells produced by pipe tables will not wrap, since there
22312231is no information available about relative widths. If you want content
22322232to wrap within cells, use multiline or grid tables.
22332233
2234−Note: Pandoc also recognizes pipe tables of the following
2234+Note: pandoc also recognizes pipe tables of the following
22352235form, as can be produced by Emacs' orgtbl-mode:
22362236
22372237 | One | Two |
@@ -2332,7 +2332,7 @@ hyphens (`---`) at the top and a line of three hyphens (`---`) or three dots
23322332document, but if it is not at the beginning, it must be preceded by a blank
23332333line. (Note that, because of the way pandoc concatenates input files when
23342334several are provided, you may also keep the metadata in a separate YAML file
2335−and pass it to pandoc as an argument, along with your markdown files:
2335+and pass it to pandoc as an argument, along with your Markdown files:
23362336
23372337 pandoc chap1.md chap2.md chap3.md metadata.yaml -s -o book.html
23382338
@@ -2341,7 +2341,7 @@ Just be sure that the YAML file begins with `---` and ends with `---` or
23412341
23422342Metadata will be taken from the fields of the YAML object and added to any
23432343existing document metadata. Metadata can contain lists and objects (nested
2344−arbitrarily), but all string scalars will be interpreted as markdown. Fields
2344+arbitrarily), but all string scalars will be interpreted as Markdown. Fields
23452345with names ending in an underscore will be ignored by pandoc. (They may be
23462346given a role by external processors.)
23472347
@@ -2349,7 +2349,7 @@ A document may contain multiple metadata blocks. The metadata fields will
23492349be combined through a *left-biased union*: if two metadata blocks attempt
23502350to set the same field, the value from the first block will be taken.
23512351
2352−When pandoc is used with `-t markdown` to create a markdown document,
2352+When pandoc is used with `-t markdown` to create a Markdown document,
23532353a YAML metadata block will be produced only if the `-s/--standalone`
23542354option is used. All of the metadata will appear in a single block
23552355at the beginning of the document.
@@ -2376,7 +2376,7 @@ when the field contains blank lines:
23762376
23772377Template variables will be set automatically from the metadata. Thus, for
23782378example, in writing HTML, the variable `abstract` will be set to the HTML
2379−equivalent of the markdown in the `abstract` field:
2379+equivalent of the Markdown in the `abstract` field:
23802380
23812381 <p>This is the abstract.</p>
23822382 <p>It consists of two paragraphs.</p>
@@ -2413,12 +2413,12 @@ instead of
24132413
24142414 <strong>hello</strong>
24152415
2416−This rule is easier to remember than standard markdown's rule,
2416+This rule is easier to remember than standard Markdown's rule,
24172417which allows only the following characters to be backslash-escaped:
24182418
24192419 \`*_{}[]()>#+-.!
24202420
2421−(However, if the `markdown_strict` format is used, the standard markdown rule
2421+(However, if the `markdown_strict` format is used, the standard Markdown rule
24222422will be used.)
24232423
24242424A backslash-escaped space is parsed as a nonbreaking space. It will
@@ -2428,7 +2428,7 @@ appear in TeX output as `~` and in HTML and XML as `\ ` or
24282428A backslash-escaped newline (i.e. a backslash occurring at the end of
24292429a line) is parsed as a hard line break. It will appear in TeX output as
24302430`\\` and in HTML as `<br />`. This is a nice alternative to
2431−markdown's "invisible" way of indicating hard line breaks using
2431+Markdown's "invisible" way of indicating hard line breaks using
24322432two trailing spaces on a line.
24332433
24342434Backslash escapes do not work in verbatim contexts.
@@ -2520,7 +2520,7 @@ of consecutive backticks (optionally followed by a space)
25202520and ends with a string of the same number of backticks (optionally
25212521preceded by a space).
25222522
2523−Note that backslash-escapes (and other markdown constructs) do not
2523+Note that backslash-escapes (and other Markdown constructs) do not
25242524work in verbatim contexts:
25252525
25262526 This is a backslash followed by an asterisk: `\*`.
@@ -2653,7 +2653,7 @@ Raw HTML
26532653Markdown allows you to insert raw HTML (or DocBook) anywhere in a document
26542654(except verbatim contexts, where `<`, `>`, and `&` are interpreted
26552655literally). (Technically this is not an extension, since standard
2656−markdown allows it, but it has been made an extension so that it can
2656+Markdown allows it, but it has been made an extension so that it can
26572657be disabled if desired.)
26582658
26592659The raw HTML is passed through unchanged in HTML, S5, Slidy, Slideous,
@@ -2662,15 +2662,15 @@ formats.
26622662
26632663#### Extension: `markdown_in_html_blocks` ####
26642664
2665−Standard markdown allows you to include HTML "blocks": blocks
2665+Standard Markdown allows you to include HTML "blocks": blocks
26662666of HTML between balanced tags that are separated from the surrounding text
26672667with blank lines, and start and end at the left margin. Within
2668−these blocks, everything is interpreted as HTML, not markdown;
2668+these blocks, everything is interpreted as HTML, not Markdown;
26692669so (for example), `*` does not signify emphasis.
26702670
26712671Pandoc behaves this way when the `markdown_strict` format is used; but
2672−by default, pandoc interprets material between HTML block tags as markdown.
2673−Thus, for example, Pandoc will turn
2672+by default, pandoc interprets material between HTML block tags as Markdown.
2673+Thus, for example, pandoc will turn
26742674
26752675 <table>
26762676 <tr>
@@ -2691,12 +2691,12 @@ into
26912691whereas `Markdown.pl` will preserve it as is.
26922692
26932693There is one exception to this rule: text between `<script>` and
2694−`<style>` tags is not interpreted as markdown.
2694+`<style>` tags is not interpreted as Markdown.
26952695
2696−This departure from standard markdown should make it easier to mix
2697−markdown with HTML block elements. For example, one can surround
2698−a block of markdown text with `<div>` tags without preventing it
2699−from being interpreted as markdown.
2696+This departure from standard Markdown should make it easier to mix
2697+Markdown with HTML block elements. For example, one can surround
2698+a block of Markdown text with `<div>` tags without preventing it
2699+from being interpreted as Markdown.
27002700
27012701#### Extension: `native_divs` ####
27022702
@@ -2734,7 +2734,7 @@ Note that in LaTeX environments, like
27342734 \end{tabular}
27352735
27362736the material between the begin and end tags will be interpreted as raw
2737−LaTeX, not as markdown.
2737+LaTeX, not as Markdown.
27382738
27392739Inline LaTeX is ignored in output formats other than Markdown, LaTeX,
27402740and ConTeXt.
@@ -2830,7 +2830,7 @@ empty:
28302830
28312831 [my website]: http://foo.bar.baz
28322832
2833−Note: In `Markdown.pl` and most other markdown implementations,
2833+Note: In `Markdown.pl` and most other Markdown implementations,
28342834reference link definitions cannot occur in nested constructions
28352835such as list items or block quotes. Pandoc lifts this arbitrary
28362836seeming restriction. So the following is fine in pandoc, though
@@ -2903,7 +2903,7 @@ Footnotes
29032903
29042904#### Extension: `footnotes` ####
29052905
2906−Pandoc's markdown allows footnotes, using the following syntax:
2906+Pandoc's Markdown allows footnotes, using the following syntax:
29072907
29082908 Here is a footnote reference,[^1] and another.[^longnote]
29092909
@@ -2982,7 +2982,7 @@ Note that `pandoc-citeproc --bib2json` and `pandoc-citeproc --bib2yaml`
29822982can produce `.json` and `.yaml` files from any of the supported formats.
29832983
29842984In-field markup: In BibTeX and BibLaTeX databases, pandoc-citeproc parses
2985−a subset of LaTeX markup; in CSL YAML databases, pandoc markdown; and in CSL JSON databases, an [HTML-like markup][CSL markup specs]:
2985+a subset of LaTeX markup; in CSL YAML databases, pandoc Markdown; and in CSL JSON databases, an [HTML-like markup][CSL markup specs]:
29862986
29872987`<i>...</i>`
29882988: italics
@@ -3124,10 +3124,10 @@ format (either BibTeX or BibLaTeX).
31243124Non-pandoc extensions
31253125---------------------
31263126
3127−The following markdown syntax extensions are not enabled by default
3127+The following Markdown syntax extensions are not enabled by default
31283128in pandoc, but may be enabled by adding `+EXTENSION` to the format
31293129name, where `EXTENSION` is the name of the extension. Thus, for
3130−example, `markdown+hard_line_breaks` is markdown with hard line breaks.
3130+example, `markdown+hard_line_breaks` is Markdown with hard line breaks.
31313131
31323132#### Extension: `lists_without_preceding_blankline` ####
31333133
@@ -3161,8 +3161,8 @@ as display TeX math.
31613161
31623162#### Extension: `markdown_attribute` ####
31633163
3164−By default, pandoc interprets material inside block-level tags as markdown.
3165−This extension changes the behavior so that markdown is only parsed
3164+By default, pandoc interprets material inside block-level tags as Markdown.
3165+This extension changes the behavior so that Markdown is only parsed
31663166inside block-level tags if the tags have the attribute `markdown=1`.
31673167
31683168#### Extension: `mmd_title_block` ####
@@ -3244,7 +3244,7 @@ in several respects:
32443244Markdown variants
32453245-----------------
32463246
3247−In addition to pandoc's extended markdown, the following markdown
3247+In addition to pandoc's extended Markdown, the following Markdown
32483248variants are supported:
32493249
32503250`markdown_phpextra` (PHP Markdown Extra)
@@ -3270,11 +3270,11 @@ variants are supported:
32703270`markdown_strict` (Markdown.pl)
32713271: `raw_html`
32723272
3273−Extensions with formats other than markdown
3273+Extensions with formats other than Markdown
32743274-------------------------------------------
32753275
32763276Some of the extensions discussed above can be used with formats
3277−other than markdown:
3277+other than Markdown:
32783278
32793279* `auto_identifiers` can be used with `latex`, `rst`, `mediawiki`,
32803280 and `textile` input (and is used by default).
@@ -3284,15 +3284,15 @@ other than markdown:
32843284 (This is handy for reading web pages formatted using MathJax,
32853285 for example.)
32863286
3287−Producing slide shows with Pandoc
3287+Producing slide shows with pandoc
32883288=================================
32893289
3290−You can use Pandoc to produce an HTML + javascript slide presentation
3290+You can use pandoc to produce an HTML + javascript slide presentation
32913291that can be viewed via a web browser. There are five ways to do this,
32923292using [S5], [DZSlides], [Slidy], [Slideous], or [reveal.js].
32933293You can also produce a PDF slide show using LaTeX [`beamer`].
32943294
3295−Here's the markdown source for a simple slide show, `habits.txt`:
3295+Here's the Markdown source for a simple slide show, `habits.txt`:
32963296
32973297 % Habits
32983298 % John Doe
@@ -3460,12 +3460,12 @@ Speaker notes
34603460-------------
34613461
34623462reveal.js has good support for speaker notes. You can add notes to your
3463−markdown document thus:
3463+Markdown document thus:
34643464
34653465 <div class="notes">
34663466 This is my note.
34673467
3468− - It can contain markdown
3468+ - It can contain Markdown
34693469 - like this list
34703470
34713471 </div>
@@ -3496,7 +3496,7 @@ EPUB Metadata
34963496-------------
34973497
34983498EPUB metadata may be specified using the `--epub-metadata` option, but
3499−if the source document is markdown, it is better to use a [YAML metadata
3499+if the source document is Markdown, it is better to use a [YAML metadata
35003500block][Extension: `yaml_metadata_block`]. Here is an example:
35013501
35023502 ---
@@ -3605,12 +3605,12 @@ format (`markdown`, `markdown_strict`, `rst`, or `latex` for input or output;
36053605`beamer`, `html` or `html5` for output only), pandoc will treat the document as
36063606literate Haskell source. This means that
36073607
3608− - In markdown input, "bird track" sections will be parsed as Haskell
3608+ - In Markdown input, "bird track" sections will be parsed as Haskell
36093609 code rather than block quotations. Text between `\begin{code}`
36103610 and `\end{code}` will also be treated as Haskell code. For
36113611 ATX-style headers the character '=' will be used instead of '#'.
36123612
3613− - In markdown output, code blocks with classes `haskell` and `literate`
3613+ - In Markdown output, code blocks with classes `haskell` and `literate`
36143614 will be rendered using bird tracks, and block quotations will be
36153615 indented one space, so they will not be treated as Haskell code.
36163616 In addition, headers will be rendered setext-style (with underlines)
@@ -3636,7 +3636,7 @@ Examples:
36363636
36373637 pandoc -f markdown+lhs -t html
36383638
3639−reads literate Haskell source formatted with markdown conventions and writes
3639+reads literate Haskell source formatted with Markdown conventions and writes
36403640ordinary HTML (without bird tracks).
36413641
36423642 pandoc -f markdown+lhs -t html+lhs