summaryrefslogtreecommitdiffstats
path: root/docs/asciidoc.md
diff options
context:
space:
mode:
authorSoreine <soreine.plume@gmail.com>2016-03-02 11:12:44 +0100
committerSoreine <soreine.plume@gmail.com>2016-03-03 16:39:17 +0100
commite67286c51d96d88ffb8d279dbfd41f3a32de7ce0 (patch)
tree343f0b21274e9cfa98bf03fbcc879892535f3c85 /docs/asciidoc.md
parent603622e3379e1381b7acedf5174ceba656b15285 (diff)
downloadgitbook-e67286c51d96d88ffb8d279dbfd41f3a32de7ce0.zip
gitbook-e67286c51d96d88ffb8d279dbfd41f3a32de7ce0.tar.gz
gitbook-e67286c51d96d88ffb8d279dbfd41f3a32de7ce0.tar.bz2
Reviewing, first part
Diffstat (limited to 'docs/asciidoc.md')
-rw-r--r--docs/asciidoc.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/asciidoc.md b/docs/asciidoc.md
index c04098b..0dfbb41 100644
--- a/docs/asciidoc.md
+++ b/docs/asciidoc.md
@@ -8,11 +8,11 @@ Just like for markdown, GitBook is using some special files to extract structure
### README.adoc
-This is the main entry of your book: the introduction. This file is **non optional**.
+This is the main entry of your book: the introduction. This file is **required**.
### SUMMARY.adoc
-This file defines the list of chapters and subchapters. Just like [for markdown](./pages.md), the `SUMMARY.adoc`'s format is simply a list of links, the name of the link is used as the chapter's name, and the target is a path to that chapter's file.
+This file defines the list of chapters and subchapters. Just like in Markdown, the `SUMMARY.adoc`'s format is simply a list of links, the name of the link is used as the chapter's name, and the target is a path to that chapter's file.
Subchapters are defined simply by adding a nested list to a parent chapter.