[latex3-commits] [latex3/latex3] main: Tighten up use of the word "groups" in l3keys documentation (d5d10c8e7)

[github at latex-project.org]

Repository : https://github.com/latex3/latex3
On branch  : main
Link       : https://github.com/latex3/latex3/commit/d5d10c8e7c0380e8fee6da02297b5bc7fb12c0b2

>---------------------------------------------------------------

commit d5d10c8e7c0380e8fee6da02297b5bc7fb12c0b2
Author: Bruno Le Floch <blflatex at gmail.com>
Date:   Thu Jan 11 23:53:55 2024 +0100

    Tighten up use of the word "groups" in l3keys documentation


>---------------------------------------------------------------

d5d10c8e7c0380e8fee6da02297b5bc7fb12c0b2
 l3kernel/l3keys.dtx | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/l3kernel/l3keys.dtx b/l3kernel/l3keys.dtx
index bbdac54fb..d3171ade8 100644
--- a/l3kernel/l3keys.dtx
+++ b/l3kernel/l3keys.dtx
@@ -109,8 +109,8 @@
 % Key names may contain any tokens, as they are handled internally
 % using \cs{tl_to_str:n}. As discussed in
 % section~\ref{sec:l3keys:subdivision}, it is suggested that the character
-% |/| is reserved for sub-division of keys into logical
-% groups. Functions and variables are \emph{not} expanded when creating
+% |/| is reserved for sub-division of keys into different subsets.
+% Functions and variables are \emph{not} expanded when creating
 % key names, and so
 % \begin{verbatim}
 %   \tl_set:Nn \l_mymodule_tmp_tl { key }
@@ -340,7 +340,7 @@
 %   \end{syntax}
 %   Specifies that the \meta{key} path should inherit the keys listed
 %   as any of the \meta{parents} (a comma list), which can be a module
-%   or a subgroup. For example, after setting
+%   or a sub-division thereof. For example, after setting
 %   \begin{verbatim}
 %     \keys_define:nn { foo } { test .code:n = \tl_show:n {#1} }
 %     \keys_define:nn { } { bar .inherit:n = foo }
@@ -547,21 +547,21 @@
 % \label{sec:l3keys:subdivision}
 %
 % When creating large numbers of keys, it may be desirable to divide
-% them into several sub-groups for a given module. This can be achieved
+% them into several subsets for a given module. This can be achieved
 % either by adding a sub-division to the module name:
 % \begin{verbatim}
-%   \keys_define:nn { mymodule / subgroup }
+%   \keys_define:nn { mymodule / subset }
 %     { key .code:n = code }
 % \end{verbatim}
 % or to the key name:
 % \begin{verbatim}
 %   \keys_define:nn { mymodule }
-%     { subgroup / key .code:n = code }
+%     { subset / key .code:n = code }
 % \end{verbatim}
 % As illustrated, the best choice of token for sub-dividing keys in
 % this way is |/|. This is because of the method that is
 % used to represent keys internally. Both of the above code fragments
-% set the same key, which has full name \texttt{mymodule/subgroup/key}.
+% set the same key, which has full name \texttt{mymodule/subset/key}.
 %
 % As illustrated in the next section, this subdivision is
 % particularly relevant to making multiple choices.