[taler-docs] branch master updated: clarify ‘.. include::’ placement in README.md

[gnunet]

This is an automated email from the git hooks/post-receive script.

ttn pushed a commit to branch master
in repository docs.

The following commit(s) were added to refs/heads/master by this push:
     new cc32ee6  clarify ‘.. include::’ placement in README.md
cc32ee6 is described below

commit cc32ee651a54aaf86f95208b37e789be947c4ef3
Author: Thien-Thi Nguyen <ttn@gnuvola.org>
AuthorDate: Fri Dec 11 15:22:18 2020 -0500

    clarify ‘.. include::’ placement in README.md
---
 frags/README.md | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/frags/README.md b/frags/README.md
index 9facc4c..0fe7923 100644
--- a/frags/README.md
+++ b/frags/README.md
@@ -4,7 +4,9 @@ This directory contains fragments to be included by the 
directive:
 
   .. include:: RELATIVE-FILE-NAME
 
-If the fragment includes headers, you MUST include it at top-level.
-Otherwise, you MUST include it only at "block" level.
+If the fragment includes header lines, you MUST include it at top-level
+(no indentation for the directive).
+
+Otherwise, it can be included at either top-level or indented.
 
 See 
<https://docutils.sourceforge.io/docs/ref/rst/directives.html#including-an-external-document-fragment>.

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.