summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--js/index.html2
-rwxr-xr-xjs/stmd.js2
-rw-r--r--spec.txt20
3 files changed, 12 insertions, 12 deletions
diff --git a/js/index.html b/js/index.html
index 994b147..05fc216 100644
--- a/js/index.html
+++ b/js/index.html
@@ -52,7 +52,7 @@ $(document).ready(function() {
render();
}, 0); // ms delay
};
- $("#text").keyup(parseAndRender);
+ $("#text").bind('keyup paste cut mouseup', parseAndRender);
$(".option").change(render);
});
</script>
diff --git a/js/stmd.js b/js/stmd.js
index 15d7345..4b3d83e 100755
--- a/js/stmd.js
+++ b/js/stmd.js
@@ -1,4 +1,4 @@
-// stmd.js - CommomMark in javascript
+// stmd.js - CommonMark in javascript
// Copyright (C) 2014 John MacFarlane
// License: BSD3.
diff --git a/spec.txt b/spec.txt
index 112dccc..040c060 100644
--- a/spec.txt
+++ b/spec.txt
@@ -1058,7 +1058,7 @@ a blank line either before or after.
The content of a code fence is treated as literal text, not parsed
as inlines. The first word of the info string is typically used to
specify the language of the code sample, and rendered in the `class`
-attribute of the `pre` tag. However, this spec does not mandate any
+attribute of the `code` tag. However, this spec does not mandate any
particular treatment of the info string.
Here is a simple example with backticks:
@@ -1994,11 +1994,11 @@ form of the definition is:
> transforming X in such-and-such a way is a container of type Y
> with these blocks as its content.
-So, we explain what counts as a block quote or list item by
-explaining how these can be *generated* from their contents.
-This should suffice to define the syntax, although it does not
-give a recipe for *parsing* these constructions. (A recipe is
-provided below in the section entitled [A parsing strategy].)
+So, we explain what counts as a block quote or list item by explaining
+how these can be *generated* from their contents. This should suffice
+to define the syntax, although it does not give a recipe for *parsing*
+these constructions. (A recipe is provided below in the section entitled
+[A parsing strategy](#appendix-a-a-parsing-strategy).)
## Block quotes
@@ -2010,9 +2010,9 @@ The following rules define [block quotes](#block-quote):
<a id="block-quote"></a>
1. **Basic case.** If a string of lines *Ls* constitute a sequence
- of blocks *Bs*, then the result of appending a [block quote marker]
- to the beginning of each line in *Ls* is a [block quote](#block-quote)
- containing *Bs*.
+ of blocks *Bs*, then the result of appending a [block quote
+ marker](#block-quote-marker) to the beginning of each line in *Ls*
+ is a [block quote](#block-quote) containing *Bs*.
2. **Laziness.** If a string of lines *Ls* constitute a [block
quote](#block-quote) with contents *Bs*, then the result of deleting
@@ -4041,7 +4041,7 @@ for efficient parsing strategies that do not backtrack:
(a) it is not part of a sequence of four or more unescaped `_`s,
(b) it is not followed by whitespace,
- (c) is is not preceded by an ASCII alphanumeric character, and
+ (c) it is not preceded by an ASCII alphanumeric character, and
(d) either it is not followed by a `_` character or it is
followed immediately by strong emphasis.