texinfo-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[no subject]


From: Patrice Dumas
Date: Sun, 17 Jul 2022 16:30:20 -0400 (EDT)

branch: master
commit 04b2cf42556f2756590858e9bb8571b18e0878e6
Author: Patrice Dumas <pertusus@free.fr>
AuthorDate: Sun Jul 17 19:30:47 2022 +0200

    Minor changes in POD and api documentation
---
 doc/customization_api.texi      | 12 ++++++------
 tp/Texinfo/Convert/Converter.pm |  4 ++--
 2 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/doc/customization_api.texi b/doc/customization_api.texi
index c3296b5da1..273fe88226 100644
--- a/doc/customization_api.texi
+++ b/doc/customization_api.texi
@@ -551,7 +551,7 @@ first step of parsing the Texinfo code, which cannot be 
customized.}.
 The function used is @code{texinfo_register_type_format_info}:
 
 @defun texinfo_register_type_format_info ($type, $code_type, $pre_class_type)
-@var{$type} is the type of the container.  If @var{code_type} is set, the 
container
+@var{$type} is the type of the container.  If @var{$code_type} is set, the 
container
 contents are assumed to be in code context. @xref{Init File Expansion
 Contexts}. If @var{$pre_class_type} is set, the HTML @code{<pre>} elements
 class attribute are based on @var{$pre_class_type}, if there are such HTML
@@ -763,10 +763,10 @@ conversely, the main component is nodes if 
@code{USE_NODES} is set.
 When sections are the main components of element units, ``isolated'' nodes
 not directly associated with a sectioning command are associated with
 the following sectioning command, while sectioning commands without
-nodes constitute an element.  Conversely, when nodes are the main
+nodes constitute element units.  Conversely, when nodes are the main
 components of elements, isolated sections not associated with nodes
 are associated with the previous node, and isolated nodes are
-elements.
+element units.
 
 
 @node Directions
@@ -783,8 +783,8 @@ associated with a button (@pxref{Simple Navigation Panel 
Customization}).
 
 Each element direction has a name and a reference to the element unit they
 point to, when such an element exists.  The element is either a
-global element (for example, the first element) or relative to the
-current element (for example, the next element unit).  Such relative
+global element unit (for example, the first element) or relative to the
+current element unit (for example, the next element unit).  Such relative
 elements are determined with respect to the document structure defined
 by the section structuring commands (@code{@@chapter},
 @code{@@unnumbered}@dots{}) or by the nodes if the node pointers are
@@ -1137,7 +1137,7 @@ the elements, but it can be interesting in some cases.
 
 @deftypefun $converted_text $converter->convert_tree (\%element, $explanation)
 @var{\%element} is a Texinfo tree element. @var{$explanation} is
-optional, it is a tree explaining why the function was called, to help
+optional, it is a string explaining why the function was called, to help
 in case of debugging.  The function returns @var{\%element} converted.
 @end deftypefun
 
diff --git a/tp/Texinfo/Convert/Converter.pm b/tp/Texinfo/Convert/Converter.pm
index 630708d1c9..a80e4878b3 100644
--- a/tp/Texinfo/Convert/Converter.pm
+++ b/tp/Texinfo/Convert/Converter.pm
@@ -1702,14 +1702,14 @@ also initialized as a L<Texinfo::Report>.
 
 =back
 
-To help with these initializations, the modules can define two methods:
+To help with these initializations, the modules subclassing 
C<Texinfo::Convert::Converter> can define two methods:
 
 =over
 
 =item %defaults = $converter->converter_defaults($options)
 X<C<converter_defaults>>
 
-The converter can provide a defaults hash for configuration options.
+The module can provide a defaults hash for converter configuration options.
 The I<$options> hash reference holds options for the converter.
 
 =item converter_initialize



reply via email to

[Prev in Thread] Current Thread [Next in Thread]