From d6812a617e987f3022eb2aaba92a94cd7db8feaf Mon Sep 17 00:00:00 2001 From: Titus Wormer Date: Tue, 1 Oct 2019 21:21:05 +0200 Subject: [PATCH 01/21] Remove line tabulation, form feed from whitespace --- spec.txt | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/spec.txt b/spec.txt index c62df5bb..b6c010a0 100644 --- a/spec.txt +++ b/spec.txt @@ -307,16 +307,14 @@ A line containing no characters, or a line containing only spaces The following definitions of character classes will be used in this spec: A [whitespace character](@) is a space -(`U+0020`), tab (`U+0009`), newline (`U+000A`), line tabulation (`U+000B`), -form feed (`U+000C`), or carriage return (`U+000D`). +(`U+0020`), tab (`U+0009`), newline (`U+000A`), or carriage return (`U+000D`). [Whitespace](@) is a sequence of one or more [whitespace characters]. A [Unicode whitespace character](@) is any code point in the Unicode `Zs` general category, or a tab (`U+0009`), -carriage return (`U+000D`), newline (`U+000A`), or form feed -(`U+000C`). +carriage return (`U+000D`), newline (`U+000A`), or form feed (`U+000C`). [Unicode whitespace](@) is a sequence of one or more [Unicode whitespace characters]. From 02030c0ec3cc4da1c4c77d55911bab17ad974bc2 Mon Sep 17 00:00:00 2001 From: Titus Wormer Date: Tue, 1 Oct 2019 21:21:18 +0200 Subject: [PATCH 02/21] Remove superfluous blank line from spec --- spec.txt | 1 - 1 file changed, 1 deletion(-) diff --git a/spec.txt b/spec.txt index b6c010a0..d9495a25 100644 --- a/spec.txt +++ b/spec.txt @@ -9726,4 +9726,3 @@ closers: After we're done, we remove all delimiters above `stack_bottom` from the delimiter stack. - From a24f2b114d7eef325821bb1246ec052953c5e5f2 Mon Sep 17 00:00:00 2001 From: Titus Wormer Date: Tue, 1 Oct 2019 21:24:02 +0200 Subject: [PATCH 03/21] Rename newline to line feed or line ending --- spec.txt | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/spec.txt b/spec.txt index d9495a25..bfaab494 100644 --- a/spec.txt +++ b/spec.txt @@ -294,12 +294,12 @@ of [characters] rather than bytes. A conforming parser may be limited to a certain encoding. A [line](@) is a sequence of zero or more [characters] -other than newline (`U+000A`) or carriage return (`U+000D`), +other than line feed (`U+000A`) or carriage return (`U+000D`), followed by a [line ending] or by the end of file. -A [line ending](@) is a newline (`U+000A`), a carriage return -(`U+000D`) not followed by a newline, or a carriage return and a -following newline. +A [line ending](@) is a line feed (`U+000A`), a carriage return +(`U+000D`) not followed by a line feed, or a carriage return and a +following line feed. A line containing no characters, or a line containing only spaces (`U+0020`) or tabs (`U+0009`), is called a [blank line](@). @@ -307,14 +307,14 @@ A line containing no characters, or a line containing only spaces The following definitions of character classes will be used in this spec: A [whitespace character](@) is a space -(`U+0020`), tab (`U+0009`), newline (`U+000A`), or carriage return (`U+000D`). +(`U+0020`), tab (`U+0009`), line feed (`U+000A`), or carriage return (`U+000D`). [Whitespace](@) is a sequence of one or more [whitespace characters]. A [Unicode whitespace character](@) is any code point in the Unicode `Zs` general category, or a tab (`U+0009`), -carriage return (`U+000D`), newline (`U+000A`), or form feed (`U+000C`). +carriage return (`U+000D`), line feed (`U+000A`), or form feed (`U+000C`). [Unicode whitespace](@) is a sequence of one or more [Unicode whitespace characters]. @@ -2443,7 +2443,7 @@ _world_. ```````````````````````````````` -In this case, the HTML block is terminated by the newline — the `**Hello**` +In this case, the HTML block is terminated by the blank line — the `**Hello**` text remains verbatim — and regular parsing resumes, with a paragraph, emphasised `world` and inline and block HTML following. @@ -6439,7 +6439,7 @@ whitespace: ```````````````````````````````` -A newline also counts as whitespace: +A line ending also counts as whitespace: ```````````````````````````````` example *foo bar @@ -6604,7 +6604,7 @@ __ foo bar__ ```````````````````````````````` -A newline counts as whitespace: +A line ending counts as whitespace: ```````````````````````````````` example __ foo bar__ From 55fee91a96fc22132d9f43b74be5bf6dd831950a Mon Sep 17 00:00:00 2001 From: Titus Wormer Date: Wed, 2 Oct 2019 09:57:37 +0200 Subject: [PATCH 04/21] Reword to be more explicit about whitespace --- spec.txt | 294 +++++++++++++++++++++++++++---------------------------- 1 file changed, 147 insertions(+), 147 deletions(-) diff --git a/spec.txt b/spec.txt index bfaab494..b8abdee2 100644 --- a/spec.txt +++ b/spec.txt @@ -306,23 +306,16 @@ A line containing no characters, or a line containing only spaces The following definitions of character classes will be used in this spec: -A [whitespace character](@) is a space -(`U+0020`), tab (`U+0009`), line feed (`U+000A`), or carriage return (`U+000D`). - -[Whitespace](@) is a sequence of one or more [whitespace -characters]. - A [Unicode whitespace character](@) is any code point in the Unicode `Zs` general category, or a tab (`U+0009`), carriage return (`U+000D`), line feed (`U+000A`), or form feed (`U+000C`). -[Unicode whitespace](@) is a sequence of one -or more [Unicode whitespace characters]. +[Unicode whitespace](@) is a sequence of one or more +[Unicode whitespace characters]. -A [space](@) is `U+0020`. +A [tab](@) is `U+0009`. -A [non-whitespace character](@) is any character -that is not a [whitespace character]. +A [space](@) is `U+0020`. An [ASCII control character](@) is a character between `U+0000–1F` (both including) or `U+007F`. @@ -341,7 +334,7 @@ the general Unicode categories `Pc`, `Pd`, `Pe`, `Pf`, `Pi`, `Po`, or `Ps`. ## Tabs Tabs in lines are not expanded to [spaces]. However, -in contexts where whitespace helps to define block structure, +in contexts where spaces help to define block structure, tabs behave as if they were replaced by spaces with a tab stop of 4 characters. @@ -914,7 +907,7 @@ __

