From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: appendices/devbook-guide/
Date: Fri, 25 Oct 2024 11:21:45 +0000 (UTC) [thread overview]
Message-ID: <1729792642.ebce25b336d5e27ec1efa8193b11de38f1c4030d.ulm@gentoo> (raw)
commit: ebce25b336d5e27ec1efa8193b11de38f1c4030d
Author: Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Thu Oct 24 17:57:22 2024 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Thu Oct 24 17:57:22 2024 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=ebce25b3
devbook-guide: Clarify use of the term "tag"
- The XML declaration is not a tag.
- A tag cannot be closed; an element can (by a closing tag).
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
appendices/devbook-guide/text.xml | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/appendices/devbook-guide/text.xml b/appendices/devbook-guide/text.xml
index c725307..b853b0b 100644
--- a/appendices/devbook-guide/text.xml
+++ b/appendices/devbook-guide/text.xml
@@ -40,7 +40,7 @@ used in a DevBook XML document:
</codesample>
<p>
-On the first lines, we see the requisite tag that identifies this as an XML
+On the first lines, we see the XML declaration that identifies this as an XML
document. Next, there's a <c><guide></c> tag <d/> the entire document is
enclosed within a <c><guide> </guide></c> pair. Its <c>self</c>
attribute must point to the relative path of the document from the root node;
@@ -55,7 +55,7 @@ document.
</p>
<p>
-All tags must be closed of course, so the document ends with:
+All elements must be closed of course, so the document ends with:
</p>
<codesample lang="sgml">
@@ -126,7 +126,7 @@ tag. Note that the trailing slash in the <c>href</c> value is mandatory.
<p>
A table of contents can be generated with <c><contentsTree></c>.
-Typically, this tag would be the only element in its own section body, as in
+Typically, this would be the only element in its own section body, as in
the following example:
</p>
next reply other threads:[~2024-10-25 11:21 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 11:21 Ulrich Müller [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-09-09 5:10 [gentoo-commits] proj/devmanual:master commit in: appendices/devbook-guide/ Ulrich Müller
2025-06-22 9:29 Ulrich Müller
2025-06-15 14:06 Sam James
2024-10-31 18:59 Ulrich Müller
2024-05-08 5:57 Ulrich Müller
2023-11-05 16:48 Ulrich Müller
2023-11-05 16:45 Ulrich Müller
2023-10-05 20:29 Ulrich Müller
2022-02-16 18:56 Ulrich Müller
2021-07-31 17:59 Ulrich Müller
2021-03-19 19:23 Ulrich Müller
2021-03-19 19:23 Ulrich Müller
2021-03-19 19:22 Ulrich Müller
2021-03-12 19:32 Ulrich Müller
2021-03-11 11:24 Ulrich Müller
2020-12-14 19:35 Ulrich Müller
2020-08-21 16:53 Ulrich Müller
2020-03-06 16:30 Ulrich Müller
2020-03-06 16:30 Ulrich Müller
2020-03-01 12:32 Ulrich Müller
2020-02-22 21:27 Ulrich Müller
2020-01-28 5:55 Ulrich Müller
2020-01-16 18:50 Ulrich Müller
2020-01-15 22:36 Ulrich Müller
2020-01-15 22:14 Ulrich Müller
2020-01-15 21:30 Ulrich Müller
2020-01-15 21:30 Ulrich Müller
2020-01-15 21:29 Ulrich Müller
2020-01-15 21:29 Ulrich Müller
2020-01-15 21:29 Ulrich Müller
2020-01-15 21:29 Ulrich Müller
2020-01-15 21:29 Ulrich Müller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1729792642.ebce25b336d5e27ec1efa8193b11de38f1c4030d.ulm@gentoo \
--to=ulm@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox