summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMatthias Beyer <mail@beyermatthias.de>2019-11-09 17:27:10 +0100
committerMatthias Beyer <mail@beyermatthias.de>2019-12-01 13:03:22 +0100
commite8f3d26a4bf1fd42d55b0c952a838f85d4c53f23 (patch)
tree55ff84a4112432cc4258d98ac2f831fdcc26892d
parenta5d0cd7a745647e6d050799b065fa5016d87108f (diff)
Remove notes on markup implementation as not relevant here
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
-rw-r--r--doc/src/02000-store.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/src/02000-store.md b/doc/src/02000-store.md
index 495ae48a..2bac11db 100644
--- a/doc/src/02000-store.md
+++ b/doc/src/02000-store.md
@@ -63,13 +63,13 @@ read or write other sections than its own.
The content is the part of the file where the user is free to enter any textual
content. The content may be rendered as Markdown or other markup format for the
-users convenience. The store does never expect and specific markup and actually
-the markup implementation is not inside the very core of imag.
+users convenience. The store does never expect any specific markup.
Technically it would be possible that the content part of a file is used to
store binary data.
We don't want this, though, as it is contrary to the goals of imag.
+
### Example {#sec:thestore:fileformat:example}
An example for a file in the store follows.