[gentoo-commits] proj/pms:eapi-9 commit in: /

["Ulrich Müller" <ulm@gentoo.org>]

commit:     c5a07aa426d0536f6ff9387af471105ebb0ba96e
Author:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Wed Feb  1 18:12:48 2023 +0000
Commit:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Wed Feb  1 18:12:48 2023 +0000
URL:        https://gitweb.gentoo.org/proj/pms.git/commit/?id=c5a07aa4

Reference sections by "section 11.2" rather than "11.2"

Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>

 ebuild-env-vars.tex    | 8 ++++----
 ebuild-environment.tex | 6 +++---
 2 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/ebuild-env-vars.tex b/ebuild-env-vars.tex
index 7f430e7..b8deb04 100644
--- a/ebuild-env-vars.tex
+++ b/ebuild-env-vars.tex
@@ -6,7 +6,7 @@ meaningful in all phases; variables that are not meaningful in a given phase may
 any value. Ebuilds must not attempt to modify any of these variables, unless otherwise specified.
 
 Because of their special meanings, these variables may not be preserved consistently across all
-phases as would normally happen due to environment saving (see~\ref{sec:ebuild-env-state}).
+phases as would normally happen due to environment saving (see section~\ref{sec:ebuild-env-state}).
 For example, \t{EBUILD_PHASE} is different for every phase, and \t{ROOT} may have changed between
 the various different \t{pkg_*} phases. Ebuilds must recalculate any variable they derive from an
 inconsistent variable.
@@ -40,7 +40,7 @@ inconsistent variable.
 \endlastfoot
 \t{P} &
     All &
-    No\footnote{May change if a package has been updated (see~\ref{sec:updates-dir}).} &
+    No\footnote{May change if a package has been updated (see section~\ref{sec:updates-dir}).} &
     Package name and version, without the revision part. For example, \t{vim-7.0.174}. \\
 \t{PF} &
     All &
@@ -175,8 +175,8 @@ inconsistent variable.
     calling environment, \t{EPREFIX} defaults to the built-in offset-prefix that was set during
     installation of the package manager. When a different \t{EPREFIX} value than the built-in value
     is set in the calling environment, a cross-prefix build is performed where using the existing
-    utilities, a package is built for the given \t{EPREFIX}, akin to \t{ROOT}\@.
-    See also~\ref{sec:offset-vars}. Only for EAPIs listed in table~\ref{tab:offset-env-vars-table}
+    utilities, a package is built for the given \t{EPREFIX}, akin to \t{ROOT}\@. See also
+    section~\ref{sec:offset-vars}. Only for EAPIs listed in table~\ref{tab:offset-env-vars-table}
     as supporting \t{EPREFIX}. \\
 \t{D} &
     \t{src_*} &

diff --git a/ebuild-environment.tex b/ebuild-environment.tex
index b9f3622..8093f1e 100644
--- a/ebuild-environment.tex
+++ b/ebuild-environment.tex
@@ -16,9 +16,9 @@ Variables that were exported must remain exported in later functions; variables
 visibility may retain default visibility or be exported. Variables with special meanings to the
 package manager are excluded from this rule.
 
-Global variables must only contain invariant values (see~\ref{sec:metadata-invariance}). If a global
-variable's value is invariant, it may have the value that would be generated at any given point
-in the build sequence.
+Global variables must only contain invariant values (see section~\ref{sec:metadata-invariance}).
+If a global variable's value is invariant, it may have the value that would be generated at any
+given point in the build sequence.
 
 This is demonstrated by code listing~\ref{lst:env-saving}.