Clarify wording for EAPI parsing.

Clarify wording. Require a space before the trailing comment.

1 files changed, 6 insertions, 5 deletions

diff --git a/ebuild-vars.tex b/ebuild-vars.tex
index f3b72bf..29b9dfa 100644
--- a/ebuild-vars.tex
+++ b/ebuild-vars.tex
@@ -129,14 +129,15 @@ once. The assignment must not be preceded by any lines other than blank lines or
 with optional whitespace (spaces or tabs) followed by a \t{\#} character, and the line containing
 the assignment statement must match the following regular expression:
 \begin{verbatim}
-^[ \t]*EAPI=(['"]?)([A-Za-z0-9+_.-]*)\1[ \t]*(#.*)?$
+^[ \t]*EAPI=(['"]?)([A-Za-z0-9+_.-]*)\1[ \t]*([ \t]#.*)?$
 \end{verbatim}
 
 The package manager may optionally determine the EAPI of an ebuild by parsing its first non-blank
-and non-comment line, using above regular expression. If a recognised EAPI has been determined
-such, then the package manager must make sure that the \t{EAPI} value obtained by sourcing the
-ebuild with bash is identical to the EAPI obtained by parsing. The ebuild must be treated as
-invalid if these values are different.
+and non-comment line, using the above regular expression. If it matches, the EAPI is the substring
+matched by the capturing parentheses (\t{0} if empty), otherwise it is \t{0}. For a recognised
+EAPI, the package manager must make sure that the \t{EAPI} value obtained by sourcing the ebuild
+with bash is identical to the EAPI obtained by parsing. The ebuild must be treated as invalid if
+these values are different.
 
 \subsection{\t{RDEPEND} value}
 \label{sec:rdepend-depend}