```````````````````````````````` -One to three spaces indent are allowed: +One to three spaces of indentation are allowed: ```````````````````````````````` example *** @@ -927,7 +920,7 @@ One to three spaces indent are allowed: ```````````````````````````````` -Four spaces is too many: +Four spaces of indentation is too many: ```````````````````````````````` example *** @@ -955,7 +948,7 @@ _____________________________________ ```````````````````````````````` -Spaces are allowed between the characters: +Spaces and tabs are allowed between the characters: ```````````````````````````````` example - - - @@ -978,7 +971,7 @@ Spaces are allowed between the characters: ```````````````````````````````` -Spaces are allowed at the end: +Spaces and tabs are allowed at the end: ```````````````````````````````` example - - - - @@ -1002,7 +995,7 @@ a------ ```````````````````````````````` -It is required that all of the [non-whitespace characters] be the same. +It is required that all of the characters other than spaces or tabs be the same. So, this is not a thematic break: ```````````````````````````````` example @@ -1097,12 +1090,12 @@ An [ATX heading](@) consists of a string of characters, parsed as inline content, between an opening sequence of 1--6 unescaped `#` characters and an optional closing sequence of any number of unescaped `#` characters. -The opening sequence of `#` characters must be followed by a -[space] or by the end of line. The optional closing sequence of `#`s must be -preceded by a [space] and may be followed by spaces only. The opening -`#` character may be indented 0-3 spaces. The raw contents of the -heading are stripped of leading and trailing spaces before being parsed -as inline content. The heading level is equal to the number of `#` +The opening sequence of `#` characters must be followed by spaces or tabs, or +by the end of line. The optional closing sequence of `#`s must be preceded by +spaces or tabs space and may be followed by spaces or tabs only. The opening +`#` character may be indented 0-3 spaces of indentation. The raw contents of +the heading are stripped of leading and trailing space or tabs before being +parsed as inline content. The heading level is equal to the number of `#` characters in the opening sequence. Simple headings: @@ -1133,7 +1126,7 @@ More than six `#` characters is not a heading: ```````````````````````````````` -At least one space is required between the `#` characters and the +At least one space or tab is required between the `#` characters and the heading's contents, unless the heading is empty. Note that many implementations currently do not require the space. However, the space was required by the @@ -1169,7 +1162,7 @@ Contents are parsed as inlines: ```````````````````````````````` -Leading and trailing [whitespace] is ignored in parsing inline content: +Leading and trailing spaces or tabs are ignored in parsing inline content: ```````````````````````````````` example # foo @@ -1178,7 +1171,7 @@ Leading and trailing [whitespace] is ignored in parsing inline content: ```````````````````````````````` -One to three spaces indentation are allowed: +One to three spaces of indentation are allowed: ```````````````````````````````` example ### foo @@ -1191,7 +1184,7 @@ One to three spaces indentation are allowed: ```````````````````````````````` -Four spaces are too much: +Four spaces of indentation are too much: ```````````````````````````````` example # foo @@ -1232,7 +1225,7 @@ It need not be the same length as the opening sequence: ```````````````````````````````` -Spaces are allowed after the closing sequence: +Spaces or tabs are allowed after the closing sequence: ```````````````````````````````` example ### foo ### @@ -1241,7 +1234,7 @@ Spaces are allowed after the closing sequence: ```````````````````````````````` -A sequence of `#` characters with anything but [spaces] following it +A sequence of `#` characters with anything but spaces or tabs following it is not a closing sequence, but counts as part of the contents of the heading: @@ -1252,7 +1245,7 @@ heading: ```````````````````````````````` -The closing sequence must be preceded by a space: +The closing sequence must be preceded by a space or tab: ```````````````````````````````` example # foo# @@ -1316,8 +1309,8 @@ ATX headings can be empty: ## Setext headings A [setext heading](@) consists of one or more -lines of text, each containing at least one [non-whitespace -character], with no more than 3 spaces indentation, followed by +lines of text, not interrupted by a blank line, of which the first line does not +have more than 3 spaces of indentation, followed by a [setext heading underline]. The lines of text must be such that, were they not followed by the setext heading underline, they would be interpreted as a paragraph: they cannot be @@ -1327,7 +1320,7 @@ interpretable as a [code fence], [ATX heading][ATX headings], A [setext heading underline](@) is a sequence of `=` characters or a sequence of `-` characters, with no more than 3 -spaces indentation and any number of trailing spaces. If a line +spaces of indentation and any number of trailing space or tabs. If a line containing a single `-` can be interpreted as an empty [list items], it should be interpreted this way and not as a [setext heading underline]. @@ -1371,7 +1364,7 @@ baz The contents are the result of parsing the headings's raw content as inlines. The heading's raw content is formed by concatenating the lines and removing initial and final -[whitespace]. +spaces or tabs. ```````````````````````````````` example Foo *bar @@ -1397,7 +1390,7 @@ Foo ```````````````````````````````` -The heading content can be indented up to three spaces, and need +The heading content can be indented up to three spaces of indentation, and need not line up with the underlining: ```````````````````````````````` example @@ -1416,7 +1409,7 @@ not line up with the underlining: ```````````````````````````````` -Four spaces indent is too much: +Four spaces of indentation is too much: ```````````````````````````````` example Foo @@ -1434,8 +1427,8 @@ Foo ```````````````````````````````` -The setext heading underline can be indented up to three spaces, and -may have trailing spaces: +The setext heading underline can be indented up to three spaces of indentation, +and may have trailing spaces or tabs: ```````````````````````````````` example Foo @@ -1445,7 +1438,7 @@ Foo ```````````````````````````````` -Four spaces is too much: +Four spaces of indentation is too much: ```````````````````````````````` example Foo @@ -1456,7 +1449,7 @@ Foo ```````````````````````````````` -The setext heading underline cannot contain internal spaces: +The setext heading underline cannot contain internal spaces or tabs: ```````````````````````````````` example Foo @@ -1472,7 +1465,7 @@ Foo ```````````````````````````````` -Trailing spaces in the content line do not cause a line break: +Trailing spaces or tabs in the content line do not cause a line break: ```````````````````````````````` example Foo @@ -1737,8 +1730,8 @@ baz

An [indented code block](@) is composed of one or more [indented chunks] separated by blank lines. An [indented chunk](@) is a sequence of non-blank lines, -each indented four or more spaces. The contents of the code block are -the literal contents of the lines, including trailing +each indented four or more spaces of indentation. The contents of the code block +are the literal contents of the lines, including trailing [line endings], minus four spaces of indentation. An indented code block has no [info string]. @@ -1831,8 +1824,8 @@ chunk3 ```````````````````````````````` -Any initial spaces beyond four will be included in the content, even -in interior blank lines: +Any initial spaces or tabs beyond four spaces of indentation will be included in +the content, even in interior blank lines: ```````````````````````````````` example chunk1 @@ -1859,7 +1852,7 @@ bar

```````````````````````````````` -However, any non-blank line with fewer than four leading spaces ends +However, any non-blank line with fewer than four spaces of indentation ends the code block immediately. So a paragraph may occur immediately after indented code: @@ -1894,7 +1887,7 @@ Heading ```````````````````````````````` -The first line can be indented more than four spaces: +The first line can be indented more than four spaces of indentation: ```````````````````````````````` example foo @@ -1921,7 +1914,7 @@ are not included in it: ```````````````````````````````` -Trailing spaces are included in the code block's content: +Trailing spaces or tabs are included in the code block's content: ```````````````````````````````` example foo @@ -1938,11 +1931,11 @@ A [code fence](@) is a sequence of at least three consecutive backtick characters (`` ` ``) or tildes (`~`). (Tildes and backticks cannot be mixed.) A [fenced code block](@) -begins with a code fence, indented no more than three spaces. +begins with a code fence, indented no more than three spaces of indentation. The line with the opening code fence may optionally contain some text following the code fence; this is trimmed of leading and trailing -whitespace and called the [info string](@). If the [info string] comes +spaces or tabs and called the [info string](@). If the [info string] comes after a backtick fence, it may not contain any backtick characters. (The reason for this restriction is that otherwise some inline code would be incorrectly interpreted as the @@ -1952,13 +1945,13 @@ The content of the code block consists of all subsequent lines, until a closing [code fence] of the same type as the code block began with (backticks or tildes), and with at least as many backticks or tildes as the opening code fence. If the leading code fence is -indented N spaces, then up to N spaces of indentation are removed from -each line of the content (if present). (If a content line is not -indented, it is preserved unchanged. If it is indented less than N -spaces, all of the indentation is removed.) +indented N spaces of indentation, then up to N spaces of indentation are removed +from each line of the content (if present). (If a content line is not +indented, it is preserved unchanged. If it is indented N spaces or less, all +of the indentation is removed.) -The closing code fence may be indented up to three spaces, and may be -followed only by spaces, which are ignored. If the end of the +The closing code fence may be indented up to three spaces of indentation, and +may be followed only by spaces or tabs, which are ignored. If the end of the containing block (or document) is reached and no closing code fence has been found, the code block contains all of the lines after the opening code fence until the end of the containing block (or @@ -2171,7 +2164,7 @@ aaa ```````````````````````````````` -Four spaces indentation produces an indented code block: +Four spaces of indentation produces an indented code block: ```````````````````````````````` example ``` @@ -2185,8 +2178,8 @@ aaa ```````````````````````````````` -Closing fences may be indented by 0-3 spaces, and their indentation -need not match that of the opening fence: +Closing fences may be indented by 0-3 spaces of indentation, and their +indentation need not match that of the opening fence: ```````````````````````````````` example ``` @@ -2222,7 +2215,7 @@ aaa -Code fences (opening and closing) cannot contain internal spaces: +Code fences (opening and closing) cannot contain internal spaces or tabs: ```````````````````````````````` example ``` ``` @@ -2365,7 +2358,7 @@ as raw HTML (and will not be escaped in HTML output). There are seven kinds of [HTML block], which can be defined by their start and end conditions. The block begins with a line that meets a -[start condition](@) (after up to three spaces optional indentation). +[start condition](@) (after up to three optional spaces of indentation). It ends with the first subsequent line that meets a matching [end condition](@), or the last line of the document, or the last line of the [container block](#container-blocks) containing the current HTML @@ -2374,7 +2367,7 @@ the first line meets both the [start condition] and the [end condition], the block will contain just that line. 1. **Start condition:** line begins with the string ``, or the end of the line.\ **End condition:** line contains an end tag ``, ``, or `` (case-insensitive; it @@ -2405,14 +2398,14 @@ followed by one of the strings (case-insensitive) `address`, `nav`, `noframes`, `ol`, `optgroup`, `option`, `p`, `param`, `section`, `source`, `summary`, `table`, `tbody`, `td`, `tfoot`, `th`, `thead`, `title`, `tr`, `track`, `ul`, followed -by [whitespace], the end of the line, the string `>`, or +by a space, a tab, the end of the line, the string `>`, or the string `/>`.\ **End condition:** line is followed by a [blank line]. 7. **Start condition:** line begins with a complete [open tag] (with any [tag name] other than `script`, `style`, or `pre`) or a complete [closing tag], -followed only by [whitespace] or the end of the line.\ +followed only by a space, a tab, or the end of the line.\ **End condition:** line is followed by a [blank line]. HTML blocks continue until they are closed by their appropriate @@ -2945,7 +2938,7 @@ function matchwo(a,b) ```````````````````````````````` -The opening tag can be indented 1-3 spaces, but not 4: +The opening tag can be indented 1-3 spaces of indentation, but not 4: ```````````````````````````````` example @@ -3021,7 +3014,7 @@ specification, which says: > The only restrictions are that block-level HTML elements — > e.g. `
`, ``, `
`, `
`, etc. — must be separated from
 > surrounding content by blank lines, and the start and end tags of the
-> block should not be indented with tabs or spaces.
+> block should not be indented with spaces or tabs.
 
 In some ways Gruber's rule is more restrictive than the one given
 here:
@@ -3139,14 +3132,14 @@ deleted.  The exception is inside `
` tags, but as described
 ## Link reference definitions
 
 A [link reference definition](@)
-consists of a [link label], indented up to three spaces, followed
-by a colon (`:`), optional [whitespace] (including up to one
+consists of a [link label], indented up to three spaces of indentation, followed
+by a colon (`:`), optional spaces or tabs (including up to one
 [line ending]), a [link destination],
-optional [whitespace] (including up to one
+optional spaces or tabs (including up to one
 [line ending]), and an optional [link
 title], which if it is present must be separated
-from the [link destination] by [whitespace].
-No further [non-whitespace characters] may occur on the line.
+from the [link destination] by spaces or tabs.
+No further character may occur.
 
 A [link reference definition]
 does not correspond to a structural element of a document.  Instead, it
@@ -3264,7 +3257,7 @@ The link destination may not be omitted:
 ````````````````````````````````
 
 The title must be separated from the link destination by
-whitespace:
+spaces or tabs:
 
 ```````````````````````````````` example
 [foo]: (baz)
@@ -3355,7 +3348,7 @@ bar
 
 
 This is not a link reference definition, because there are
-[non-whitespace characters] after the title:
+characters other than tabs or spaces after the title:
 
 ```````````````````````````````` example
 [foo]: /url "title" ok
@@ -3506,7 +3499,7 @@ kinds of blocks forms a [paragraph](@).
 The contents of the paragraph are the result of parsing the
 paragraph's raw content as inlines.  The paragraph's raw content
 is formed by concatenating the lines and removing initial and final
-[whitespace].
+spaces or tabs.
 
 A simple example with two paragraphs:
 
@@ -3549,7 +3542,7 @@ bbb
 ````````````````````````````````
 
 
-Leading spaces are skipped:
+Leading spaces or tabs are skipped:
 
 ```````````````````````````````` example
   aaa
@@ -3574,7 +3567,7 @@ ccc

 ````````````````````````````````
 
 
-However, the first line may be indented at most three spaces,
+However, the first line may be indented at most three spaces of indentation,
 or an indented code block will be triggered:
 
 ```````````````````````````````` example
@@ -3596,7 +3589,7 @@ bbb
 ````````````````````````````````
 
 
-Final spaces are stripped before inline parsing, so a paragraph
+Final spaces or tabs are stripped before inline parsing, so a paragraph
 that ends with two or more spaces will not end with a [hard line
 break]:
 
@@ -3656,8 +3649,9 @@ these constructions.  (A recipe is provided below in the section entitled
 ## Block quotes
 
 A [block quote marker](@)
-consists of 0-3 spaces of initial indent, plus (a) the character `>` together
-with a following space, or (b) a single character `>` not followed by a space.
+consists of 0-3 spaces of indentation, plus (a) the character `>` together
+with a following space of indentation, or (b) a single character `>` not
+followed by a space of indentation.
 
 The following rules define [block quotes]:
 
@@ -3669,8 +3663,8 @@ The following rules define [block quotes]:
 2.  **Laziness.**  If a string of lines *Ls* constitute a [block
     quote](#block-quotes) with contents *Bs*, then the result of deleting
     the initial [block quote marker] from one or
-    more lines in which the next [non-whitespace character] after the [block
-    quote marker] is [paragraph continuation
+    more lines in which the next character other than a space or tab after the
+    [block quote marker] is [paragraph continuation
     text] is a block quote with *Bs* as its content.
     [Paragraph continuation text](@) is text
     that will be parsed as part of the content of a paragraph, but does
@@ -3696,7 +3690,7 @@ baz

 ````````````````````````````````
 
 
-The spaces after the `>` characters can be omitted:
+The space or tab after the `>` characters can be omitted:
 
 ```````````````````````````````` example
 ># Foo
@@ -3711,7 +3705,7 @@ baz

 ````````````````````````````````
 
 
-The `>` characters can be indented 1-3 spaces:
+The `>` characters can be indented 1-3 spaces of indentation:
 
 ```````````````````````````````` example
    > # Foo
@@ -3726,7 +3720,7 @@ baz

 ````````````````````````````````
 
 
-Four spaces gives us a code block:
+Four spaces of indentation gives us a code block:
 
 ```````````````````````````````` example
     > # Foo
@@ -4061,8 +4055,8 @@ baz

 
 When including an indented code block in a block quote,
 remember that the [block quote marker] includes
-both the `>` and a following space.  So *five spaces* are needed after
-the `>`:
+both the `>` and a following spaces of indentation.  So *five spaces* are needed
+after the `>`:
 
 ```````````````````````````````` example
 >     code
@@ -4097,10 +4091,10 @@ in some browsers.)
 The following rules define [list items]:
 
 1.  **Basic case.**  If a sequence of lines *Ls* constitute a sequence of
-    blocks *Bs* starting with a [non-whitespace character], and *M* is a
-    list marker of width *W* followed by 1 ≤ *N* ≤ 4 spaces, then the result
-    of prepending *M* and the following spaces to the first line of
-    *Ls*, and indenting subsequent lines of *Ls* by *W + N* spaces, is a
+    blocks *Bs* starting with a character other than a space or tab, and *M* is
+    a list marker of width *W* followed by 1 ≤ *N* ≤ 4 spaces of indentation,
+    then the result of prepending *M* and the following spaces to the first line
+    of Ls*, and indenting subsequent lines of *Ls* by *W + N* spaces, is a
     list item with *Bs* as its contents.  The type of the list item
     (bullet or ordered) is determined by the type of its list marker.
     If the list item is ordered, then it is also assigned a start
@@ -4165,8 +4159,8 @@ with two lines.

 The most important thing to notice is that the position of
 the text after the list marker determines how much indentation
 is needed in subsequent blocks in the list item.  If the list
-marker takes up two spaces, and there are three spaces between
-the list marker and the next [non-whitespace character], then blocks
+marker takes up two spaces of indentation, and there are three spaces between
+the list marker and the next character other than a space or tab, then blocks
 must be indented five spaces in order to fall under the list
 item.
 
@@ -4227,10 +4221,10 @@ put under the list item:
 
 
 It is tempting to think of this in terms of columns:  the continuation
-blocks must be indented at least to the column of the first
-[non-whitespace character] after the list marker. However, that is not quite right.
-The spaces after the list marker determine how much relative indentation
-is needed.  Which column this indentation reaches will depend on
+blocks must be indented at least to the column of the first character other than
+a space or tab after the list marker.  However, that is not quite right.
+The spaces of indentation after the list marker determine how much relative
+indentation is needed.  Which column this indentation reaches will depend on
 how the list item is embedded in other constructions, as shown by
 this example:
 
@@ -4277,7 +4271,7 @@ far enough past the blockquote marker:
 ````````````````````````````````
 
 
-Note that at least one space is needed between the list marker and
+Note that at least one spaces or tab is needed between the list marker and
 any following content, so these are not list items:
 
 ```````````````````````````````` example
@@ -4409,16 +4403,16 @@ A start number may not be negative:
 2.  **Item starting with indented code.**  If a sequence of lines *Ls*
     constitute a sequence of blocks *Bs* starting with an indented code
     block, and *M* is a list marker of width *W* followed by
-    one space, then the result of prepending *M* and the following
-    space to the first line of *Ls*, and indenting subsequent lines of
-    *Ls* by *W + 1* spaces, is a list item with *Bs* as its contents.
+    one space of indentation, then the result of prepending *M* and the
+    following space to the first line of *Ls*, and indenting subsequent lines
+    of *Ls* by *W + 1* spaces, is a list item with *Bs* as its contents.
     If a line is empty, then it need not be indented.  The type of the
     list item (bullet or ordered) is determined by the type of its list
     marker.  If the list item is ordered, then it is also assigned a
     start number, based on the ordered list marker.
 
-An indented code block will have to be indented four spaces beyond
-the edge of the region where text will be included in the list item.
+An indented code block will have to be indented four spaces of indentation
+beyond the edge of the region where text will be included in the list item.
 In the following case that is 6 spaces:
 
 ```````````````````````````````` example
@@ -4454,8 +4448,8 @@ And in this case it is 11 spaces:
 
 
 If the *first* block in the list item is an indented code block,
-then by rule #2, the contents must be indented *one* space after the
-list marker:
+then by rule #2, the contents must be indented *one* spaces of indentation after
+the list marker:
 
 ```````````````````````````````` example
     indented code
@@ -4491,7 +4485,7 @@ paragraph
 ````````````````````````````````
 
 
-Note that an additional space indent is interpreted as space
+Note that an additional space of indentation is interpreted as space
 inside the code block:
 
 ```````````````````````````````` example
@@ -4515,10 +4509,10 @@ inside the code block:
 
 Note that rules #1 and #2 only apply to two cases:  (a) cases
 in which the lines to be included in a list item begin with a
-[non-whitespace character], and (b) cases in which
+characer other than a space or tab, and (b) cases in which
 they begin with an indented code
 block.  In a case like the following, where the first block begins with
-a three-space indent, the rules do not allow us to form a list item by
+a three spaces of indentation, the rules do not allow us to form a list item by
 indenting the whole thing and prepending a list marker:
 
 ```````````````````````````````` example
@@ -4544,7 +4538,7 @@ bar
 
 
 This is not a significant restriction, because when a block begins
-with 1-3 spaces indent, the indentation can always be removed without
+with 1-3 spaces of indentation, the indentation can always be removed without
 a change in interpretation, allowing rule #1 to be applied.  So, in
 the above case:
 
@@ -4566,8 +4560,8 @@ the above case:
     starting with a single [blank line] constitute a (possibly empty)
     sequence of blocks *Bs*, and *M* is a list marker of width *W*,
     then the result of prepending *M* to the first line of *Ls*, and
-    indenting subsequent lines of *Ls* by *W + 1* spaces, is a list
-    item with *Bs* as its contents.
+    indenting subsequent lines of *Ls* by *W + 1* spaces of indentation, is a
+    list item with *Bs* as its contents.
     If a line is empty, then it need not be indented.  The type of the
     list item (bullet or ordered) is determined by the type of its list
     marker.  If the list item is ordered, then it is also assigned a
@@ -4642,7 +4636,7 @@ Here is an empty bullet list item:
 ````````````````````````````````
 
 
-It does not matter whether there are spaces following the [list marker]:
+It does not matter whether there are spaces or tabs following the [list marker]:
 
 ```````````````````````````````` example
 - foo
@@ -4700,8 +4694,8 @@ foo
 
 4.  **Indentation.**  If a sequence of lines *Ls* constitutes a list item
     according to rule #1, #2, or #3, then the result of indenting each line
-    of *Ls* by 1-3 spaces (the same for each line) also constitutes a
-    list item with the same contents and attributes.  If a line is
+    of *Ls* by 1-3 spaces of indentation (the same for each line) also
+    constitutes a list item with the same contents and attributes.  If a line is
     empty, then it need not be indented.
 
 Indented one space:
@@ -4800,7 +4794,7 @@ Four spaces indent gives a code block:
 5.  **Laziness.**  If a string of lines *Ls* constitute a [list
     item](#list-items) with contents *Bs*, then the result of deleting
     some or all of the indentation from one or more lines in which the
-    next [non-whitespace character] after the indentation is
+    next character other than a space or tab after the indentation is
     [paragraph continuation text] is a
     list item with the same contents and attributes.  The unindented
     lines are called
@@ -4885,7 +4879,7 @@ continued here.

 
 The rules for sublists follow from the general rules
 [above][List items].  A sublist must be indented the same number
-of spaces a paragraph would need to be in order to be included
+of spaces of indentation a paragraph would need to be in order to be included
 in the list item.
 
 So, in this case we need two spaces indent:
@@ -5512,7 +5506,7 @@ item:
 ````````````````````````````````
 
 Note, however, that list items may not be indented more than
-three spaces.  Here `- e` is treated as a paragraph continuation
+three spaces of indentation.  Here `- e` is treated as a paragraph continuation
 line, because it is indented more than three spaces:
 
 ```````````````````````````````` example
@@ -5598,7 +5592,7 @@ So is this, with a empty second item:
 ````````````````````````````````
 
 
-These are loose lists, even though there is no space between the items,
+These are loose lists, even though there are no blank lines between the items,
 because one of the items directly contains two block-level elements
 with a blank line between them:
 
@@ -6883,7 +6877,7 @@ emphasis sections in this example:
 
 The same condition ensures that the following
 cases are all strong emphasis nested inside
-emphasis, even when the interior spaces are
+emphasis, even when the interior whitespace is
 omitted:
 
 
@@ -7465,7 +7459,7 @@ A [link destination](@) consists of either
 
 - a nonempty sequence of characters that does not start with `<`,
   does not include [ASCII control characters][ASCII control character]
-  or [whitespace][], and includes parentheses only if (a) they are
+  or or [space] character, and includes parentheses only if (a) they are
   backslash-escaped or (b) they are part of a balanced pair of
   unescaped parentheses.
   (Implementations may impose limits on parentheses nesting to
@@ -7490,10 +7484,11 @@ Although [link titles] may span multiple lines, they may not contain
 a [blank line].
 
 An [inline link](@) consists of a [link text] followed immediately
-by a left parenthesis `(`, optional [whitespace], an optional
-[link destination], an optional [link title] separated from the link
-destination by [whitespace], optional [whitespace], and a right
-parenthesis `)`. The link's text consists of the inlines contained
+by a left parenthesis `(`, optional spaces, tabs, and up to one line ending,
+an optional [link destination], an optional [link title] separated from the link
+destination by spaces, tabs, and up to one line ending, optional spaces, tabs,
+and up to one line ending, and a right parenthesis `)`.
+The link's text consists of the inlines contained
 in the [link text] (excluding the enclosing square brackets).
 The link's URI consists of the link destination, excluding enclosing
 `<...>` if present, with backslash-escapes in effect as described
@@ -7561,7 +7556,7 @@ enclosed in pointy brackets:
 
link

 ````````````````````````````````
 
-The destination cannot contain line breaks,
+The destination cannot contain line endings,
 even if enclosed in pointy brackets:
 
 ```````````````````````````````` example
@@ -7736,7 +7731,8 @@ may be used in titles:
 ````````````````````````````````
 
 
-Titles must be separated from the link using a [whitespace].
+Titles must be separated from the link using spaces, tabs, and up to one line
+ending.
 Other [Unicode whitespace] like non-breaking space doesn't work.
 
 ```````````````````````````````` example
@@ -7779,7 +7775,8 @@ titles with no closing quotation mark, though 1.0.2b8 does not.
 It seems preferable to adopt a simple, rational rule that works
 the same way in inline links and link reference definitions.)
 
-[Whitespace] is allowed around the destination and title:
+Spaces, tabs, and up to one line ending is allowed around the destination and
+title:
 
 ```````````````````````````````` example
 [link](   /uri
@@ -7930,7 +7927,8 @@ that [matches] a [link reference definition] elsewhere in the document.
 
 A [link label](@)  begins with a left bracket (`[`) and ends
 with the first right bracket (`]`) that is not backslash-escaped.
-Between these brackets there must be at least one [non-whitespace character].
+Between these brackets there must be at least one character that is not a space,
+tab, or line ending.
 Unescaped square bracket characters are not allowed inside the
 opening and closing square brackets of [link labels].  A link
 label can have at most 999 characters inside the square
@@ -7940,8 +7938,8 @@ One label [matches](@)
 another just in case their normalized forms are equal.  To normalize a
 label, strip off the opening and closing brackets,
 perform the *Unicode case fold*, strip leading and trailing
-[whitespace] and collapse consecutive internal
-[whitespace] to a single space.  If there are multiple
+spaces, tabs, and line endings, and collapse consecutive internal
+spaces, tabs, and line endings to a single space.  If there are multiple
 matching reference link definitions, the one that comes first in the
 document is used.  (It is desirable in such cases to emit a warning.)
 
@@ -8099,7 +8097,7 @@ Unicode case fold is used:
 ````````````````````````````````
 
 
-Consecutive internal [whitespace] is treated as one space for
+Consecutive internal spaces, tabs, and line endings, is treated as one space for
 purposes of determining matching:
 
 ```````````````````````````````` example
@@ -8112,7 +8110,7 @@ purposes of determining matching:
 ````````````````````````````````
 
 
-No [whitespace] is allowed between the [link text] and the
+No spaces, tabs, or line endings, are allowed between the [link text] and the
 [link label]:
 
 ```````````````````````````````` example
@@ -8242,7 +8240,8 @@ Note that in this example `]` is not backslash-escaped:
 ````````````````````````````````
 
 
-A [link label] must contain at least one [non-whitespace character]:
+A [link label] must contain at least one character that is not a space, tab, or
+line ending:
 
 ```````````````````````````````` example
 []
@@ -8307,7 +8306,7 @@ The link labels are case-insensitive:
 
 
 
-As with full reference links, [whitespace] is not
+As with full reference links, spaces, tabs, or line endings are not
 allowed between the two sets of brackets:
 
 ```````````````````````````````` example
@@ -8635,7 +8634,7 @@ The labels are case-insensitive:
 ````````````````````````````````
 
 
-As with reference links, [whitespace] is not allowed
+As with reference links, spaces, tabs, and line endings, are not allowed
 between the two sets of brackets:
 
 ```````````````````````````````` example
@@ -8729,7 +8728,7 @@ a link to the URI, with the URI as the link's label.
 An [absolute URI](@),
 for these purposes, consists of a [scheme] followed by a colon (`:`)
 followed by zero or more characters other [ASCII control
-characters][ASCII control character] or [whitespace][] , `<`, and `>`.
+characters][ASCII control character], [space], `<`, and `>`.
 If the URI includes these characters, they must be percent-encoded
 (e.g. `%20` for a space).
 
@@ -8916,7 +8915,7 @@ A [tag name](@) consists of an ASCII letter
 followed by zero or more ASCII letters, digits, or
 hyphens (`-`).
 
-An [attribute](@) consists of [whitespace],
+An [attribute](@) consists of spaces, tabs, and up to one line ending,
 an [attribute name], and an optional
 [attribute value specification].
 
@@ -8926,9 +8925,9 @@ letters, digits, `_`, `.`, `:`, or `-`.  (Note:  This is the XML
 specification restricted to ASCII.  HTML5 is laxer.)
 
 An [attribute value specification](@)
-consists of optional [whitespace],
-a `=` character, optional [whitespace], and an [attribute
-value].
+consists of optional spaces, tabs, and up to one line ending,
+a `=` character, optional spaces, tabs, and up to one line ending,
+and an [attribute value].
 
 An [attribute value](@)
 consists of an [unquoted attribute value],
@@ -8936,7 +8935,7 @@ a [single-quoted attribute value], or a [double-quoted attribute value].
 
 An [unquoted attribute value](@)
 is a nonempty string of characters not
-including [whitespace], `"`, `'`, `=`, `<`, `>`, or `` ` ``.
+including spaces, tabs, line endings, `"`, `'`, `=`, `<`, `>`, or `` ` ``.
 
 A [single-quoted attribute value](@)
 consists of `'`, zero or more
@@ -8947,11 +8946,12 @@ consists of `"`, zero or more
 characters not including `"`, and a final `"`.
 
 An [open tag](@) consists of a `<` character, a [tag name],
-zero or more [attributes], optional [whitespace], an optional `/`
-character, and a `>` character.
+zero or more [attributes], optional spaces, tabs, and up to one line ending,
+an optional `/` character, and a `>` character.
 
 A [closing tag](@) consists of the string ``.
+[tag name], optional spaces, tabs, and up to one line ending, and the character
+`>`.
 
 An [HTML comment](@) consists of ``,
 where *text* does not start with `>` or `->`, does not end with `-`,
@@ -8992,7 +8992,7 @@ Empty elements:
 ````````````````````````````````
 
 
-[Whitespace] is allowed:
+Whitespace is allowed:
 
 ```````````````````````````````` example
 <
@@ -9065,7 +9065,7 @@ bim!bop />

 ````````````````````````````````
 
 
-Missing [whitespace]:
+Missing whitespace:
 
 ```````````````````````````````` example
 
@@ -9192,7 +9192,7 @@ baz

 
 
 For a more visible alternative, a backslash before the
-[line ending] may be used instead of two spaces:
+[line ending] may be used instead of two or more spaces:
 
 ```````````````````````````````` example
 foo\

