Fix spacing in all occurences of e.g. and i.e.

5 files changed, 18 insertions, 18 deletions

diff --git a/dependencies.tex b/dependencies.tex
index 857356c..e663a67 100644
--- a/dependencies.tex
+++ b/dependencies.tex
@@ -30,7 +30,7 @@ be surrounded on both sides by whitespace, except at the start and end of the st
     followed by whitespace, then \t{->}, then whitespace, then a simple filename when in
     \t{SRC\_URI}.  For \t{SRC\_URI} behaviour, see section~\ref{sec:src-uri-behaviour}.
 \item A flat filename. Permitted in \t{SRC\_URI}.
-\item A license name (e.g. \t{GPL-2}). Permitted in \t{LICENSE}.
+\item A license name (e.\,g.\ \t{GPL-2}). Permitted in \t{LICENSE}.
 \item A simple string. Permitted in \t{RESTRICT} and \t{PROPERTIES}.
 \item An all-of group, which consists of an open parenthesis, followed by whitespace,
     followed by zero or more of (a dependency item of any kind followed by whitespace), followed
@@ -199,8 +199,8 @@ described in table~\ref{tab:bang-strength-table}.
 
 \featurelabel{slot-deps} A named slot dependency consists of a colon followed by a slot name. A
 specification with a named slot dependency matches only if the slot of the matched package is equal
-to the slot specified. If the slot of the package to match cannot be determined (e.g. because it is
-not a supported \t{EAPI}), the match is treated as unsuccessful.
+to the slot specified. If the slot of the package to match cannot be determined (e.\,g.\ because it
+is not a supported \t{EAPI}), the match is treated as unsuccessful.
 
 \featurelabel{slot-operator-deps} An operator slot dependency consists of a colon followed by one of
 the following operators:
@@ -237,7 +237,7 @@ A 2-style or 4-style use dependency consists of one of the following:
 \item[{[-opt]}] The flag must be disabled.
 \end{description}
 
-Multiple requirements may be combined using commas, e.g. \t{[first,-second,third?]}.
+Multiple requirements may be combined using commas, e.\,g.\ \t{[first,-second,third?]}.
 
 When multiple requirements are specified, all must match for a successful match.
 
@@ -289,7 +289,7 @@ Ebuilds may not rely upon any token being supported.
 \subsection{SRC\_URI}
 \label{sec:src-uri-behaviour}
 
-All filename components that are enabled (i.e. not inside a use-conditional block that is not
+All filename components that are enabled (i.\,e.\ not inside a use-conditional block that is not
 matched) in \t{SRC\_URI} must be available in the \t{DISTDIR} directory. In addition, these
 components are used to make the \t{A} and \t{AA} variables.
 
diff --git a/ebuild-env-vars.tex b/ebuild-env-vars.tex
index f004d34..b88fc63 100644
--- a/ebuild-env-vars.tex
+++ b/ebuild-env-vars.tex
@@ -168,7 +168,7 @@ variable.
     \t{configure}, \t{compile}, \t{test}, \t{install}, \t{preinst}, \t{postinst}, \t{prerm},
     \t{postrm}, \t{info}, \t{pretend} according to the top level ebuild function that was executed
     by the package manager. May be unset or any single word that is not any of the above when the
-    ebuild is being sourced for other (e.g. metadata or QA) purposes. \\
+    ebuild is being sourced for other (e.\,g.\ metadata or QA) purposes. \\
 \t{WORKDIR} &
     \t{src\_*} &
     Yes &
diff --git a/ebuild-functions.tex b/ebuild-functions.tex
index 25944c0..2bb292b 100644
--- a/ebuild-functions.tex
+++ b/ebuild-functions.tex
@@ -96,7 +96,7 @@ before the next phase is executed.
 \label{sec:pkg-setup-function}
 The \t{pkg\_setup} function sets up the ebuild's environment for all following functions, before
 the build process starts. Further, it checks whether any necessary prerequisites not covered
-by the package manager, e.g.\ that certain kernel configuration options are fulfilled.
+by the package manager, e.\,g.\ that certain kernel configuration options are fulfilled.
 
 \t{pkg\_setup} must be run with full filesystem permissions, including the ability to add new users
 and/or groups to the system.
diff --git a/ebuild-vars.tex b/ebuild-vars.tex
index 8f888ac..72996d8 100644
--- a/ebuild-vars.tex
+++ b/ebuild-vars.tex
@@ -167,11 +167,11 @@ not be exported to the ebuild environment:
 
 \begin{description}
 \item[DEFINED\_PHASES] \featurelabel{defined-phases} A space separated arbitrarily ordered list of
-phase names (e.g. \t{configure setup unpack}) whose phase functions are defined by the ebuild or an
-eclass inherited by the ebuild. If no phase functions are defined, a single hyphen is used instead
-of an empty string. For EAPIs listed in table~\ref{tab:defined-phases-table} as having optional
-\t{DEFINED\_PHASES} support, package managers may not rely upon the metadata cache having this
-variable defined, and must treat an empty string as ``this information is not available''.
+phase names (e.\,g.\ \t{configure setup unpack}) whose phase functions are defined by the ebuild or
+an eclass inherited by the ebuild. If no phase functions are defined, a single hyphen is used
+instead of an empty string. For EAPIs listed in table~\ref{tab:defined-phases-table} as having
+optional \t{DEFINED\_PHASES} support, package managers may not rely upon the metadata cache having
+this variable defined, and must treat an empty string as ``this information is not available''.
 \end{description}
 
 \note Thus, by extension of section~\ref{sec:metadata-invariance}, phase functions must not be defined
diff --git a/pkg-mgr-commands.tex b/pkg-mgr-commands.tex
index fe6e0c4..d6db362 100644
--- a/pkg-mgr-commands.tex
+++ b/pkg-mgr-commands.tex
@@ -189,12 +189,12 @@ has returned.
 \end{algorithmic}
 \end{algorithm}
 
-\item[emake] Calls the \t{\$MAKE} program, or GNU make if the \t{MAKE} variable is unset.  Any
-    arguments given are passed directly to the make command, as are the user's chosen \t{MAKEOPTS}\@.
-    Arguments given to \t{emake} override user configuration. See also
-    section~\ref{sec:guaranteed-system-commands}. \t{emake} must be an external program and cannot be a
-    function or alias---it must be callable from e.g. \t{xargs}. Failure behaviour is EAPI dependent
-    as per section~\ref{sec:failure-behaviour}.
+\item[emake] Calls the \t{\$MAKE} program, or GNU make if the \t{MAKE} variable is unset.
+    Any arguments given are passed directly to the make command, as are the user's chosen
+    \t{MAKEOPTS}\@. Arguments given to \t{emake} override user configuration. See also
+    section~\ref{sec:guaranteed-system-commands}. \t{emake} must be an external program and cannot
+    be a function or alias---it must be callable from e.\,g.\ \t{xargs}. Failure behaviour is EAPI
+    dependent as per section~\ref{sec:failure-behaviour}.
 \item[einstall] A shortcut for the command given in Listing~\ref{lst:einstall}. Any arguments given
     to \t{einstall} are passed verbatim to \t{emake}, as shown. Failure behaviour is EAPI dependent
     as per section~\ref{sec:failure-behaviour}.