aboutsummaryrefslogtreecommitdiff
path: root/GEMTEXT-COMPATIBILITY.md
diff options
context:
space:
mode:
authorNicholas Johnson <nick@nicholasjohnson.ch>2023-05-08 00:00:00 +0000
committerNicholas Johnson <nick@nicholasjohnson.ch>2023-05-08 00:00:00 +0000
commit7a47ff5e8775f0235f1f13e59375aa46b5d869706592c70c012eae7905416758 (patch)
tree6747cb239d6ccbcbc0f3323f611551b52c1ac4e85c1866050d2cd14d87cea29c /GEMTEXT-COMPATIBILITY.md
parent3549c979d995ffc395a8cf848300f999a3678d06e6bba0033d1618d02c25b0e8 (diff)
Correct documentationv0.5.1
Diffstat (limited to 'GEMTEXT-COMPATIBILITY.md')
-rw-r--r--GEMTEXT-COMPATIBILITY.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/GEMTEXT-COMPATIBILITY.md b/GEMTEXT-COMPATIBILITY.md
index 35ca34d..3e206a4 100644
--- a/GEMTEXT-COMPATIBILITY.md
+++ b/GEMTEXT-COMPATIBILITY.md
@@ -45,7 +45,7 @@ Newlines are partially supported. Line breaks are unsupported.
Explanation:
-The gemtext renderer and HTML renderer handle whitespace differently. While whitespace has special meaning in Markdown, the gemtext renderer simply copies it unmodified into the output. It is possible to achieve consecutive newlines in the HTML, but the gemtext won't render it correctly. For compatibility, always use exactly two literal newlines.
+The gemtext renderer and HTML renderer handle whitespace differently. While whitespace has special meaning in Markdown, the gemtext renderer simply copies it unmodified into the output. It is possible to achieve consecutive newlines in the HTML, but the gemtext won't render it correctly. For compatibility, use exactly two literal newlines except after headings. After headings, just use one newline.
E.g: