Use simple underscores throughout.

Replacement was done using "sed -i 's/\\_/_/g' *.tex".
This does not change the resulting PDF and HTML output.

1 files changed, 121 insertions, 121 deletions

diff --git a/ebuild-functions.tex b/ebuild-functions.tex
index 045b207..e90c050 100644
--- a/ebuild-functions.tex
+++ b/ebuild-functions.tex
@@ -12,8 +12,8 @@ temporary directory \t{T}; exceptions are noted below. All functions may assume
 access to all system libraries, binaries and configuration files that are accessible to normal
 users.
 
-The environment for functions run outside of the build sequence (that is, \t{pkg\_config},
-\t{pkg\_info}, \t{pkg\_prerm} and \t{pkg\_postrm}) must be the environment used for the build of the
+The environment for functions run outside of the build sequence (that is, \t{pkg_config},
+\t{pkg_info}, \t{pkg_prerm} and \t{pkg_postrm}) must be the environment used for the build of the
 package, not the current configuration.
 
 Ebuilds must not call nor assume the existence of any phase functions.
@@ -37,10 +37,10 @@ fallback to \t{WORKDIR} is used:
 
 \begin{compactitem}
 \item The \t{A} variable contains no items.
-\item The phase function in question is not in \t{DEFINED\_PHASES}.
+\item The phase function in question is not in \t{DEFINED_PHASES}.
 \item None of the phase functions \t{unpack}, \t{prepare}, \t{configure}, \t{compile} or \t{install},
     if supported by the EAPI in question and occurring prior to the phase about to be executed, are
-    in \t{DEFINED\_PHASES}.
+    in \t{DEFINED_PHASES}.
 \end{compactitem}
 
 \ChangeWhenAddingAnEAPI{6}
@@ -57,30 +57,30 @@ fallback to \t{WORKDIR} is used:
     \end{tabular}
 \end{centertable}
 
-\subsection{pkg\_pretend}
+\subsection{pkg_pretend}
 
-\featurelabel{pkg-pretend} The \t{pkg\_pretend} function is only called for EAPIs listed in
+\featurelabel{pkg-pretend} The \t{pkg_pretend} function is only called for EAPIs listed in
 table~\ref{tab:pkg-pretend-table} as supporting it.
 
-The \t{pkg\_pretend} function may be used to carry out sanity checks early on in the install
+The \t{pkg_pretend} function may be used to carry out sanity checks early on in the install
 process. For example, if an ebuild requires a particular kernel configuration, it may perform that
-check in \t{pkg\_pretend} and call \t{eerror} and then \t{die} with appropriate messages if the
+check in \t{pkg_pretend} and call \t{eerror} and then \t{die} with appropriate messages if the
 requirement is not met.
 
-\t{pkg\_pretend} is run separately from the main phase function sequence, and does not participate
+\t{pkg_pretend} is run separately from the main phase function sequence, and does not participate
 in any kind of environment saving. There is no guarantee that any of an ebuild's dependencies will
 be met at this stage, and no guarantee that the system state will not have changed substantially
 before the next phase is executed.
 
-\t{pkg\_pretend} must not write to the filesystem.
+\t{pkg_pretend} must not write to the filesystem.
 
 \ChangeWhenAddingAnEAPI{6}
-\begin{centertable}{EAPIs supporting \t{pkg\_pretend}}
+\begin{centertable}{EAPIs supporting \t{pkg_pretend}}
     \label{tab:pkg-pretend-table}
     \begin{tabular}{ll}
       \toprule
       \multicolumn{1}{c}{\textbf{EAPI}} &
-      \multicolumn{1}{c}{\textbf{Supports \t{pkg\_pretend}?}} \\
+      \multicolumn{1}{c}{\textbf{Supports \t{pkg_pretend}?}} \\
       \midrule
       0, 1, 2, 3        & No  \\
       4, 5, 6           & Yes \\
@@ -88,25 +88,25 @@ before the next phase is executed.
     \end{tabular}
 \end{centertable}
 
