From 8a216b00ef3207dba1438387c6064a97719c8fb3 Mon Sep 17 00:00:00 2001 From: John MacFarlane Date: Sat, 4 Nov 2017 10:30:32 -0700 Subject: [PATCH] Revise clarification on fenced_divs. (#4039) --- MANUAL.txt | 13 +++++-------- 1 file changed, 5 insertions(+), 8 deletions(-) diff --git a/MANUAL.txt b/MANUAL.txt index 085a34234..7edc6b063 100644 --- a/MANUAL.txt +++ b/MANUAL.txt @@ -3119,14 +3119,11 @@ because they *must* have attributes: ::: :::::::::::::::::: -Unlike fenced code blocks, here the exact number of colons in the opening and -closing fences is irrelevant, even when nesting divs: the telltale sign -between opening and closing fences is the presence of attributes, or the lack -thereof. Hence, the number of colons in a closing fence doesn't have to -match that of its opening counterpart, and there is no need to use different -fences lenghts to distinguish a nested div from its parent (except for visual -clarity). - +Fences without attributes are always closing fences. Unlike +with fenced code blocks, the number of colons in the closing +fence need not match the number in the opening fence. However, +it can be helpful for visual clarity to use fences of different +lengths to distinguish nested divs from their parents. #### Extension: `raw_tex` ####