branch master updated: * doc/texinfo.texi (@code{@@chapter}): use consistent chapter name in example.

[Patrice Dumas]

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

pertusus pushed a commit to branch master
in repository texinfo.

The following commit(s) were added to refs/heads/master by this push:
     new ef57362f77 * doc/texinfo.texi (@code{@@chapter}): use consistent 
chapter name in example.
ef57362f77 is described below

commit ef57362f7761b18c737963f38b9f68ef757ebe76
Author: Patrice Dumas <pertusus@free.fr>
AuthorDate: Tue Aug 16 19:17:36 2022 +0200

    * doc/texinfo.texi (@code{@@chapter}): use consistent chapter name
    in example.
    
    (@code{@@unnumbered @@appendix}): do not refer to the <title> DocBook
    element, it is not useful.
    
    (@code{@@majorheading @@chapheading}): do not refer to specific
    output format, but use a wording including all the remainaing
    output formats.
---
 ChangeLog        | 12 ++++++++++++
 doc/texinfo.texi | 13 +++++--------
 2 files changed, 17 insertions(+), 8 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index 3afd3f9624..0c24fef332 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,15 @@
+2022-08-16  Patrice Dumas  <pertusus@free.fr>
+
+       * doc/texinfo.texi (@code{@@chapter}): use consistent chapter name
+       in example.
+
+       (@code{@@unnumbered @@appendix}): do not refer to the <title> DocBook
+       element, it is not useful.
+
+       (@code{@@majorheading @@chapheading}): do not refer to specific
+       output format, but use a wording including all the remainaing
+       output formats.
+
 2022-08-16  Patrice Dumas  <pertusus@free.fr>
 
        * tp/Texinfo/Convert/DocBook.pm (%docbook_sections): use 'sect1'
diff --git a/doc/texinfo.texi b/doc/texinfo.texi
index df0976ee9a..735fdd1653 100644
--- a/doc/texinfo.texi
+++ b/doc/texinfo.texi
@@ -3841,11 +3841,11 @@ of the chapter.  The chapter is numbered automatically, 
starting
 from@tie{}1.
 
 For example, the present chapter in this manual is entitled
-``@code{@@chapter}: Chapter Structuring''; the @code{@@chapter} line
+``Chapter Structuring''; the @code{@@chapter} line
 looks like this:
 
 @example
-@@chapter @@code@{@@@@chapter@}: Chapter Structuring
+@@chapter Chapter Structuring
 @end example
 
 In printed output, the @code{@@chapter} command produces a chapter heading in
@@ -3910,11 +3910,10 @@ Acknowledgements  Colophon  Dedication  Preface
 @cindex @code{<dedication>} DocBook tag
 @cindex @code{<preface>} DocBook tag
 @cindex @code{<chapter>} DocBook tag
-@cindex @code{<title>} DocBook tag
 @noindent then the DocBook output uses corresponding special tags
 (@code{<preface>}, etc.)@: instead of the default @code{<chapter>}.
 The argument to @code{@@unnumbered} itself can be anything, and is
-output as the following @code{<title>} text as usual.
+output as the element title as usual.
 
 
 @node @code{@@majorheading @@chapheading}
@@ -3935,10 +3934,8 @@ In @TeX{}, a @code{@@majorheading} command generates a 
larger vertical
 whitespace before the heading than a @code{@@chapheading} command but
 is otherwise the same.
 
-In Info and plain text, the @code{@@majorheading} and
-@code{@@chapheading} commands produce the same output as
-@code{@@chapter}: the title is printed on a line by itself with a line
-of asterisks underneath.  Similarly for HTML@.  The only difference is
+In other output formats, the @code{@@majorheading} and @code{@@chapheading}
+commands produce a similar output as @code{@@chapter}.  The difference is
 the lack of numbering and the lack of any association with nodes.
 @xref{@code{@@chapter}}.