From 3cad3060c9ab1fab992f35e21508367c8bdf829c Mon Sep 17 00:00:00 2001
From: Titus Wormer 
Date: Wed, 2 Oct 2019 10:00:47 +0200
Subject: [PATCH 05/21] Rename `Punctuation` to `Unicode punctuation`

---
 spec.txt | 22 +++++++++++-----------
 1 file changed, 11 insertions(+), 11 deletions(-)

diff --git a/spec.txt b/spec.txt
index b8abdee2..b33c8fb6 100644
--- a/spec.txt
+++ b/spec.txt
@@ -327,7 +327,7 @@ is `!`, `"`, `#`, `$`, `%`, `&`, `'`, `(`, `)`,
 `[`, `\`, `]`, `^`, `_`, `` ` `` (U+005B–0060), 
 `{`, `|`, `}`, or `~` (U+007B–007E).
 
-A [punctuation character](@) is an [ASCII
+A [Unicode punctuation character](@) is an [ASCII
 punctuation character] or anything in
 the general Unicode categories  `Pc`, `Pd`, `Pe`, `Pf`, `Pi`, `Po`, or `Ps`.
 
@@ -6129,17 +6129,17 @@ a non-backslash-escaped `_` character.
 
 A [left-flanking delimiter run](@) is
 a [delimiter run] that is (1) not followed by [Unicode whitespace],
-and either (2a) not followed by a [punctuation character], or
-(2b) followed by a [punctuation character] and
-preceded by [Unicode whitespace] or a [punctuation character].
+and either (2a) not followed by a [Unicode punctuation character], or
+(2b) followed by a [Unicode punctuation character] and
+preceded by [Unicode whitespace] or a [Unicode punctuation character].
 For purposes of this definition, the beginning and the end of
 the line count as Unicode whitespace.
 
 A [right-flanking delimiter run](@) is
 a [delimiter run] that is (1) not preceded by [Unicode whitespace],
-and either (2a) not preceded by a [punctuation character], or
-(2b) preceded by a [punctuation character] and
-followed by [Unicode whitespace] or a [punctuation character].
+and either (2a) not preceded by a [Unicode punctuation character], or
+(2b) preceded by a [Unicode punctuation character] and
+followed by [Unicode whitespace] or a [Unicode punctuation character].
 For purposes of this definition, the beginning and the end of
 the line count as Unicode whitespace.
 
@@ -6194,7 +6194,7 @@ The following rules define emphasis and strong emphasis:
     it is part of a [left-flanking delimiter run]
     and either (a) not part of a [right-flanking delimiter run]
     or (b) part of a [right-flanking delimiter run]
-    preceded by punctuation.
+    preceded by Unicode punctuation.
 
 3.  A single `*` character [can close emphasis](@)
     iff it is part of a [right-flanking delimiter run].
@@ -6203,7 +6203,7 @@ The following rules define emphasis and strong emphasis:
     it is part of a [right-flanking delimiter run]
     and either (a) not part of a [left-flanking delimiter run]
     or (b) part of a [left-flanking delimiter run]
-    followed by punctuation.
+    followed by Unicode punctuation.
 
 5.  A double `**` [can open strong emphasis](@)
     iff it is part of a [left-flanking delimiter run].
@@ -6212,7 +6212,7 @@ The following rules define emphasis and strong emphasis:
     it is part of a [left-flanking delimiter run]
     and either (a) not part of a [right-flanking delimiter run]
     or (b) part of a [right-flanking delimiter run]
-    preceded by punctuation.
+    preceded by Unicode punctuation.
 
 7.  A double `**` [can close strong emphasis](@)
     iff it is part of a [right-flanking delimiter run].
@@ -6221,7 +6221,7 @@ The following rules define emphasis and strong emphasis:
     it is part of a [right-flanking delimiter run]
     and either (a) not part of a [left-flanking delimiter run]
     or (b) part of a [left-flanking delimiter run]
-    followed by punctuation.
+    followed by Unicode punctuation.
 
 9.  Emphasis begins with a delimiter that [can open emphasis] and ends
     with a delimiter that [can close emphasis], and that uses the same

From f8fc3dfedf94c56529deccd265c859b2101c6e77 Mon Sep 17 00:00:00 2001
From: Titus Wormer 
Date: Wed, 2 Oct 2019 10:09:56 +0200
Subject: [PATCH 06/21] Reorder unicode whitespace

---
 spec.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/spec.txt b/spec.txt
index b33c8fb6..afeed220 100644
--- a/spec.txt
+++ b/spec.txt
@@ -308,7 +308,7 @@ The following definitions of character classes will be used in this spec:
 
 A [Unicode whitespace character](@) is
 any code point in the Unicode `Zs` general category, or a tab (`U+0009`),
-carriage return (`U+000D`), line feed (`U+000A`), or form feed (`U+000C`).
+line feed (`U+000A`), form feed (`U+000C`), or carriage return (`U+000D`).
 
 [Unicode whitespace](@) is a sequence of one or more
 [Unicode whitespace characters].

From 60500961787a2dc9cf3766f5a56eb9d572a99152 Mon Sep 17 00:00:00 2001
From: Titus Wormer 
Date: Wed, 2 Oct 2019 10:16:22 +0200
Subject: [PATCH 07/21] Reword line breaks

---
 spec.txt | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/spec.txt b/spec.txt
index afeed220..cc89d51d 100644
--- a/spec.txt
+++ b/spec.txt
@@ -1465,7 +1465,7 @@ Foo
 ````````````````````````````````
 
 
-Trailing spaces or tabs in the content line do not cause a line break:
+Trailing spaces or tabs in the content line do not cause a hard line break:
 
 ```````````````````````````````` example
 Foo  
@@ -7454,7 +7454,7 @@ following rules apply:
 A [link destination](@) consists of either
 
 - a sequence of zero or more characters between an opening `<` and a
-  closing `>` that contains no line breaks or unescaped
+  closing `>` that contains no line endings or unescaped
   `<` or `>` characters, or
 
 - a nonempty sequence of characters that does not start with `<`,
@@ -9177,7 +9177,7 @@ foo 
 
 ## Hard line breaks
 
-A line break (not in a code span or HTML tag) that is preceded
+A line ending (not in a code span or HTML tag) that is preceded
 by two or more spaces and does not occur at the end of a block
 is parsed as a [hard line break](@) (rendered
 in HTML as a `
` tag):
@@ -9234,7 +9234,7 @@ bar

 ````````````````````````````````
 
 
-Line breaks can occur inside emphasis, links, and other constructs
+Hard line breaks can occur inside emphasis, links, and other constructs
 that allow inline content:
 
 ```````````````````````````````` example
@@ -9255,7 +9255,7 @@ bar

 ````````````````````````````````
 
 
-Line breaks do not occur inside code spans
+Hard line breaks do not occur inside code spans
 
 ```````````````````````````````` example
 `code 
@@ -9327,9 +9327,9 @@ foo
 
 ## Soft line breaks
 
-A regular line break (not in a code span or HTML tag) that is not
+A regular line ending (not in a code span or HTML tag) that is not
 preceded by two or more spaces or a backslash is parsed as a
-[softbreak](@).  (A softbreak may be rendered in HTML either as a
+[softbreak](@).  (A soft line break may be rendered in HTML either as a
 [line ending] or as a space. The result will be the same in
 browsers. In the examples here, a [line ending] will be used.)
 
@@ -9355,7 +9355,7 @@ baz

 
 
 A conforming parser may render a soft line break in HTML either as a
-line break or as a space.
+line ending or as a space.
 
 A renderer may also provide an option to render soft line breaks
 as hard line breaks.

From 1ca7e304ff45239a6336d2c8203066b9390b9a67 Mon Sep 17 00:00:00 2001
From: Titus 
Date: Thu, 3 Oct 2019 20:04:59 +0200
Subject: [PATCH 08/21] Update spec.txt
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Co-Authored-By: Johel Ernesto Guerrero Peña 
---
 spec.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/spec.txt b/spec.txt
index cc89d51d..57fbf6c8 100644
--- a/spec.txt
+++ b/spec.txt
@@ -1092,7 +1092,7 @@ opening sequence of 1--6 unescaped `#` characters and an optional
 closing sequence of any number of unescaped `#` characters.
 The opening sequence of `#` characters must be followed by spaces or tabs, or
 by the end of line. The optional closing sequence of `#`s must be preceded by
-spaces or tabs space and may be followed by spaces or tabs only.  The opening
+spaces or tabs and may be followed by spaces or tabs only.  The opening
 `#` character may be indented 0-3 spaces of indentation.  The raw contents of
 the heading are stripped of leading and trailing space or tabs before being
 parsed as inline content.  The heading level is equal to the number of `#`

From 355b8de5a0bb9e23d48aeb918d55e2ad35d4887a Mon Sep 17 00:00:00 2001
From: Titus 
Date: Thu, 3 Oct 2019 20:06:29 +0200
Subject: [PATCH 09/21] Update spec.txt
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Co-Authored-By: Johel Ernesto Guerrero Peña 
---
 spec.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/spec.txt b/spec.txt
index 57fbf6c8..fa95f0d9 100644
--- a/spec.txt
+++ b/spec.txt
@@ -3348,7 +3348,7 @@ bar
 
 
 This is not a link reference definition, because there are
-characters other than tabs or spaces after the title:
+characters other than spaces or tabs after the title:
 
 ```````````````````````````````` example
 [foo]: /url "title" ok

From 7a9b2d313612770697d8647258fcb8d74b6a1a6e Mon Sep 17 00:00:00 2001
From: Titus 
Date: Thu, 3 Oct 2019 20:07:10 +0200
Subject: [PATCH 10/21] Update spec.txt
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Co-Authored-By: Johel Ernesto Guerrero Peña 
---
 spec.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/spec.txt b/spec.txt
index fa95f0d9..fd5ffac8 100644
--- a/spec.txt
+++ b/spec.txt
@@ -4055,7 +4055,7 @@ baz

 
 When including an indented code block in a block quote,
 remember that the [block quote marker] includes
-both the `>` and a following spaces of indentation.  So *five spaces* are needed
+both the `>` and a following space of indentation.  So *five spaces* are needed
 after the `>`:
 
 ```````````````````````````````` example

From 921870d2897b31baa08d971f099c0c4fc7970f1f Mon Sep 17 00:00:00 2001
From: Titus 
Date: Thu, 3 Oct 2019 20:08:02 +0200
Subject: [PATCH 11/21] Update spec.txt
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Co-Authored-By: Johel Ernesto Guerrero Peña 
---
 spec.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/spec.txt b/spec.txt
index fd5ffac8..08588e53 100644
--- a/spec.txt
+++ b/spec.txt
@@ -4271,7 +4271,7 @@ far enough past the blockquote marker:
 ````````````````````````````````
 
 
-Note that at least one spaces or tab is needed between the list marker and
+Note that at least one space or tab is needed between the list marker and
 any following content, so these are not list items:
 
 ```````````````````````````````` example

From 35161baffc40bc7d16afc5d9994723b22175c214 Mon Sep 17 00:00:00 2001
From: Titus 
Date: Thu, 3 Oct 2019 20:08:24 +0200
Subject: [PATCH 12/21] Update spec.txt
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Co-Authored-By: Johel Ernesto Guerrero Peña 
---
 spec.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/spec.txt b/spec.txt
index 08588e53..c086ad61 100644
--- a/spec.txt
+++ b/spec.txt
@@ -4448,7 +4448,7 @@ And in this case it is 11 spaces:
 
 
 If the *first* block in the list item is an indented code block,
-then by rule #2, the contents must be indented *one* spaces of indentation after
+then by rule #2, the contents must be indented *one* space of indentation after
 the list marker:
 
 ```````````````````````````````` example

From 7c20cb236135d55038a48c5da672666ab6c3910b Mon Sep 17 00:00:00 2001
From: Titus 
Date: Thu, 3 Oct 2019 20:08:54 +0200
Subject: [PATCH 13/21] Update spec.txt
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Co-Authored-By: Johel Ernesto Guerrero Peña 
---
 spec.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/spec.txt b/spec.txt
index c086ad61..7f4d7b37 100644
--- a/spec.txt
+++ b/spec.txt
@@ -7459,7 +7459,7 @@ A [link destination](@) consists of either
 
 - a nonempty sequence of characters that does not start with `<`,
   does not include [ASCII control characters][ASCII control character]
-  or or [space] character, and includes parentheses only if (a) they are
+  or [space] character, and includes parentheses only if (a) they are
   backslash-escaped or (b) they are part of a balanced pair of
   unescaped parentheses.
   (Implementations may impose limits on parentheses nesting to

From f3347069d29e89c817dfa11112314ece3c2b24d5 Mon Sep 17 00:00:00 2001
From: Titus 
Date: Thu, 3 Oct 2019 20:10:15 +0200
Subject: [PATCH 14/21] Apply suggestions from code review
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Co-Authored-By: Johel Ernesto Guerrero Peña 
---
 spec.txt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/spec.txt b/spec.txt
index 7f4d7b37..60b06fb2 100644
--- a/spec.txt
+++ b/spec.txt
@@ -8097,7 +8097,7 @@ Unicode case fold is used:
 ````````````````````````````````
 
 
-Consecutive internal spaces, tabs, and line endings, is treated as one space for
+Consecutive internal spaces, tabs, and line endings are treated as one space for
 purposes of determining matching:
 
 ```````````````````````````````` example
@@ -8110,7 +8110,7 @@ purposes of determining matching:
 ````````````````````````````````
 
 
-No spaces, tabs, or line endings, are allowed between the [link text] and the
+No spaces, tabs, or line endings are allowed between the [link text] and the
 [link label]:
 
 ```````````````````````````````` example

From 9ca9c615cf5ad55794c4a90c4e2ef2e98632b891 Mon Sep 17 00:00:00 2001
From: Titus Wormer 
Date: Wed, 30 Oct 2019 16:16:49 +0100
Subject: [PATCH 15/21] Link unicode punctuation

---
 spec.txt | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/spec.txt b/spec.txt
index 60b06fb2..e52920ad 100644
--- a/spec.txt
+++ b/spec.txt
@@ -6194,7 +6194,7 @@ The following rules define emphasis and strong emphasis:
     it is part of a [left-flanking delimiter run]
     and either (a) not part of a [right-flanking delimiter run]
     or (b) part of a [right-flanking delimiter run]
-    preceded by Unicode punctuation.
+    preceded by a [Unicode punctuation character].
 
 3.  A single `*` character [can close emphasis](@)
     iff it is part of a [right-flanking delimiter run].
@@ -6203,7 +6203,7 @@ The following rules define emphasis and strong emphasis:
     it is part of a [right-flanking delimiter run]
     and either (a) not part of a [left-flanking delimiter run]
     or (b) part of a [left-flanking delimiter run]
-    followed by Unicode punctuation.
+    followed by a [Unicode punctuation character].
 
 5.  A double `**` [can open strong emphasis](@)
     iff it is part of a [left-flanking delimiter run].
@@ -6212,7 +6212,7 @@ The following rules define emphasis and strong emphasis:
     it is part of a [left-flanking delimiter run]
     and either (a) not part of a [right-flanking delimiter run]
     or (b) part of a [right-flanking delimiter run]
-    preceded by Unicode punctuation.
+    preceded by a [Unicode punctuation character].
 
 7.  A double `**` [can close strong emphasis](@)
     iff it is part of a [right-flanking delimiter run].
@@ -6221,7 +6221,7 @@ The following rules define emphasis and strong emphasis:
     it is part of a [right-flanking delimiter run]
     and either (a) not part of a [left-flanking delimiter run]
     or (b) part of a [left-flanking delimiter run]
-    followed by Unicode punctuation.
+    followed by a [Unicode punctuation character].
 
 9.  Emphasis begins with a delimiter that [can open emphasis] and ends
     with a delimiter that [can close emphasis], and that uses the same

From f9bd1fa71f074bafb65c6cdbb189b83db1fa446e Mon Sep 17 00:00:00 2001
From: Titus Wormer 
Date: Wed, 30 Oct 2019 16:24:48 +0100
Subject: [PATCH 16/21] Clarrify link whitespace by describing `link
 information`

---
 spec.txt | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/spec.txt b/spec.txt
index e52920ad..5acedb4e 100644
--- a/spec.txt
+++ b/spec.txt
@@ -7485,9 +7485,12 @@ a [blank line].
 
 An [inline link](@) consists of a [link text] followed immediately
 by a left parenthesis `(`, optional spaces, tabs, and up to one line ending,
-an optional [link destination], an optional [link title] separated from the link
-destination by spaces, tabs, and up to one line ending, optional spaces, tabs,
-and up to one line ending, and a right parenthesis `)`.
+optional link information, and a right parenthesis `)`.
+Link information consists of a [link destination], an optional [link title], and
+optional spaces, tabs, and up to one line ending.
+If a title is present, it must be separated from the link destination by spaces,
+tabs, and up to one line ending.
+
 The link's text consists of the inlines contained
 in the [link text] (excluding the enclosing square brackets).
 The link's URI consists of the link destination, excluding enclosing

From 10ca5cc37aaf700debd4e5aa6b903637687a6ba1 Mon Sep 17 00:00:00 2001
From: Titus Wormer 
Date: Wed, 30 Oct 2019 17:08:54 +0100
Subject: [PATCH 17/21] Clarrify link destination and title

---
 spec.txt | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/spec.txt b/spec.txt
index 5acedb4e..58a540d7 100644
--- a/spec.txt
+++ b/spec.txt
@@ -7484,12 +7484,12 @@ Although [link titles] may span multiple lines, they may not contain
 a [blank line].
 
 An [inline link](@) consists of a [link text] followed immediately
-by a left parenthesis `(`, optional spaces, tabs, and up to one line ending,
-optional link information, and a right parenthesis `)`.
-Link information consists of a [link destination], an optional [link title], and
-optional spaces, tabs, and up to one line ending.
-If a title is present, it must be separated from the link destination by spaces,
-tabs, and up to one line ending.
+by a left parenthesis `(`, an optional [link destination], an optional
+[link title], and a right parenthesis `)`.
+These four components may be separated by spaces, tabs, and up to one line
+ending.
+If both [link destination] and [link title] are present, they *must* be
+separated by spaces, tabs, and up to one line ending.
 
 The link's text consists of the inlines contained
 in the [link text] (excluding the enclosing square brackets).

From a18f88078940abd585165f05b86aee0094d7efd1 Mon Sep 17 00:00:00 2001
From: Titus Wormer 
Date: Tue, 19 May 2020 16:09:11 +0200
Subject: [PATCH 18/21] Remove duplicate indentations

---
 spec.txt | 39 ++++++++++++++++++++-------------------
 1 file changed, 20 insertions(+), 19 deletions(-)

diff --git a/spec.txt b/spec.txt
index 58a540d7..f37e4838 100644
--- a/spec.txt
+++ b/spec.txt
@@ -1093,7 +1093,7 @@ closing sequence of any number of unescaped `#` characters.
 The opening sequence of `#` characters must be followed by spaces or tabs, or
 by the end of line. The optional closing sequence of `#`s must be preceded by
 spaces or tabs and may be followed by spaces or tabs only.  The opening
-`#` character may be indented 0-3 spaces of indentation.  The raw contents of
+`#` character may be preceded by 1-3 spaces of indentation.  The raw contents of
 the heading are stripped of leading and trailing space or tabs before being
 parsed as inline content.  The heading level is equal to the number of `#`
 characters in the opening sequence.
@@ -1320,7 +1320,7 @@ interpretable as a [code fence], [ATX heading][ATX headings],
 
 A [setext heading underline](@) is a sequence of
 `=` characters or a sequence of `-` characters, with no more than 3
-spaces of indentation and any number of trailing space or tabs.  If a line
+spaces of indentation and any number of trailing spaces or tabs.  If a line
 containing a single `-` can be interpreted as an
 empty [list items], it should be interpreted this way
 and not as a [setext heading underline].
@@ -1390,8 +1390,8 @@ Foo
 ````````````````````````````````
 
 
-The heading content can be indented up to three spaces of indentation, and need
-not line up with the underlining:
+The heading content can be preceded by up to three spaces of indentation, and
+need not line up with the underlining:
 
 ```````````````````````````````` example
    Foo
@@ -1427,8 +1427,8 @@ Foo
 ````````````````````````````````
 
 
-The setext heading underline can be indented up to three spaces of indentation,
-and may have trailing spaces or tabs:
+The setext heading underline can be preceded by up to three spaces of
+indentation, and may have trailing spaces or tabs:
 
 ```````````````````````````````` example
 Foo
@@ -1887,7 +1887,7 @@ Heading
 ````````````````````````````````
 
 
-The first line can be indented more than four spaces of indentation:
+The first line can be preceded by more than four spaces of indentation:
 
 ```````````````````````````````` example
         foo
@@ -1931,7 +1931,7 @@ A [code fence](@) is a sequence
 of at least three consecutive backtick characters (`` ` ``) or
 tildes (`~`).  (Tildes and backticks cannot be mixed.)
 A [fenced code block](@)
-begins with a code fence, indented no more than three spaces of indentation.
+begins with a code fence, preceded by no more than three spaces of indentation.
 
 The line with the opening code fence may optionally contain some text
 following the code fence; this is trimmed of leading and trailing
@@ -1945,12 +1945,12 @@ The content of the code block consists of all subsequent lines, until
 a closing [code fence] of the same type as the code block
 began with (backticks or tildes), and with at least as many backticks
 or tildes as the opening code fence.  If the leading code fence is
-indented N spaces of indentation, then up to N spaces of indentation are removed
-from each line of the content (if present).  (If a content line is not
+preceded by N spaces of indentation, then up to N spaces of indentation are
+removed from each line of the content (if present).  (If a content line is not
 indented, it is preserved unchanged.  If it is indented N spaces or less, all
 of the indentation is removed.)
 
-The closing code fence may be indented up to three spaces of indentation, and
+The closing code fence may be preceded by up to three spaces of indentation, and
 may be followed only by spaces or tabs, which are ignored.  If the end of the
 containing block (or document) is reached and no closing code fence
 has been found, the code block contains all of the lines after the
@@ -2178,7 +2178,7 @@ aaa
 ````````````````````````````````
 
 
-Closing fences may be indented by 0-3 spaces of indentation, and their
+Closing fences may be preceded by 1-3 spaces of indentation, and their
 indentation need not match that of the opening fence:
 
 ```````````````````````````````` example
@@ -2938,7 +2938,7 @@ function matchwo(a,b)
 ````````````````````````````````
 
 
-The opening tag can be indented 1-3 spaces of indentation, but not 4:
+The opening tag can be preceded by 1-3 spaces of indentation, but not 4:
 
 ```````````````````````````````` example
   
@@ -3132,7 +3132,8 @@ deleted.  The exception is inside `
` tags, but as described
 ## Link reference definitions
 
 A [link reference definition](@)
-consists of a [link label], indented up to three spaces of indentation, followed
+consists of a [link label], optionally preceded by up to three spaces of
+indentation, followed
 by a colon (`:`), optional spaces or tabs (including up to one
 [line ending]), a [link destination],
 optional spaces or tabs (including up to one
@@ -3567,7 +3568,7 @@ ccc

 ````````````````````````````````
 
 
-However, the first line may be indented at most three spaces of indentation,
+However, the first line may be preceded by at most three spaces of indentation,
 or an indented code block will be triggered:
 
 ```````````````````````````````` example
@@ -3705,7 +3706,7 @@ baz

 ````````````````````````````````
 
 
-The `>` characters can be indented 1-3 spaces of indentation:
+The `>` characters can be preceded by 1-3 spaces of indentation:
 
 ```````````````````````````````` example
    > # Foo
@@ -4411,7 +4412,7 @@ A start number may not be negative:
     marker.  If the list item is ordered, then it is also assigned a
     start number, based on the ordered list marker.
 
-An indented code block will have to be indented four spaces of indentation
+An indented code block will have to be preceded by four spaces of indentation
 beyond the edge of the region where text will be included in the list item.
 In the following case that is 6 spaces:
 
@@ -4512,7 +4513,7 @@ in which the lines to be included in a list item begin with a
 characer other than a space or tab, and (b) cases in which
 they begin with an indented code
 block.  In a case like the following, where the first block begins with
-a three spaces of indentation, the rules do not allow us to form a list item by
+three spaces of indentation, the rules do not allow us to form a list item by
 indenting the whole thing and prepending a list marker:
 
 ```````````````````````````````` example
@@ -5505,7 +5506,7 @@ item:
 
 ````````````````````````````````
 
-Note, however, that list items may not be indented more than
+Note, however, that list items may not be preceded by more than
 three spaces of indentation.  Here `- e` is treated as a paragraph continuation
 line, because it is indented more than three spaces:
 

From 2201adbdaecb229370d05b2562a5bdcb6635bf82 Mon Sep 17 00:00:00 2001
From: Titus Wormer 
Date: Tue, 19 May 2020 16:16:31 +0200
Subject: [PATCH 19/21] Fix two more duplicate indentations

---
 spec.txt | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/spec.txt b/spec.txt
index f37e4838..bf1c3d9c 100644
--- a/spec.txt
+++ b/spec.txt
@@ -1730,8 +1730,8 @@ baz

 An [indented code block](@) is composed of one or more
 [indented chunks] separated by blank lines.
 An [indented chunk](@) is a sequence of non-blank lines,
-each indented four or more spaces of indentation. The contents of the code block
-are the literal contents of the lines, including trailing
+each preceded by four or more spaces of indentation. The contents of the code
+block are the literal contents of the lines, including trailing
 [line endings], minus four spaces of indentation.
 An indented code block has no [info string].
 
@@ -4449,8 +4449,8 @@ And in this case it is 11 spaces:
 
 
 If the *first* block in the list item is an indented code block,
-then by rule #2, the contents must be indented *one* space of indentation after
-the list marker:
+then by rule #2, the contents must be preceded by *one* space of indentation
+after the list marker:
 
 ```````````````````````````````` example
     indented code

From ac533b83337b1cdecfe4aed7b32998339b35558b Mon Sep 17 00:00:00 2001
From: Titus Wormer 
Date: Tue, 19 May 2020 16:29:21 +0200
Subject: [PATCH 20/21] Fix two more duplicate indentations

---
 spec.txt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/spec.txt b/spec.txt
index bf1c3d9c..81578322 100644
--- a/spec.txt
+++ b/spec.txt
@@ -4561,7 +4561,7 @@ the above case:
     starting with a single [blank line] constitute a (possibly empty)
     sequence of blocks *Bs*, and *M* is a list marker of width *W*,
     then the result of prepending *M* to the first line of *Ls*, and
-    indenting subsequent lines of *Ls* by *W + 1* spaces of indentation, is a
+    preceding subsequent lines of *Ls* by *W + 1* spaces of indentation, is a
     list item with *Bs* as its contents.
     If a line is empty, then it need not be indented.  The type of the
     list item (bullet or ordered) is determined by the type of its list
@@ -4694,7 +4694,7 @@ foo
 
 
 4.  **Indentation.**  If a sequence of lines *Ls* constitutes a list item
-    according to rule #1, #2, or #3, then the result of indenting each line
+    according to rule #1, #2, or #3, then the result of preceding each line
     of *Ls* by 1-3 spaces of indentation (the same for each line) also
     constitutes a list item with the same contents and attributes.  If a line is
     empty, then it need not be indented.

From 69abb8164061d12ea3f22f094b1ed8ee4f882c3d Mon Sep 17 00:00:00 2001
From: Titus Wormer 
Date: Sat, 23 May 2020 09:34:45 +0200
Subject: [PATCH 21/21] Do away with ranges and use words instead

---
 spec.txt | 58 +++++++++++++++++++++++++++++---------------------------
 1 file changed, 30 insertions(+), 28 deletions(-)

diff --git a/spec.txt b/spec.txt
index 81578322..7dcfc48e 100644
--- a/spec.txt
+++ b/spec.txt
@@ -862,8 +862,8 @@ Markdown document.
 
 ## Thematic breaks
 
-A line consisting of 0-3 spaces of indentation, followed by a sequence
-of three or more matching `-`, `_`, or `*` characters, each followed
+A line consisting of optionally up to three spaces of indentation, followed by a
+sequence of three or more matching `-`, `_`, or `*` characters, each followed
 optionally by any number of spaces or tabs, forms a
 [thematic break](@).
 
@@ -907,7 +907,7 @@ __

 ````````````````````````````````
 
 
-One to three spaces of indentation are allowed:
+Up to three spaces of indentation are allowed:
 
 ```````````````````````````````` example
  ***
@@ -1093,10 +1093,10 @@ closing sequence of any number of unescaped `#` characters.
 The opening sequence of `#` characters must be followed by spaces or tabs, or
 by the end of line. The optional closing sequence of `#`s must be preceded by
 spaces or tabs and may be followed by spaces or tabs only.  The opening
-`#` character may be preceded by 1-3 spaces of indentation.  The raw contents of
-the heading are stripped of leading and trailing space or tabs before being
-parsed as inline content.  The heading level is equal to the number of `#`
-characters in the opening sequence.
+`#` character may be preceded by up to three spaces of indentation.  The raw
+contents of the heading are stripped of leading and trailing space or tabs
+before being parsed as inline content.  The heading level is equal to the number
+of `#` characters in the opening sequence.
 
 Simple headings:
 
@@ -1171,7 +1171,7 @@ Leading and trailing spaces or tabs are ignored in parsing inline content:
 ````````````````````````````````
 
 
-One to three spaces of indentation are allowed:
+Up to three spaces of indentation are allowed:
 
 ```````````````````````````````` example
  ### foo
@@ -1184,7 +1184,7 @@ One to three spaces of indentation are allowed:
 ````````````````````````````````
 
 
-Four spaces of indentation are too much:
+Four spaces of indentation is too many:
 
 ```````````````````````````````` example
     # foo
@@ -1409,7 +1409,7 @@ need not line up with the underlining:
 ````````````````````````````````
 
 
-Four spaces of indentation is too much:
+Four spaces of indentation is too many:
 
 ```````````````````````````````` example
     Foo
@@ -1438,7 +1438,7 @@ Foo
 ````````````````````````````````
 
 
-Four spaces of indentation is too much:
+Four spaces of indentation is too many:
 
 ```````````````````````````````` example
 Foo
@@ -1931,7 +1931,7 @@ A [code fence](@) is a sequence
 of at least three consecutive backtick characters (`` ` ``) or
 tildes (`~`).  (Tildes and backticks cannot be mixed.)
 A [fenced code block](@)
-begins with a code fence, preceded by no more than three spaces of indentation.
+begins with a code fence, preceded by up to three spaces of indentation.
 
 The line with the opening code fence may optionally contain some text
 following the code fence; this is trimmed of leading and trailing
@@ -2164,7 +2164,7 @@ aaa
 ````````````````````````````````
 
 
-Four spaces of indentation produces an indented code block:
+Four spaces of indentation is too many:
 
 ```````````````````````````````` example
     ```
@@ -2178,7 +2178,7 @@ aaa
 ````````````````````````````````
 
 
-Closing fences may be preceded by 1-3 spaces of indentation, and their
+Closing fences may be preceded by up to three spaces of indentation, and their
 indentation need not match that of the opening fence:
 
 ```````````````````````````````` example
@@ -2938,7 +2938,8 @@ function matchwo(a,b)
 ````````````````````````````````
 
 
-The opening tag can be preceded by 1-3 spaces of indentation, but not 4:
+The opening tag can be preceded by up to three spaces of indentation, but not
+four:
 
 ```````````````````````````````` example
   
@@ -3568,8 +3569,8 @@ ccc

 ````````````````````````````````
 
 
-However, the first line may be preceded by at most three spaces of indentation,
-or an indented code block will be triggered:
+However, the first line may be preceded by up to three spaces of indentation.
+Four spaces of indentation is too many:
 
 ```````````````````````````````` example
    aaa
@@ -3649,10 +3650,11 @@ these constructions.  (A recipe is provided below in the section entitled
 
 ## Block quotes
 
-A [block quote marker](@)
-consists of 0-3 spaces of indentation, plus (a) the character `>` together
-with a following space of indentation, or (b) a single character `>` not
-followed by a space of indentation.
+A [block quote marker](@),
+optionally preceded by up to three spaces of indentation,
+consists of (a) the character `>` together with a following space of
+indentation, or (b) a single character `>` not followed by a space of
+indentation.
 
 The following rules define [block quotes]:
 
@@ -3706,7 +3708,7 @@ baz

 ````````````````````````````````
 
 
-The `>` characters can be preceded by 1-3 spaces of indentation:
+The `>` characters can be preceded by up to three spaces of indentation:
 
 ```````````````````````````````` example
    > # Foo
@@ -3721,7 +3723,7 @@ baz

 ````````````````````````````````
 
 
-Four spaces of indentation gives us a code block:
+Four spaces of indentation is too many:
 
 ```````````````````````````````` example
     > # Foo
@@ -4538,8 +4540,8 @@ bar
 ````````````````````````````````
 
 
-This is not a significant restriction, because when a block begins
-with 1-3 spaces of indentation, the indentation can always be removed without
+This is not a significant restriction, because when a block is preceded by up to
+three spaces of indentation, the indentation can always be removed without
 a change in interpretation, allowing rule #1 to be applied.  So, in
 the above case:
 
@@ -4695,7 +4697,7 @@ foo
 
 4.  **Indentation.**  If a sequence of lines *Ls* constitutes a list item
     according to rule #1, #2, or #3, then the result of preceding each line
-    of *Ls* by 1-3 spaces of indentation (the same for each line) also
+    of *Ls* by up to three spaces of indentation (the same for each line) also
     constitutes a list item with the same contents and attributes.  If a line is
     empty, then it need not be indented.
 
@@ -5113,8 +5115,8 @@ The choice of four spaces is arbitrary.  It can be learned, but it is
 not likely to be guessed, and it trips up beginners regularly.
 
 Would it help to adopt a two-space rule?  The problem is that such
-a rule, together with the rule allowing 1--3 spaces indentation of the
-initial list marker, allows text that is indented *less than* the
+a rule, together with the rule allowing up to three spaces of indentation for
+the initial list marker, allows text that is indented *less than* the
 original list marker to be included in the list item. For example,
 `Markdown.pl` parses