branch master updated: * doc/texinfo.texi (Structuring Command Types): Grammar and style fixes. Try to avoid confusion between type of DocBook element in abstract and the actual element that is output. Clarify that e.g. @sections would not contain following @chapters even if they were the last section of a chapter.

[Gavin D. Smith]

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

gavin pushed a commit to branch master
in repository texinfo.

The following commit(s) were added to refs/heads/master by this push:
     new 23b37a3d68 * doc/texinfo.texi (Structuring Command Types): Grammar and 
style fixes.  Try to avoid confusion between type of DocBook element in 
abstract and the actual element that is output. Clarify that e.g. @sections 
would not contain following @chapters even if they were the last section of a 
chapter.
23b37a3d68 is described below

commit 23b37a3d68f0902a10c1ecfcddcea0bb357bd9a5
Author: Gavin Smith <gavinsmith0123@gmail.com>
AuthorDate: Tue Aug 23 17:57:31 2022 +0100

    * doc/texinfo.texi (Structuring Command Types): Grammar
    and style fixes.  Try to avoid confusion between type of DocBook
    element in abstract and the actual element that is output.
    Clarify that e.g. @sections would not contain following @chapters
    even if they were the last section of a chapter.
---
 ChangeLog        |  8 ++++++++
 doc/texinfo.texi | 23 +++++++++++++----------
 2 files changed, 21 insertions(+), 10 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index f24e18a476..c03560dc54 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,11 @@
+2022-08-23  Gavin Smith  <gavinsmith0123@gmail.com>
+
+       * doc/texinfo.texi (Structuring Command Types): Grammar
+       and style fixes.  Try to avoid confusion between type of DocBook
+       element in abstract and the actual element that is output.
+       Clarify that e.g. @sections would not contain following @chapters
+       even if they were the last section of a chapter.
+
 2022-08-23  Patrice Dumas  <pertusus@free.fr>
 
        Fix conditions on @kpdinputstyle example
diff --git a/doc/texinfo.texi b/doc/texinfo.texi
index 31ce594886..63b0011256 100644
--- a/doc/texinfo.texi
+++ b/doc/texinfo.texi
@@ -3822,13 +3822,10 @@ in the document.  When a @code{@@setchapternewpage} 
command says to do so, the
 start new pages in the printed manual; the @code{@@heading} commands
 do not.  @xref{@code{@@setchapternewpage}}.
 
-In Info and plain text output, the command cause the
+In Info and plain text output, the command causes the
 title to appear on a line by itself, with a line of an ASCII character
-(@samp{*}, @samp{=}, @dots{}) inserted
-underneath.  The underlining character is the same for all the commands
-at the same level.  For instance, they are the same for the chapter-level 
commands
-@code{@@chapter}, @code{@@apppendix}, @code{@@unnumbered} and
-@code{@@chapheading}.  For example, the ``Chapter Structuring'' heading could 
be:
+(@samp{*}, @samp{=}, @dots{}) inserted underneath.
+For example, the ``Chapter Structuring'' heading could be:
 
 @example
 @group
@@ -3837,15 +3834,21 @@ at the same level.  For instance, they are the same for 
the chapter-level comman
 @end group
 @end example
 
+@noindent The underlining character is the same for all the commands at the
+same level.  For instance, it is the same for the chapter-level commands
+@code{@@chapter}, @code{@@apppendix}, @code{@@unnumbered} and
+@code{@@chapheading}.
+
 In HTML, the chapter-level commands produce an @code{<h2>}-level
 header by default (controlled by the @code{CHAPTER_HEADER_LEVEL}
 customization variable, @pxref{Other Customization Variables}).
 The heading element level is adjusted for the other commands.
 
-In the XML and DocBook output, the appropriate element is produced
-that includes all the following sections, up to the next command
-at the same level.  For example, a @code{<chapter>} element is produced
-for @code{@@chapter}.
+In the XML and DocBook output, the appropriate level of element is used.
+The produced element includes all following sections up to the next command
+at the same or higher level.
+For example, a @code{<chapter>} element is produced for @code{@@chapter},
+and contains any sections or subsections in the chapter.
 
 Here is a summary: