Whitespace

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

6 files changed, 16 insertions, 15 deletions

diff --git a/dependencies.tex b/dependencies.tex
index 0ff1c7e..6c09714 100644
--- a/dependencies.tex
+++ b/dependencies.tex
@@ -240,8 +240,8 @@ error on non-compliant input.
 
 In EAPIs shown in table~\ref{tab:slot-deps-table} as supporting \t{SLOT} dependencies, either of the
 above formats may additionally be suffixed by a \t{:slot} restriction, as described in
-section~\ref{sec:slot-dep}. A package manager must warn or error if slot dependencies are used with an
-EAPI not supporting \t{SLOT} dependencies.
+section~\ref{sec:slot-dep}. A package manager must warn or error if slot dependencies are used with
+an EAPI not supporting \t{SLOT} dependencies.
 
 \featurelabel{use-deps} In EAPIs shown in table~\ref{tab:use-deps-table} as supporting 2-style
 or 4-style \t{USE} dependencies, a specification may additionally be suffixed by at most one
diff --git a/ebuild-env-vars.tex b/ebuild-env-vars.tex
index db693ab..004a7a2 100644
--- a/ebuild-env-vars.tex
+++ b/ebuild-env-vars.tex
@@ -6,10 +6,10 @@ 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}). 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.
+phases as would normally happen due to environment saving (see~\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.
 
 \begin{landscape}
 \reversemarginpar
diff --git a/ebuild-functions.tex b/ebuild-functions.tex
index 0c745c3..7d372fa 100644
--- a/ebuild-functions.tex
+++ b/ebuild-functions.tex
@@ -434,8 +434,9 @@ the \t{ROOT} environment variable.
 
 \subsection{pkg_config}
 
-The \t{pkg_config} function performs any custom steps required to configure a package after it has been
-fully installed. It is the only ebuild function which may be interactive and prompt for user input.
+The \t{pkg_config} function performs any custom steps required to configure a package after it has
+been fully installed. It is the only ebuild function which may be interactive and prompt for user
+input.
 
 \t{pkg_config} must be run with full access to all files and directories inside of \t{ROOT}.
 
diff --git a/eclasses.tex b/eclasses.tex
index e23dcd8..01692bc 100644
--- a/eclasses.tex
+++ b/eclasses.tex
@@ -8,8 +8,8 @@ using them. The interpreter is therefore the same, and the same requirements for
 hold.
 
 Eclasses must be located in the \t{eclass} directory in the top level of the repository---see
-section~\ref{sec:eclass-dir}. Each eclass is a single file named \t{<name>.eclass}, where \t{<name>} is
-the name of this eclass, used by \t{inherit} and \t{EXPORT_FUNCTIONS} among other places.
+section~\ref{sec:eclass-dir}. Each eclass is a single file named \t{<name>.eclass}, where \t{<name>}
+is the name of this eclass, used by \t{inherit} and \t{EXPORT_FUNCTIONS} among other places.
 
 \section{The inherit Command}
 \label{sec:inherit}
diff --git a/introduction.tex b/introduction.tex
index 57fb51a..86149b2 100644
--- a/introduction.tex
+++ b/introduction.tex
@@ -13,9 +13,9 @@ This document does not specify any user or package manager configuration informa
 
 \section{Rationale}
 
-At present the only definition of what an ebuild can assume about its environment,
-and the only definition of what is valid in an ebuild, is the source code of the latest Portage release
-and a general consensus about which features are too new to assume availability. This has several
+At present the only definition of what an ebuild can assume about its environment, and the only
+definition of what is valid in an ebuild, is the source code of the latest Portage release and
+a general consensus about which features are too new to assume availability. This has several
 drawbacks: not only is it impossible to change any aspect of Portage behaviour without verifying
 that nothing in the tree relies upon it, but if a new package manager should appear it becomes
 impossible to fully support such an ill-defined standard.
diff --git a/merge.tex b/merge.tex
index 6fcfeec..ca1036d 100644
--- a/merge.tex
+++ b/merge.tex
@@ -30,8 +30,8 @@ except as follows:
     its group be that of the superuser.
 \end{compactitem}
 
-On SELinux systems, the SELinux context must also be preserved. Other directory attributes, including
-modification time, may be discarded.
+On SELinux systems, the SELinux context must also be preserved. Other directory attributes,
+including modification time, may be discarded.
 
 \subsection{Empty directories}