l3 (12jul13)

git-svn-id: svn://tug.org/texlive/trunk@31181 c570f23f-e606-0410-a88d-b1316a301751

1 files changed, 11 insertions, 11 deletions

diff --git a/Master/texmf-dist/source/latex/l3packages/xparse/xparse.dtx b/Master/texmf-dist/source/latex/l3packages/xparse/xparse.dtx
index 64a7cb504d9..be5242226ba 100644
--- a/Master/texmf-dist/source/latex/l3packages/xparse/xparse.dtx
+++ b/Master/texmf-dist/source/latex/l3packages/xparse/xparse.dtx
@@ -41,8 +41,8 @@
 %<*driver|package>
 % The version of expl3 required is tested as early as possible, as
 % some really old versions do not define \ProvidesExplPackage.
-\RequirePackage{expl3}[2013/03/12]
-%<package>\@ifpackagelater{expl3}{2013/03/12}
+\RequirePackage{expl3}[2013/07/12]
+%<package>\@ifpackagelater{expl3}{2013/07/12}
 %<package>  {}
 %<package>  {%
 %<package>    \PackageError{xparse}{Support package l3kernel too old}
@@ -54,7 +54,7 @@
 %<package>      }%
 %<package>    \endinput
 %<package>  }
-\GetIdInfo$Id: xparse.dtx 4467 2013-03-12 08:29:05Z joseph $
+\GetIdInfo$Id: xparse.dtx 4544 2013-07-12 07:14:52Z joseph $
   {L3 Experimental document command parser}
 %</driver|package>
 %<*driver>
@@ -344,10 +344,10 @@
 %   \begin{verbatim}
 %     \DeclareDocumentCommand \chapter { s o m }
 %       {
-%        \IfBooleanTF {#1}
-%          { \typesetnormalchapter {#2} {#3} }
-%          { \typesetstarchapter {#3} }
-%      }
+%         \IfBooleanTF {#1}
+%           { \typesetstarchapter {#3} }
+%           { \typesetnormalchapter {#2} {#3} }
+%       }
 %   \end{verbatim}
 %   would be a way to define a \cs{chapter} command which would
 %   essentially behave like the current \LaTeXe{} command (except that it
@@ -499,7 +499,7 @@
 %     \cs{ReverseBoolean}
 %   \end{syntax}
 %   This processor reverses the logic of \cs{BooleanTrue} and
-%   \cs{BooleanFalse}, so that the the example from earlier would become
+%   \cs{BooleanFalse}, so that the example from earlier would become
 %   \begin{verbatim}
 %     \DeclareDocumentCommand \foo { > { \ReverseBoolean } s m }
 %       {
@@ -1955,7 +1955,7 @@
 %   to collect up each pair of optional tokens without \TeX{} helping out,
 %   and without counting anything. The code above will already have
 %   removed the leading opening token and a closing token, but the
-%   wrong one. The aim is then to work through the the material grabbed
+%   wrong one. The aim is then to work through the material grabbed
 %   so far and divide it up on each opening token, grabbing a closing
 %   token to match (thus working in pairs). Once there are no opening
 %   tokens, then there is a second check to see if there are any
@@ -2308,7 +2308,7 @@
 % \begin{variable}{\l_@@_v_rest_of_signature_tl}
 % \begin{variable}{\l_@@_v_arg_tl}
 %   The opening delimiter is never read verbatim, for consistency: if the
-%   preceeding argument was optional and absent, then \TeX{} has already read
+%   preceding argument was optional and absent, then \TeX{} has already read
 %   that token when looking for the optional argument. The first thing
 %   to check is that this delimiter is a character, and distinguish the
 %   case of a left brace (in that case, \cs{group_align_safe_end:}
@@ -2820,7 +2820,7 @@
 %
 % \begin{macro}[EXP]{\@@_expandable_grab_R_alt:w}
 % \begin{macro}[EXP]{\@@_expandable_grab_R_alt_aux:NNnwNn}
-%   When the delimiters are identical, nesting is not possble and a simplified
+%   When the delimiters are identical, nesting is not possible and a simplified
 %   approach is used. The test concept here is the same as for the case where
 %   the delimiters are different.
 %    \begin{macrocode}