[latex3-commits] [l3svn] r6263 - Typo and spacing changes

[noreply at latex-project.org]

Author: bruno
Date: 2015-11-15 19:21:43 +0100 (Sun, 15 Nov 2015)
New Revision: 6263

Modified:
   trunk/l3packages/xparse/xparse.dtx
Log:
Typo and spacing changes


Modified: trunk/l3packages/xparse/xparse.dtx
===================================================================
--- trunk/l3packages/xparse/xparse.dtx	2015-11-15 14:45:57 UTC (rev 6262)
+++ trunk/l3packages/xparse/xparse.dtx	2015-11-15 18:21:43 UTC (rev 6263)
@@ -288,7 +288,11 @@
 % \verb*|\foo{arg1} [arg2]| will not. This is so that trailing optional
 % arguments are not picked up \enquote{by accident} in input.
 %
-% There is one major exception to the rules listed above: when \pkg{xparse} is used to define what \TeX\ defines as \enquote{control symbols} in which the function name is made up of a single character, such as \enquote{\cmd{\\}}, spaces are \emph{not} ignored directly after them even for mandatory arguments.
+% There is one major exception to the rules listed above: when
+% \pkg{xparse} is used to define what \TeX\ defines as \enquote{control
+% symbols} in which the function name is made up of a single character,
+% such as \enquote{\cmd{\\}}, spaces are \emph{not} ignored directly
+% after them even for mandatory arguments.
 %
 % \subsection{Required delimited arguments}
 %
@@ -646,14 +650,14 @@
 %     \item The \enquote{verbatim} argument type \texttt{v} is not available.
 %     \item It is not possible to differentiate between, for example
 %       |\foo[| and |\foo{[}|: in both cases the \texttt{[} will be
-%       interpreted as the start of an optional argument. As a result
+%       interpreted as the start of an optional argument. As a
 %       result, checking for optional arguments is less robust than
 %       in the standard version.
 %   \end{itemize}
 %   \pkg{xparse} will issue an error if an argument specifier is given
 %   which does not conform to the first three requirements. The last
 %   item is an issue when the function is used, and so is beyond the
-%  scope of \pkg{xparse} itself.
+%   scope of \pkg{xparse} itself.
 % \end{function}
 %
 % \subsection{Access to the argument specification}
@@ -1832,7 +1836,7 @@
 % \end{macro}
 %
 % \begin{macro}{\@@_add_expandable_type_v:w}
-%  Another forbidden type.
+%   Another forbidden type.
 %    \begin{macrocode}
 \cs_new_protected_nopar:Npn \@@_add_expandable_type_v:w
   {