cmark

My personal build of CMark ✏️

Commit: 7817cd7edd94b80e3d851189ad1290661e109c7c
Parent: 32fb4068515058748ca78664302ecb1d5124adcb
Author: John MacFarlane <jgm@berkeley.edu>
Date: Sat, 3 Jan 2015 15:10:29 -0800

Make clear that any sequence of characters is a valid document.

Closes #266 in a slightly different way than @anko's PR.

Diffstat

1 file changed, 5 insertions, 5 deletions

Status	File Name	N° Changes	Insertions	Deletions
Modified	spec.txt	10	5	5

diff --git a/spec.txt b/spec.txt
@@ -202,17 +202,17 @@ In the examples, the `→` character is used to represent tabs.
 
 ## Characters and lines
 
-The input is a sequence of zero or more [lines](#line).
-
-A [line](@line)
-is a sequence of zero or more [characters](#character) followed by a
-[line ending](#line-ending) or by the end of file.
+Any sequence of [characters](#character) is a valid CommonMark
+document.
 
 A [character](@character) is a unicode code point.
 This spec does not specify an encoding; it thinks of lines as composed
 of characters rather than bytes.  A conforming parser may be limited
 to a certain encoding.
 
+A [line](@line) is a sequence of zero or more [characters](#character)
+followed by a [line ending](#line-ending) or by the end of file.
+
 A [line ending](@line-ending) is, depending on the platform, a
 newline (`U+000A`), carriage return (`U+000D`), or
 carriage return + newline.