-\subsection{pkg\_setup}
+\subsection{pkg_setup}
 
-The \t{pkg\_setup} function sets up the ebuild's environment for all following functions, before
+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.
 
-\t{pkg\_setup} must be run with full filesystem permissions, including the ability to add new users
+\t{pkg_setup} must be run with full filesystem permissions, including the ability to add new users
 and/or groups to the system.
 
-\subsection{src\_unpack}
+\subsection{src_unpack}
 
-The \t{src\_unpack} function extracts all of the package's sources. In EAPIs lacking
-\t{src\_prepare}, it may also apply patches and set up the package's build system for further use.
+The \t{src_unpack} function extracts all of the package's sources. In EAPIs lacking
+\t{src_prepare}, it may also apply patches and set up the package's build system for further use.
 
 The initial working directory must be \t{WORKDIR}, and the default implementation used when
-the ebuild lacks the \t{src\_unpack} function shall behave as:
+the ebuild lacks the \t{src_unpack} function shall behave as:
 
 \begin{listing}[H]
-\caption{\t{src\_unpack}}
+\caption{\t{src_unpack}}
 \begin{verbatim}
 src_unpack() {
     if [[ -n ${A} ]]; then
@@ -116,21 +116,21 @@ src_unpack() {
 \end{verbatim}
 \end{listing}
 
-\subsection{src\_prepare}
+\subsection{src_prepare}
 
-\featurelabel{src-prepare} The \t{src\_prepare} function is only called for EAPIs listed in
-table~\ref{tab:src-prepare-table} as supporting it. The \t{src\_prepare} function can be used for
+\featurelabel{src-prepare} The \t{src_prepare} function is only called for EAPIs listed in
+table~\ref{tab:src-prepare-table} as supporting it. The \t{src_prepare} function can be used for
 post-unpack source preparation.
 
 The initial working directory is \t{S}, with an error or fallback to \t{WORKDIR} as discussed in
 section~\ref{sec:s-to-workdir-fallback}.
 
 \featurelabel{src-prepare-6} For EAPIs listed in table~\ref{tab:src-prepare-table} as using format
-6, the default implementation used when the ebuild lacks the \t{src\_prepare} function shall behave
+6, the default implementation used when the ebuild lacks the \t{src_prepare} function shall behave
 as:
 
 \begin{listing}[H]
-\caption{\t{src\_prepare}, format~6}
+\caption{\t{src_prepare}, format~6}
 \begin{verbatim}
 src_prepare() {
     if declare -p PATCHES | grep -q "^declare -a "; then
@@ -143,16 +143,16 @@ src_prepare() {
 \end{verbatim}
 \end{listing}
 
-For other EAPIs supporting \t{src\_prepare}, the default implementation used when the ebuild lacks
-the \t{src\_prepare} function is a no-op.
+For other EAPIs supporting \t{src_prepare}, the default implementation used when the ebuild lacks
+the \t{src_prepare} function is a no-op.
 
 \ChangeWhenAddingAnEAPI{6}
-\begin{centertable}{\t{src\_prepare} support and behaviour for EAPIs}
+\begin{centertable}{\t{src_prepare} support and behaviour for EAPIs}
     \label{tab:src-prepare-table}
     \begin{tabular}{lll}
       \toprule
       \multicolumn{1}{c}{\textbf{EAPI}} &
-      \multicolumn{1}{c}{\textbf{Supports \t{src\_prepare}?}} &
+      \multicolumn{1}{c}{\textbf{Supports \t{src_prepare}?}} &
       \multicolumn{1}{c}{\textbf{Format}} \\
       \midrule
       0, 1              & No  & Not applicable \\
@@ -162,19 +162,19 @@ the \t{src\_prepare} function is a no-op.
     \end{tabular}
 \end{centertable}
 
-\subsection{src\_configure}
+\subsection{src_configure}
 
-\featurelabel{src-configure} The \t{src\_configure} function is only called for EAPIs listed in
+\featurelabel{src-configure} The \t{src_configure} function is only called for EAPIs listed in
 table~\ref{tab:src-configure-table} as supporting it.
 
 The initial working directory is \t{S}, with an error or fallback to \t{WORKDIR} as discussed in
 section~\ref{sec:s-to-workdir-fallback}.
 
-The \t{src\_configure} function configures the package's build environment. The default
-implementation used when the ebuild lacks the \t{src\_configure} function shall behave as:
+The \t{src_configure} function configures the package's build environment. The default
+implementation used when the ebuild lacks the \t{src_configure} function shall behave as:
 
 \begin{listing}[H]
-\caption{\t{src\_configure}}
+\caption{\t{src_configure}}
 \begin{verbatim}
 src_configure() {
     if [[ -x ${ECONF_SOURCE:-.}/configure ]]; then
@@ -185,12 +185,12 @@ src_configure() {
 \end{listing}
 
 \ChangeWhenAddingAnEAPI{6}
-\begin{centertable}{EAPIs supporting \t{src\_configure}}
+\begin{centertable}{EAPIs supporting \t{src_configure}}
     \label{tab:src-configure-table}
     \begin{tabular}{ll}
       \toprule
       \multicolumn{1}{c}{\textbf{EAPI}} &
-      \multicolumn{1}{c}{\textbf{Supports \t{src\_configure}?}} \\
+      \multicolumn{1}{c}{\textbf{Supports \t{src_configure}?}} \\
       \midrule
       0, 1              & No  \\
       2, 3, 4, 5, 6     & Yes \\
@@ -198,20 +198,20 @@ src_configure() {
     \end{tabular}
 \end{centertable}
 
-\subsection{src\_compile}
+\subsection{src_compile}
 
-\featurelabel{src-compile} The \t{src\_compile} function configures the package's build environment
-in EAPIs lacking \t{src\_configure}, and builds the package in all EAPIs.
+\featurelabel{src-compile} The \t{src_compile} function configures the package's build environment
+in EAPIs lacking \t{src_configure}, and builds the package in all EAPIs.
 
 The initial working directory is \t{S}, with an error or fallback to \t{WORKDIR} as discussed in
 section~\ref{sec:s-to-workdir-fallback}.
 
 \featurelabel{src-compile-0} For EAPIs listed in table~\ref{tab:src-compile-table} as using format
-0, the default implementation used when the ebuild lacks the \t{src\_compile} function shall behave
+0, the default implementation used when the ebuild lacks the \t{src_compile} function shall behave
 as:
 
 \begin{listing}[H]
-\caption{\t{src\_compile}, format~0}
+\caption{\t{src_compile}, format~0}
 \begin{verbatim}
 src_compile() {
     if [[ -x ./configure ]]; then
@@ -225,11 +225,11 @@ src_compile() {
 \end{listing}
 
 \featurelabel{src-compile-1} For EAPIs listed in table~\ref{tab:src-compile-table} as using format
-1, the default implementation used when the ebuild lacks the \t{src\_compile} function shall behave
+1, the default implementation used when the ebuild lacks the \t{src_compile} function shall behave
 as:
 
 \begin{listing}[H]
-\caption{\t{src\_compile}, format~1}
+\caption{\t{src_compile}, format~1}
 \begin{verbatim}
 src_compile() {
     if [[ -x ${ECONF_SOURCE:-.}/configure ]]; then
@@ -243,11 +243,11 @@ src_compile() {
 \end{listing}
 
 \featurelabel{src-compile-2} For EAPIs listed in table~\ref{tab:src-compile-table} as using format
-2, the default implementation used when the ebuild lacks the \t{src\_compile} function shall behave
+2, the default implementation used when the ebuild lacks the \t{src_compile} function shall behave
 as:
 
 \begin{listing}[H]
-\caption{\t{src\_compile}, format~2}
+\caption{\t{src_compile}, format~2}
 \begin{verbatim}
 src_compile() {
     if [[ -f Makefile ]] || [[ -f GNUmakefile ]] || [[ -f makefile ]]; then
@@ -258,7 +258,7 @@ src_compile() {
 \end{listing}
 
 \ChangeWhenAddingAnEAPI{6}
-\begin{centertable}{\t{src\_compile} behaviour for EAPIs}
+\begin{centertable}{\t{src_compile} behaviour for EAPIs}
     \label{tab:src-compile-table}
     \begin{tabular}{ll}
       \toprule
@@ -272,13 +272,13 @@ src_compile() {
     \end{tabular}
 \end{centertable}
 
-\subsection{src\_test}
+\subsection{src_test}
 
-The \t{src\_test} function runs unit tests for the newly built but not yet installed package as
+The \t{src_test} function runs unit tests for the newly built but not yet installed package as
 provided.
 
 The initial working directory must be \t{S} if that exists, falling back to \t{WORKDIR} otherwise.
-The default implementation used when the ebuild lacks the \t{src\_test} function must, if tests are
+The default implementation used when the ebuild lacks the \t{src_test} function must, if tests are
 enabled, run \t{emake check} if and only if such a target is available, or if not run
 \t{emake test} if and only if such a target is available. In both cases, if \t{emake} returns
 non-zero the build must be aborted.
@@ -286,11 +286,11 @@ non-zero the build must be aborted.
 \featurelabel{parallel-tests} For EAPIs listed in table~\ref{tab:src-test-table} as not supporting
 parallel tests, the \t{emake} command must be called with option \t{-j1}.
 
-The \t{src\_test} function may be disabled by \t{RESTRICT}\@. See section~\ref{sec:restrict}. It may
+The \t{src_test} function may be disabled by \t{RESTRICT}\@. See section~\ref{sec:restrict}. It may
 be disabled by user too, using a PM-specific mechanism.
 
 \ChangeWhenAddingAnEAPI{6}
-\begin{centertable}{\t{src\_test} behaviour for EAPIs}
+\begin{centertable}{\t{src_test} behaviour for EAPIs}
     \label{tab:src-test-table}
     \begin{tabular}{ll}
       \toprule
@@ -303,20 +303,20 @@ be disabled by user too, using a PM-specific mechanism.
     \end{tabular}
 \end{centertable}
 
-\subsection{src\_install}
+\subsection{src_install}
 
-\featurelabel{src-install} The \t{src\_install} function installs the package's content to a
+\featurelabel{src-install} The \t{src_install} function installs the package's content to a
 directory specified in \t{D}.
 
 The initial working directory is \t{S}, with an error or fallback to \t{WORKDIR} as discussed in
 section~\ref{sec:s-to-workdir-fallback}.
 
 \featurelabel{src-install-4} For EAPIs listed in table~\ref{tab:src-install-table} as using format
-4, the default implementation used when the ebuild lacks the \t{src\_install} function shall behave
+4, the default implementation used when the ebuild lacks the \t{src_install} function shall behave
 as:
 
 \begin{listing}[H]
-\caption{\t{src\_install}, format~4}
+\caption{\t{src_install}, format~4}
 \begin{verbatim}
 src_install() {
     if [[ -f Makefile ]] || [[ -f GNUmakefile ]] || [[ -f makefile ]]; then
@@ -339,11 +339,11 @@ src_install() {
 \end{listing}
 
 \featurelabel{src-install-6} For EAPIs listed in table~\ref{tab:src-install-table} as using format
-6, the default implementation used when the ebuild lacks the \t{src\_install} function shall behave
+6, the default implementation used when the ebuild lacks the \t{src_install} function shall behave
 as:
 
 \begin{listing}[H]
-\caption{\t{src\_install}, format~6}
+\caption{\t{src_install}, format~6}
 \begin{verbatim}
 src_install() {
     if [[ -f Makefile ]] || [[ -f GNUmakefile ]] || [[ -f makefile ]]; then
@@ -354,11 +354,11 @@ src_install() {
 \end{verbatim}
 \end{listing}
 
-For other EAPIs, the default implementation used when the ebuild lacks the \t{src\_install} function
+For other EAPIs, the default implementation used when the ebuild lacks the \t{src_install} function
 is a no-op.
 
 \ChangeWhenAddingAnEAPI{6}
-\begin{centertable}{\t{src\_install} behaviour for EAPIs}
+\begin{centertable}{\t{src_install} behaviour for EAPIs}
     \label{tab:src-install-table}
     \begin{tabular}{ll}
       \toprule
@@ -372,66 +372,66 @@ is a no-op.
     \end{tabular}
 \end{centertable}
 
-\subsection{pkg\_preinst}
+\subsection{pkg_preinst}
 
-The \t{pkg\_preinst} function performs any special tasks that are required immediately before
+The \t{pkg_preinst} function performs any special tasks that are required immediately before
 merging the package to the live filesystem. It must not write outside of the directories specified
 by the \t{ROOT} and \t{D} environment variables.
 
-\t{pkg\_preinst} must be run with full access to all files and directories below that specified by
+\t{pkg_preinst} must be run with full access to all files and directories below that specified by
 the \t{ROOT} and \t{D} environment variables.
 
-\subsection{pkg\_postinst}
+\subsection{pkg_postinst}
 
-The \t{pkg\_postinst} function performs any special tasks that are required immediately after
+The \t{pkg_postinst} function performs any special tasks that are required immediately after
 merging the package to the live filesystem. It must not write outside of the directory specified
 in the \t{ROOT} environment variable.
 
-\t{pkg\_postinst}, like, \t{pkg\_preinst}, must be run with full access to all files and directories
+\t{pkg_postinst}, like, \t{pkg_preinst}, must be run with full access to all files and directories
 below that specified by the \t{ROOT} environment variable.
 
-\subsection{pkg\_prerm}
+\subsection{pkg_prerm}
 
-The \t{pkg\_prerm} function performs any special tasks that are required immediately before
+The \t{pkg_prerm} function performs any special tasks that are required immediately before
 unmerging the package from the live filesystem. It must not write outside of the directory specified
 by the \t{ROOT} environment variable.
 
-\t{pkg\_prerm} must be run with full access to all files and directories below that specified by
+\t{pkg_prerm} must be run with full access to all files and directories below that specified by
 the \t{ROOT} environment variable.
 
-\subsection{pkg\_postrm}
+\subsection{pkg_postrm}
 
-The \t{pkg\_postrm} function performs any special tasks that are required immediately after
+The \t{pkg_postrm} function performs any special tasks that are required immediately after
 unmerging the package from the live filesystem. It must not write outside of the directory specified
 by the \t{ROOT} environment variable.
 
-\t{pkg\_postrm} must be run with full access to all files and directories below that specified by
+\t{pkg_postrm} must be run with full access to all files and directories below that specified by
 the \t{ROOT} environment variable.
 
-\subsection{pkg\_config}
+\subsection{pkg_config}
 
-The \t{pkg\_config} function performs any custom steps required to configure a package after it has been
+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}.
+\t{pkg_config} must be run with full access to all files and directories inside of \t{ROOT}.
 
-\subsection{pkg\_info}
+\subsection{pkg_info}
 
-\featurelabel{pkg-info} The \t{pkg\_info} function may be called by the package manager when
+\featurelabel{pkg-info} The \t{pkg_info} function may be called by the package manager when
 displaying information about an installed package. In EAPIs listed in table~\ref{tab:pkg-info-table}
-as supporting \t{pkg\_info} on non-installed packages, it may also be called by the package manager
+as supporting \t{pkg_info} on non-installed packages, it may also be called by the package manager
 when displaying information about a non-installed package. In this case, ebuild authors should note
 that dependencies may not be installed.
 
-\t{pkg\_info} must not write to the filesystem.
+\t{pkg_info} must not write to the filesystem.
 
 \ChangeWhenAddingAnEAPI{6}
-\begin{centertable}{EAPIs supporting \t{pkg\_info} on non-installed packages}
+\begin{centertable}{EAPIs supporting \t{pkg_info} on non-installed packages}
     \label{tab:pkg-info-table}
     \begin{tabular}{ll}
       \toprule
       \multicolumn{1}{c}{\textbf{EAPI}} &
-      \multicolumn{1}{c}{\textbf{Supports \t{pkg\_info} on non-installed packages?}} \\
+      \multicolumn{1}{c}{\textbf{Supports \t{pkg_info} on non-installed packages?}} \\
       \midrule
       0, 1, 2, 3        & No  \\
       4, 5, 6           & Yes \\
@@ -439,36 +439,36 @@ that dependencies may not be installed.
     \end{tabular}
 \end{centertable}
 
-\subsection{pkg\_nofetch}
+\subsection{pkg_nofetch}
 
-The \t{pkg\_nofetch} function is run when the fetch phase of an fetch-restricted ebuild is run, and
+The \t{pkg_nofetch} function is run when the fetch phase of an fetch-restricted ebuild is run, and
 the relevant source files are not available. It should direct the user to download all relevant
 source files from their respective locations, with notes concerning licensing if applicable.
 
-\t{pkg\_nofetch} must require no write access to any part of the filesystem.
+\t{pkg_nofetch} must require no write access to any part of the filesystem.
 
 \subsection{Default phase functions}
 \label{sec:default-phase-funcs}
 
 \featurelabel{default-phase-funcs} In EAPIs listed in
-table~\ref{tab:default-phase-function-table} as supporting \t{default\_} phase functions, a function
-named \t{default\_}(phase) that behaves as the default implementation for that EAPI shall be defined
+table~\ref{tab:default-phase-function-table} as supporting \t{default_} phase functions, a function
+named \t{default_}(phase) that behaves as the default implementation for that EAPI shall be defined
 when executing any ebuild phase listed in the table. Ebuilds must not call these functions except
 when in the phase in question.
 
 \ChangeWhenAddingAnEAPI{6}
-\begin{centertable}{EAPIs supporting \t{default\_} phase functions}
+\begin{centertable}{EAPIs supporting \t{default_} phase functions}
     \label{tab:default-phase-function-table}
     \begin{tabular}{l P{26em}}
       \toprule
       \multicolumn{1}{c}{\textbf{EAPI}} &
-      \multicolumn{1}{c}{\textbf{Supports \t{default\_} functions in phases}} \\
+      \multicolumn{1}{c}{\textbf{Supports \t{default_} functions in phases}} \\
       \midrule
       0, 1              & None \\
-      2, 3              & \t{pkg\_nofetch}, \t{src\_unpack}, \t{src\_prepare}, \t{src\_configure},
-                          \t{src\_compile}, \t{src\_test} \\
-      4, 5, 6           & \t{pkg\_nofetch}, \t{src\_unpack}, \t{src\_prepare}, \t{src\_configure},
-                          \t{src\_compile}, \t{src\_install}, \t{src\_test} \\
+      2, 3              & \t{pkg_nofetch}, \t{src_unpack}, \t{src_prepare}, \t{src_configure},
+                          \t{src_compile}, \t{src_test} \\
+      4, 5, 6           & \t{pkg_nofetch}, \t{src_unpack}, \t{src_prepare}, \t{src_configure},
+                          \t{src_compile}, \t{src_install}, \t{src_test} \\
       \bottomrule
     \end{tabular}
 \end{centertable}
@@ -478,56 +478,56 @@ when in the phase in question.
 The call order for installing a package is:
 
 \begin{compactitem}
-\item \t{pkg\_pretend} (only for EAPIs listed in table~\ref{tab:pkg-pretend-table}), which is called
+\item \t{pkg_pretend} (only for EAPIs listed in table~\ref{tab:pkg-pretend-table}), which is called
     outside of the normal call order process.
-\item \t{pkg\_setup}
-\item \t{src\_unpack}
-\item \t{src\_prepare} (only for EAPIs listed in table~\ref{tab:src-prepare-table})
-\item \t{src\_configure} (only for EAPIs listed in table~\ref{tab:src-configure-table})
-\item \t{src\_compile}
-\item \t{src\_test} (except if \t{RESTRICT=test} or disabled by user)
-\item \t{src\_install}
-\item \t{pkg\_preinst}
-\item \t{pkg\_postinst}
+\item \t{pkg_setup}
+\item \t{src_unpack}
+\item \t{src_prepare} (only for EAPIs listed in table~\ref{tab:src-prepare-table})
+\item \t{src_configure} (only for EAPIs listed in table~\ref{tab:src-configure-table})
+\item \t{src_compile}
+\item \t{src_test} (except if \t{RESTRICT=test} or disabled by user)
+\item \t{src_install}
+\item \t{pkg_preinst}
+\item \t{pkg_postinst}
 \end{compactitem}
 
 The call order for uninstalling a package is:
 
 \begin{compactitem}
-\item \t{pkg\_prerm}
-\item \t{pkg\_postrm}
+\item \t{pkg_prerm}
+\item \t{pkg_postrm}
 \end{compactitem}
 
 The call order for upgrading, downgrading or reinstalling a package is:
 
 \begin{compactitem}
-\item \t{pkg\_pretend} (only for EAPIs listed in table~\ref{tab:pkg-pretend-table}), which is called
+\item \t{pkg_pretend} (only for EAPIs listed in table~\ref{tab:pkg-pretend-table}), which is called
     outside of the normal call order process.
-\item \t{pkg\_setup}
-\item \t{src\_unpack}
-\item \t{src\_prepare} (only for EAPIs listed in table~\ref{tab:src-prepare-table})
-\item \t{src\_configure} (only for EAPIs listed in table~\ref{tab:src-configure-table})
-\item \t{src\_compile}
-\item \t{src\_test} (except if \t{RESTRICT=test})
-\item \t{src\_install}
-\item \t{pkg\_preinst}
-\item \t{pkg\_prerm} for the package being replaced
-\item \t{pkg\_postrm} for the package being replaced
-\item \t{pkg\_postinst}
+\item \t{pkg_setup}
+\item \t{src_unpack}
+\item \t{src_prepare} (only for EAPIs listed in table~\ref{tab:src-prepare-table})
+\item \t{src_configure} (only for EAPIs listed in table~\ref{tab:src-configure-table})
+\item \t{src_compile}
+\item \t{src_test} (except if \t{RESTRICT=test})
+\item \t{src_install}
+\item \t{pkg_preinst}
+\item \t{pkg_prerm} for the package being replaced
+\item \t{pkg_postrm} for the package being replaced
+\item \t{pkg_postinst}
 \end{compactitem}
 
 Note: When up- or downgrading a package in EAPI 0 or 1, the last four phase functions can
-alternatively be called in the order \t{pkg\_preinst}, \t{pkg\_postinst}, \t{pkg\_prerm},
-\t{pkg\_postrm}. This behaviour is deprecated.
+alternatively be called in the order \t{pkg_preinst}, \t{pkg_postinst}, \t{pkg_prerm},
+\t{pkg_postrm}. This behaviour is deprecated.
 
-The \t{pkg\_config}, \t{pkg\_info} and \t{pkg\_nofetch} functions are not called in a normal
-sequence. The \t{pkg\_pretend} function is called some unspecified time before a (possibly
+The \t{pkg_config}, \t{pkg_info} and \t{pkg_nofetch} functions are not called in a normal
+sequence. The \t{pkg_pretend} function is called some unspecified time before a (possibly
 hypothetical) normal sequence.
 
 For installing binary packages, the \t{src} phases are not called.
 
-When building binary packages that are not to be installed locally, the \t{pkg\_preinst}
-and \t{pkg\_postinst} functions are not called.
+When building binary packages that are not to be installed locally, the \t{pkg_preinst}
+and \t{pkg_postinst} functions are not called.
 
 % vim: set filetype=tex fileencoding=utf8 et tw=100 spell spelllang=en :