From 15422f68253bd5d877f0b308b1bf6caec6e0eb79 Mon Sep 17 00:00:00 2001
From: John MacFarlane <jgm@berkeley.edu>
Date: Sun, 26 Oct 2014 00:26:38 -0700
Subject: Tweaked the closing fence section added in last commit.

---
 spec.txt | 46 +++++++++++++++-------------------------------
 1 file changed, 15 insertions(+), 31 deletions(-)

(limited to 'spec.txt')

diff --git a/spec.txt b/spec.txt
index c226866..e5953bd 100644
--- a/spec.txt
+++ b/spec.txt
@@ -1288,45 +1288,41 @@ aaa
 </code></pre>
 .
 
-Closing fences may be indented by 0-3 spaces:
+Four spaces indentation produces an indented code block:
 
 .
-```
-code
-```
-.
-<pre><code>code
-</code></pre>
-.
-
+    ```
+    aaa
+    ```
 .
+<pre><code>```
+aaa
 ```
-code
- ```
-.
-<pre><code>code
 </code></pre>
 .
 
+Closing fences may be indented by 0-3 spaces, and their indentation
+need not match that of the opening fence:
+
 .
 ```
-code
+aaa
   ```
 .
-<pre><code>code
+<pre><code>aaa
 </code></pre>
 .
 
 .
-```
-code
    ```
+aaa
+  ```
 .
-<pre><code>code
+<pre><code>aaa
 </code></pre>
 .
 
-But not by 4:
+This is not a closing fence, because it is indented 4 spaces:
 
 .
 ```
@@ -1338,18 +1334,6 @@ aaa
 </code></pre>
 .
 
-Four spaces indentation produces an indented code block:
-
-.
-    ```
-    aaa
-    ```
-.
-<pre><code>```
-aaa
-```
-</code></pre>
-.
 
 Code fences (opening and closing) cannot contain internal spaces:
 
-- 
cgit v1.2.3