Commit 6cacc7e5 authored by Sarah White's avatar Sarah White Committed by Dan Allen
Browse files

update section titles; replace xref to markdown compatibility (PR #19)

parent 13de5f4c
= AsciiDoc Versus Markdown
= Compare AsciiDoc and Markdown
:description: A brief comparison of AsciiDoc and Markdown.
The most compelling reason to choose a lightweight markup language for writing is to minimize the number of technical concepts an author must grasp in order to be immediately productive.
In other words, the goal is to be able to _write without friction_.
== Getting your start with Markdown
== Starting with Markdown
The defacto lightweight markup language is Markdown.
(At least, Markdown is what you call it at first).
......@@ -460,8 +460,8 @@ NOTE: Certain Markdown flavors, such as Markdown Extra, support additional featu
However, since these features don't appear in "`plain`" Markdown, they're not included in the comparison table.
But they're supported natively by AsciiDoc.
Asciidoctor, which is used for converting AsciiDoc on GitHub and GitLab, emulates "`the good parts`" of the Markdown syntax, like headings, blockquotes and fenced code blocks, making migration from Markdown to AsciiDoc fairly simple.
For details about migration, see #url-home/docs/asciidoc-syntax-quick-reference/#markdown-compatibility[Markdown Compatibility#.
Asciidoctor, which is used for converting AsciiDoc on GitHub and GitLab, emulates some of the common parts of the Markdown syntax, like headings, blockquotes and fenced code blocks, simplifying the migration from Markdown to AsciiDoc.
For details, see xref:syntax-quick-reference.adoc#markdown-compatibility[Markdown compatibility].
////
===== Description Lists in AsciiDoc
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment