80486DX2-66/80486DX2-66
1
0
Fork 0
Code Activity

revolt-bugs: correct grammar

Browse source
This commit is contained in:
Intel A80486DX2-66 2024-01-21 22:46:40 +03:00
parent 3d2996d846
commit dfd14c9809
Signed by: 80486DX2-66
GPG key ID: 83631EF27054609B
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
notepad/revolt-bugs.md
View file

@ -3,7 +3,7 @@
- A no-break space has to be added for empty lines in a multi-line quite to preserve them (or another invisible character except whitespace).
- Empty lines in code blocks have a no-break space character in them. This behavior can break some compilers/interpreters.
- If a backslash is followed by another backslash or some other symbols, it is evaluated.
- If you declare an unordered or ordered list, the rest of it will be treated as either (1) the same list when creating another, or as (2) the content of the last item. A workaround is to use a page break (e.g. `***`) which will mark an end of a list, while it would be rendered as an empty line.
- If you declare an unordered or ordered list, the rest of it will be treated as either (1) the same list when creating another, or (2) the content of the last item. A workaround is to use a page break (e.g. `***`) which will mark an end of a list, while it would be rendered as an empty line.
- In code blocks, after a sequence of one or multiple lines starting with `>`, an empty line is added.
- Page breaks do not work as intended, but are parsed (the characters are removed).
- Some markdown, such as headers without text, is evaluated. It shouldn't be evaluated.