commit: fd9c0342503dd70838f2ecc75434d76349304079
Author: Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Mon Apr 29 16:28:46 2024 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Tue May 7 17:16:53 2024 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=fd9c0342
Fix internal references
Internal links referring to sections were broken by the previous
"Sentence case devmanual" commit.
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
appendices/common-problems/text.xml | 8 ++++----
appendices/contributors/text.xml | 8 ++++----
appendices/devbook-guide/text.xml | 14 +++++++-------
archs/alpha/text.xml | 2 +-
archs/amd64/text.xml | 17 +++++++++--------
archs/mips/text.xml | 2 +-
archs/sparc/text.xml | 4 ++--
ebuild-maintenance/git/text.xml | 2 +-
ebuild-writing/eapi/text.xml | 9 +++++----
ebuild-writing/file-format/text.xml | 4 ++--
ebuild-writing/functions/pkg_nofetch/text.xml | 2 +-
.../functions/src_compile/build-environment/text.xml | 2 +-
ebuild-writing/functions/src_test/text.xml | 2 +-
ebuild-writing/functions/text.xml | 6 +++---
ebuild-writing/misc-files/metadata/text.xml | 4 ++--
ebuild-writing/misc-files/patches/text.xml | 4 ++--
ebuild-writing/use-conditional-code/text.xml | 2 +-
ebuild-writing/user-submitted/text.xml | 2 +-
ebuild-writing/variables/text.xml | 2 +-
eclass-writing/text.xml | 2 +-
function-reference/build-functions/text.xml | 2 +-
function-reference/query-functions/text.xml | 4 ++--
function-reference/sandbox-functions/text.xml | 2 +-
general-concepts/autotools/text.xml | 2 +-
general-concepts/dependencies/text.xml | 4 ++--
general-concepts/ebuild-revisions/text.xml | 4 ++--
general-concepts/manifest/text.xml | 2 +-
general-concepts/mirrors/text.xml | 3 ++-
general-concepts/sandbox/text.xml | 2 +-
general-concepts/slotting/text.xml | 4 ++--
general-concepts/tree/text.xml | 2 +-
keywording/text.xml | 2 +-
profiles/categories/text.xml | 2 +-
profiles/use.mask/text.xml | 2 +-
quickstart/text.xml | 7 ++++---
tools-reference/bash/text.xml | 2 +-
tools-reference/text.xml | 2 +-
37 files changed, 75 insertions(+), 71 deletions(-)
diff --git a/appendices/common-problems/text.xml
b/appendices/common-problems/text.xml
index 84bb610..6ebc098 100644
--- a/appendices/common-problems/text.xml
+++ b/appendices/common-problems/text.xml
@@ -59,8 +59,8 @@ in use, there are various alternatives:
Usually when any of the above are used in global scope, it is to manipulate
a version or program name string. These should be avoided in favour of pure
<c>bash</c> constructs. The built-in helpers of EAPI 7 are useful here. See
- <uri link="::ebuild-writing/variables/#Version and Name Formatting
Issues"/>
- and <uri link="::tools-reference/bash/#Bash Variable Manipulation"/>.
+ <uri link="::ebuild-writing/variables/#Version and name formatting
issues"/>
+ and <uri link="::tools-reference/bash/#Bash variable manipulation"/>.
</dd>
<dt>
<c>has_version</c>, <c>best_version</c>
@@ -101,7 +101,7 @@ for security reasons. If this message is shown, you have a
couple of options:
</li>
<li>
Use <c>append-ldflags</c> (see
- <uri
link="::ebuild-writing/functions/src_compile/build-environment/#Adding
Additional Flags"/>)
+ <uri
link="::ebuild-writing/functions/src_compile/build-environment/#Adding
additional flags"/>)
to add <c>-Wl,-z,now</c>. This will affect <e>all</e> binaries installed,
not just the setXid ones.
</li>
</ul>
@@ -131,7 +131,7 @@ inheritance occurring. Most commonly:
</li>
<li>
When working with eclasses in an overlay with a stale cache. See <uri
- link="::general-concepts/overlay/#Overlay and Eclasses"/>.
+ link="::general-concepts/overlay/#Overlay and eclasses"/>.
</li>
<li>
When working with a stale Portage cache.
diff --git a/appendices/contributors/text.xml b/appendices/contributors/text.xml
index 2808df1..da7fe3b 100644
--- a/appendices/contributors/text.xml
+++ b/appendices/contributors/text.xml
@@ -13,7 +13,7 @@ This page lists the contributions to the Gentoo Development
Guide:
Main Content
</author>
<author name="Grant Goodyear" email="g2boo...@gentoo.org">
- <uri link="::tools-reference/cat/#Here Documents"/>
+ <uri link="::tools-reference/cat/#Here documents"/>
</author>
<author name="Aaron Walker" email="ka0t...@gentoo.org">
<uri link="::tasks-reference/completion/"/>
@@ -23,7 +23,7 @@ This page lists the contributions to the Gentoo Development
Guide:
</author>
<author name="Tom Martin" email="sla...@gentoo.org">
<uri link="::appendices/editor-configuration/emacs/"/>,
- <uri link="::general-concepts/use-flags/#Conflicting USE Flags"/>
+ <uri link="::general-concepts/use-flags/#Conflicting USE flags"/>
</author>
<author name="Paul Varner" email="fuzzy...@gentoo.org">
<uri link="::ebuild-writing/functions/src_unpack/rpm-sources/"/>
@@ -33,7 +33,7 @@ This page lists the contributions to the Gentoo Development
Guide:
</author>
<author name="Diego Pettenò" email="flamee...@gentoo.org">
<uri link="::tasks-reference/pam/"/>,
- <uri link="::general-concepts/autotools/#aclocal and m4 Files"/>
+ <uri link="::general-concepts/autotools/#aclocal and m4 files"/>
</author>
<author name="Fernando J. Pereda" email="fe...@gentoo.org">
<uri link="::archs/alpha/"/>
@@ -123,7 +123,7 @@ Misc
Search functionality
</author>
<author name="Mike Frysinger" email="vap...@gentoo.org">
- <uri link="::ebuild-writing/misc-files/patches/#Clean Patch Howto"/>
+ <uri link="::ebuild-writing/misc-files/patches/#Clean patch howto"/>
</author>
<author name="Sam James" email="s...@gentoo.org">
<uri link="::eclass-writing/"/>,
diff --git a/appendices/devbook-guide/text.xml
b/appendices/devbook-guide/text.xml
index 243017d..5c4aec7 100644
--- a/appendices/devbook-guide/text.xml
+++ b/appendices/devbook-guide/text.xml
@@ -533,12 +533,12 @@ here syndrome</uri> as recommended by the
<p>
DevBook XML makes it really easy to reference other parts of the document using
hyperlinks. You can create a link pointing to another chapter, like
-<uri link="::ebuild-writing/file-format/">Ebuild File Format</uri>, by typing
-<c><uri link="::ebuild-writing/file-format/">Ebuild File
-Format</uri></c>, i.e., two colons followed by the relative path from
+<uri link="::ebuild-writing/file-format/">Ebuild file format</uri>, by typing
+<c><uri link="::ebuild-writing/file-format/">Ebuild file
+format</uri></c>, i.e. two colons followed by the relative path from
the root node. To refer to a section in another chapter, like
-<uri link="::quickstart/#First Ebuild">First Ebuild</uri>, type
-<c><uri link="::quickstart/#First Ebuild">First Ebuild</uri></c>.
+<uri link="::quickstart/#First ebuild">First ebuild</uri>, type
+<c><uri link="::quickstart/#First ebuild">First ebuild</uri></c>.
</p>
<p>
@@ -546,9 +546,9 @@ If the link target's chapter (or section etc.) title is to
be used as the link
text, an empty <c><uri></c> element can be used. As a matter of fact,
I could have written the two examples above in more compact form:
<c><uri link="::ebuild-writing/file-format/"/></c> and
-<c><uri link="::quickstart/#First Ebuild"/></c> render as
+<c><uri link="::quickstart/#First ebuild"/></c> render as
<uri link="::ebuild-writing/file-format/"/> and
-<uri link="::quickstart/#First Ebuild"/>, respectively.
+<uri link="::quickstart/#First ebuild"/>, respectively.
</p>
</body>
diff --git a/archs/alpha/text.xml b/archs/alpha/text.xml
index f068317..9d0500e 100644
--- a/archs/alpha/text.xml
+++ b/archs/alpha/text.xml
@@ -87,7 +87,7 @@ which the compiler was built.
<p>
The <c>-mieee</c> flag <b>should</b> always be used unless you have a deep
knowledge
of the Alpha architecture, so the comments on
-<uri link="::general-concepts/user-environment/#Not Filtering Variables"/> are
+<uri link="::general-concepts/user-environment/#Not filtering variables"/> are
really important on Alpha.
</p>
diff --git a/archs/amd64/text.xml b/archs/amd64/text.xml
index 4f3b7da..05cce5f 100644
--- a/archs/amd64/text.xml
+++ b/archs/amd64/text.xml
@@ -123,7 +123,7 @@ or omitting any bit-width option will default to producing
64-bit code.
If you've chosen a multilib profile, glibc will be built twice, once 64-bit and
once 32-bit. This is because nearly every application links against glibc.
To understand how this is done in the ebuild, read
-<uri link="::archs/amd64/#The ABI Variable"/>.
+<uri link="::archs/amd64/#The ABI variable"/>.
</p>
</body>
@@ -277,9 +277,9 @@ This is what <c>/usr/include/asm/types.h</c> looks like on
an AMD64 box:
As you can see, this is just a wrapper that decides which file you need
depending on the parameter <c>-D</c> given to gcc. You'll probably run into
some troubles if you try to compile something by hand and forget to append
-<c>-D__x86_64__</c> to your <c>CFLAGS</c>. Of course, this is <b>not
necessary</b> when
-using Portage. For an explanation, see the <uri link="::archs/amd64/#The ABI
Variable"/>
-section.
+<c>-D__x86_64__</c> to your <c>CFLAGS</c>. Of course, this is
+<b>not necessary</b> when using Portage. For an explanation, see the
+<uri link="::archs/amd64/#The ABI variable"/> section.
</p>
</body>
@@ -291,10 +291,11 @@ section.
<p>
Whenever Portage builds something on amd64, it has to decide whether it should
-be 32-bit or 64-bit. As stated in <uri link="::archs/amd64/#Headers and
Multilib"/>
-the <c>__i386__</c> or <c>__x86_64__</c> respectively, is needed in
<c>CDEFINE</c>.
-Also, gcc has to know what code it should produce, therefore <c>-m32</c> or
<c>-m64</c>
-must be appended to CFLAGS. This is done via <c>profile.bashrc</c>. All you
need to do
+be 32-bit or 64-bit. As stated in
+<uri link="::archs/amd64/#Headers and multilib"/> the <c>__i386__</c> or
+<c>__x86_64__</c> respectively, is needed in <c>CDEFINE</c>. Also, gcc has to
+know what code it should produce, therefore <c>-m32</c> or <c>-m64</c> must be
+appended to CFLAGS. This is done via <c>profile.bashrc</c>. All you need to do
if you want to build a package 32-bit is to set <c>ABI=x86</c>.
</p>
diff --git a/archs/mips/text.xml b/archs/mips/text.xml
index 141664a..9e4ca16 100644
--- a/archs/mips/text.xml
+++ b/archs/mips/text.xml
@@ -70,7 +70,7 @@ between these, talk to the MIPS team.
<p>
Because <c>CFLAGS</c> are sometimes used to specify ISA and ABI information,
it is
vital that packages honour this setting. See
-<uri link="::general-concepts/user-environment/#Not Filtering Variables"/>.
+<uri link="::general-concepts/user-environment/#Not filtering variables"/>.
</p>
</body>
diff --git a/archs/sparc/text.xml b/archs/sparc/text.xml
index fccf53c..c828e83 100644
--- a/archs/sparc/text.xml
+++ b/archs/sparc/text.xml
@@ -55,7 +55,7 @@ buses.
<note>
This section is in addition to the guidelines in
-<uri link="::keywording/#Keywording on Upgrades"/>. It discusses
+<uri link="::keywording/#Keywording on upgrades"/>. It discusses
<e>additional</e> requirements for the SPARC architecture.
</note>
@@ -116,7 +116,7 @@ code. Depending upon the application, this can be anywhere
up to five times
slower than <c>v9</c> code when running on an UltraSparc <d/> cryptographic and
graphics applications which make heavy use of integer multiplication and
division are especially badly hit. For this reason, the comments in
-<uri link="::general-concepts/user-environment/#Not Filtering Variables"/>
+<uri link="::general-concepts/user-environment/#Not filtering variables"/>
are especially important on SPARC.
</p>
diff --git a/ebuild-maintenance/git/text.xml b/ebuild-maintenance/git/text.xml
index 82967cc..6ad3837 100644
--- a/ebuild-maintenance/git/text.xml
+++ b/ebuild-maintenance/git/text.xml
@@ -142,7 +142,7 @@ used. The valid uses of git include:
Whenever <c>pkgdev</c> is not used to commit, you need to manually verify all
packages affected by the commit using <c>pkgcheck scan --commits</c>. Also,
when using <c>git</c> manually, you must perform a manual sign-off to the
-<uri link="::general-concepts/copyright-policy/#Certificate of origin"/> using
+<uri link="::general-concepts/copyright-policy/#Certificate of Origin"/> using
the <c>-s </c> or <c>--signoff</c> option with your git commit commands. Make
sure you have read and understand the actual certificate.
</p>
diff --git a/ebuild-writing/eapi/text.xml b/ebuild-writing/eapi/text.xml
index f470676..26795cf 100644
--- a/ebuild-writing/eapi/text.xml
+++ b/ebuild-writing/eapi/text.xml
@@ -70,9 +70,10 @@ is the best. Using the features of the latest EAPI is
encouraged.
<p>
Gentoo policy is to support upgrades for installations at least a year old
-with no/little intervention and up to two years old with minor intervention. To
-achieve this, developers must avoid using the latest EAPI in ebuilds within
-the <c>@system</c> set (see <uri
link="::general-concepts/dependencies/#implicit-system-dependency"/>)
+with no/little intervention and up to two years old with minor intervention.
+To achieve this, developers must avoid using the latest EAPI in ebuilds within
+the <c>@system</c> set
+(see <uri link="::general-concepts/dependencies/#Implicit system dependency"/>)
or its dependencies.
</p>
@@ -603,7 +604,7 @@ installation targets.
<li><c>ver_test</c> compares two versions</li>
</ul>
<p>
- See <uri link="::ebuild-writing/variables/#Version and Name Formatting
Issues"/>
+ See <uri link="::ebuild-writing/variables/#Version and name formatting
issues"/>
for examples of common uses or
<uri
link="https://dev.gentoo.org/~mgorny/articles/the-ultimate-guide-to-eapi-7.html#version-manipulation-and-comparison-commands";>
an in-depth look</uri>
diff --git a/ebuild-writing/file-format/text.xml
b/ebuild-writing/file-format/text.xml
index aa7bb72..bca3dad 100644
--- a/ebuild-writing/file-format/text.xml
+++ b/ebuild-writing/file-format/text.xml
@@ -116,7 +116,7 @@ Overall, this gives us a filename like
<c>libfoo-1.2.5b_pre5-r2.ebuild</c>.
</p>
<p>
-The <uri link ="::ebuild-writing/variables/#Version and Name Formatting
Issues">
+The <uri link ="::ebuild-writing/variables/#Version and name formatting
issues">
EAPI 7 version commands</uri> may be used to manipulate and extract
ebuild version components.
</p>
@@ -146,7 +146,7 @@ for this is $(upcoming-version)_preYYYYMMDD.
<p>
The policy for so-called <e>live</e> ebuilds
-(see <uri link="::ebuild-writing/functions/src_unpack/#src_unpack Actions"/>)
+(see <uri link="::ebuild-writing/functions/src_unpack/#src_unpack actions"/>)
is to use <c>9999</c> as the version (or as the last version component). For
packages with more than 4 digits e.g. YYYYMMDD format, <c>99999999</c> is an
acceptable alternative.
diff --git a/ebuild-writing/functions/pkg_nofetch/text.xml
b/ebuild-writing/functions/pkg_nofetch/text.xml
index fdf4639..292c447 100644
--- a/ebuild-writing/functions/pkg_nofetch/text.xml
+++ b/ebuild-writing/functions/pkg_nofetch/text.xml
@@ -68,7 +68,7 @@ be referenced.
<body>
<p>
This function is only triggered for packages which have <c>RESTRICT="fetch"</c>
-(see <uri link="::general-concepts/mirrors/#Restricting Automatic Mirroring"/>)
+(see <uri link="::general-concepts/mirrors/#Restricting automatic mirroring"/>)
set, and only if one or more components listed in <c>SRC_URI</c> are not
already available in the <c>distfiles</c> directory.
</p>
diff --git a/ebuild-writing/functions/src_compile/build-environment/text.xml
b/ebuild-writing/functions/src_compile/build-environment/text.xml
index a9fc035..de9bea7 100644
--- a/ebuild-writing/functions/src_compile/build-environment/text.xml
+++ b/ebuild-writing/functions/src_compile/build-environment/text.xml
@@ -18,7 +18,7 @@ Except where otherwise specified, any function which operates
on
<p>
Ebuilds must not simply ignore user CFLAGS, CXXFLAGS or LDFLAGS <d/> see
-<uri link="::general-concepts/user-environment/#Not Filtering Variables"/>.
+<uri link="::general-concepts/user-environment/#Not filtering variables"/>.
</p>
</body>
diff --git a/ebuild-writing/functions/src_test/text.xml
b/ebuild-writing/functions/src_test/text.xml
index 04d180c..793e99f 100644
--- a/ebuild-writing/functions/src_test/text.xml
+++ b/ebuild-writing/functions/src_test/text.xml
@@ -72,7 +72,7 @@ to run it. Sometimes the package will need additional
dependencies for this,
i.e., dependencies that are only required to run the test suite. Such test-only
dependencies should be specified in DEPEND or BDEPEND behind a USE flag;
often, the <c>test</c> USE flag will be used for this. Please refer to the
-section on <uri link="::general-concepts/dependencies/#Test Dependencies"/>
+section on <uri link="::general-concepts/dependencies/#Test dependencies"/>
for more information.
</p>
diff --git a/ebuild-writing/functions/text.xml
b/ebuild-writing/functions/text.xml
index 0c1fbd6..c5a6cbc 100644
--- a/ebuild-writing/functions/text.xml
+++ b/ebuild-writing/functions/text.xml
@@ -60,12 +60,12 @@ Downloading a package's source happens before any of these
phases, so
<c>emerge --fetchonly</c> should perform all the network access you
need (unless you're using live ebuilds). Network access outside of
this would not be cached locally (e.g. in <c>${DISTDIR}</c>, see
-<uri link="::ebuild-writing/variables/#Predefined Read-Only Variables"/>),
+<uri link="::ebuild-writing/variables/#Predefined read-only variables"/>),
which makes it hard to have reproducible builds (see
-<uri link="::ebuild-writing/functions/src_unpack/vcs-sources/#Disadvantages of
VCS Sources"/>).
+<uri link="::ebuild-writing/functions/src_unpack/vcs-sources/#Disadvantages of
vcs sources"/>).
Avoid network access in any phase by using local files, extending
<c>SRC_URI</c> (see
-<uri link="::ebuild-writing/variables/#Ebuild-defined Variables"/>), etc.
+<uri link="::ebuild-writing/variables/#Ebuild-defined variables"/>), etc.
</p>
</body>
diff --git a/ebuild-writing/misc-files/metadata/text.xml
b/ebuild-writing/misc-files/metadata/text.xml
index cde4364..04a4164 100644
--- a/ebuild-writing/misc-files/metadata/text.xml
+++ b/ebuild-writing/misc-files/metadata/text.xml
@@ -114,7 +114,7 @@ metadata.xml:
<ti>
This tag contains a description for a category or a package.
For packages, it is used to augment the
- <uri link="::ebuild-writing/variables/#Ebuild-defined Variables">
+ <uri link="::ebuild-writing/variables/#Ebuild-defined variables">
DESCRIPTION</uri> field in the ebuilds themselves. This tag has
two optional subtags: <c><pkg></c> and <c><cat></c>.
</ti>
@@ -302,7 +302,7 @@ There are also some attributes that can be used with these
tags:
When this attribute is required on the <c><flag></c> tag, it
simply contains the name of the USE flag. For the
<c><slot></c> tag, it specifies the
- <uri link="::general-concepts/slotting/#Slot Names">
+ <uri link="::general-concepts/slotting/#Slot names">
slot name</uri> to which it applies. A slot name of <c>*</c>
allows for a single <c><slot></c> tag to match all the slots of a
package, in which case no other slot tags may be present.
diff --git a/ebuild-writing/misc-files/patches/text.xml
b/ebuild-writing/misc-files/patches/text.xml
index 239fd1b..862910c 100644
--- a/ebuild-writing/misc-files/patches/text.xml
+++ b/ebuild-writing/misc-files/patches/text.xml
@@ -25,13 +25,13 @@ number in the patch name as a suffix to the version part
<d/>
<p>
Larger patches should be
-<uri link="::general-concepts/mirrors/#Suitable Download Hosts">
+<uri link="::general-concepts/mirrors/#Suitable download hosts">
mirrored</uri>, preferably on the Gentoo Infrastructure. When
mirroring patches, choosing a name that will not cause conflicts is
important — the <c>${P}</c> prefix is highly recommended
here. Mirrored patches are often compressed with <c>xz</c> or
<c>bzip2</c>. Remember to list these patches in <c>SRC_URI</c>. Please
-see <uri link="::ebuild-maintenance/new-ebuild/#The files Directory"/>
+see <uri link="::ebuild-maintenance/new-ebuild/#The files directory"/>
for more information.
</p>
diff --git a/ebuild-writing/use-conditional-code/text.xml
b/ebuild-writing/use-conditional-code/text.xml
index 57ea99a..cb818a2 100644
--- a/ebuild-writing/use-conditional-code/text.xml
+++ b/ebuild-writing/use-conditional-code/text.xml
@@ -21,7 +21,7 @@ occasionally seen in older code must <b>not</b> be used. This
is because, since
<note>
<c>die</c> will not work as expected within a subshell, so code in the
form <c>use foo && ( blah ; blah )</c> should be avoided in favour of
a proper if
-statement. See <uri link="::ebuild-writing/error-handling/#die and
Subshells"/>.
+statement. See <uri link="::ebuild-writing/error-handling/#die and
subshells"/>.
</note>
<codesample lang="ebuild">
diff --git a/ebuild-writing/user-submitted/text.xml
b/ebuild-writing/user-submitted/text.xml
index 15576fb..9e2bc1c 100644
--- a/ebuild-writing/user-submitted/text.xml
+++ b/ebuild-writing/user-submitted/text.xml
@@ -24,7 +24,7 @@ The user-submitted ebuild must not contain custom headers
like this:
Such information should be included in the git commit message instead.
The use of tags such as <c>Suggested-By:</c> or <c>Reported-By:</c> in
the commit message, as explained in the
-<uri link="::ebuild-maintenance/git/#Git Commit Message Format">
+<uri link="::ebuild-maintenance/git/#Git commit message format">
commit message format section</uri>, is highly encouraged.
Note that ebuilds received in the form of git patches or pull requests
will have the user as the commit author by default, in which case
diff --git a/ebuild-writing/variables/text.xml
b/ebuild-writing/variables/text.xml
index 6b8565b..97e5995 100644
--- a/ebuild-writing/variables/text.xml
+++ b/ebuild-writing/variables/text.xml
@@ -676,7 +676,7 @@ Finally, to state "at least one of foo, bar, or baz must be
set":
REQUIRED_USE="|| ( foo bar baz )"
</codesample>
<important>
-See section <uri link="::general-concepts/use-flags/#Conflicting USE Flags"/>
+See section <uri link="::general-concepts/use-flags/#Conflicting USE flags"/>
for when (and when not) to use <c>REQUIRED_USE</c>.
</important>
</body>
diff --git a/eclass-writing/text.xml b/eclass-writing/text.xml
index d93e2b0..8c4c910 100644
--- a/eclass-writing/text.xml
+++ b/eclass-writing/text.xml
@@ -10,7 +10,7 @@ This section provides a brief introduction to eclass
authoring.
<important>
You should reread the
-<uri link="::general-concepts/overlay/#Overlay and Eclasses"/>
+<uri link="::general-concepts/overlay/#Overlay and eclasses"/>
and <uri link="::general-concepts/portage-cache/"/> sections before continuing.
</important>
</body>
diff --git a/function-reference/build-functions/text.xml
b/function-reference/build-functions/text.xml
index 09e6053..5e7b28d 100644
--- a/function-reference/build-functions/text.xml
+++ b/function-reference/build-functions/text.xml
@@ -34,7 +34,7 @@ during the unpack and compile stages.
<ti>
Wrapper for <c>./configure</c>. Passes on all <c>args</c>. Will abort
(via <c>die</c>) should <c>configure</c> fail.
- See <uri
link="::ebuild-writing/functions/src_configure/configuring/#econf Options"/>
+ See <uri
link="::ebuild-writing/functions/src_configure/configuring/#econf options"/>
for details.
</ti>
</tr>
diff --git a/function-reference/query-functions/text.xml
b/function-reference/query-functions/text.xml
index ec7e069..529bb77 100644
--- a/function-reference/query-functions/text.xml
+++ b/function-reference/query-functions/text.xml
@@ -131,8 +131,8 @@ query variables and similar state.
</ti>
<ti>
True if <c>pkg</c> (can include
- <uri link="::general-concepts/dependencies/#version specifiers"/> and
- <uri link="::general-concepts/dependencies/#built with use
dependencies"/>)
+ <uri link="::general-concepts/dependencies/#Version specifiers"/> and
+ <uri link="::general-concepts/dependencies/#Built with USE
dependencies"/>)
is installed. Example: <c>has_version
"=app-editors/nano-2.5.3[nls,spell]"</c>.
(EAPI=7) An option may also be specified to query certain types of
dependencies.
diff --git a/function-reference/sandbox-functions/text.xml
b/function-reference/sandbox-functions/text.xml
index 86cf05c..fa68d07 100644
--- a/function-reference/sandbox-functions/text.xml
+++ b/function-reference/sandbox-functions/text.xml
@@ -63,7 +63,7 @@ recursive, so to allow predicted writes to <c>/foo/bar</c>
and <c>/foo/baz</c>,
<p>
See <uri link="::general-concepts/sandbox/"/> for details on how the sandbox
works.
-See <uri link="::appendices/common-problems/#Handling Access Violations"/>
+See <uri link="::appendices/common-problems/#Handling access violations"/>
for how to handle sandbox-related build problems.
</p>
diff --git a/general-concepts/autotools/text.xml
b/general-concepts/autotools/text.xml
index 02a3554..39edb19 100644
--- a/general-concepts/autotools/text.xml
+++ b/general-concepts/autotools/text.xml
@@ -496,7 +496,7 @@ This is handled via the macro <c>AC_SUBST(VARNAME)</c> in
<c>configure.ac</c>.
<p>
Sometimes, badly behaved <c>Makefile.am</c> files will override user variables
such
as <c>CFLAGS</c>. This must not be allowed <d/> see
-<uri link="::general-concepts/user-environment/#Not Filtering Variables"/>.
+<uri link="::general-concepts/user-environment/#Not filtering variables"/>.
There are separate special variables which should be used in these situations
<d/> for setting <c>CFLAGS</c>. for example, a <c>Makefile.am</c> should use
<c>AM_CFLAGS</c> so that user preferences are not ignored.
diff --git a/general-concepts/dependencies/text.xml
b/general-concepts/dependencies/text.xml
index 29998cd..3201d91 100644
--- a/general-concepts/dependencies/text.xml
+++ b/general-concepts/dependencies/text.xml
@@ -74,7 +74,7 @@ distinctions still apply even if it isn't, strictly speaking,
cross-compiling.
<p>
Build dependencies are used to specify any dependencies that are required
to unpack, patch, compile, test or install the package (but see
-<uri link="::general-concepts/dependencies/#Implicit System Dependency"/> for
+<uri link="::general-concepts/dependencies/#Implicit system dependency"/> for
exemptions).
</p>
@@ -382,7 +382,7 @@ DEPEND="qt5? ( ~dev-qt/qtcore-5.15.2:5 )
In <c>EAPI=5</c> and higher, you can use slot operators appended to the package
name to declare whether or not your package should be rebuilt after the
versions
satisfying its runtime dependencies are updated to versions with a different
slot
-or <uri link="::general-concepts/slotting/#Sub-Slots">sub-slot</uri>:
+or <uri link="::general-concepts/slotting/#Sub-slots">sub-slot</uri>:
</p>
<ul>
diff --git a/general-concepts/ebuild-revisions/text.xml
b/general-concepts/ebuild-revisions/text.xml
index d363516..2c8531a 100644
--- a/general-concepts/ebuild-revisions/text.xml
+++ b/general-concepts/ebuild-revisions/text.xml
@@ -7,7 +7,7 @@
<p>
Ebuilds may have a Gentoo revision number associated with them. This is a
<c>-rX</c> suffix, where <c>X</c> is an integer <d/> see
-<uri link="::ebuild-writing/file-format/#File Naming Rules"/>.
+<uri link="::ebuild-writing/file-format/#File naming rules"/>.
This component must only be used for Gentoo changes, not upstream releases.
An ebuild with no explicit revision number has the implicit <c>-r0</c>
revision.
@@ -40,7 +40,7 @@ of thumb could be used as a guideline:
as such), then a new revision should be introduced and the old one
kept. If the package has stable keywords, the new revision should
be dropped to <c>~arch</c> (see
- <uri link="::keywording/#Keywording on Upgrades"/>).
+ <uri link="::keywording/#Keywording on upgrades"/>).
For any such revision bump, the new ebuild should be based
on the previous revision to ensure that fixes aren't dropped
accidentally.
diff --git a/general-concepts/manifest/text.xml
b/general-concepts/manifest/text.xml
index 11ed7cb..eb0d700 100644
--- a/general-concepts/manifest/text.xml
+++ b/general-concepts/manifest/text.xml
@@ -70,7 +70,7 @@ longer matches the computed checksum of the fetched distfile.
<p>
Special care is also required with regard to
-<uri link="::general-concepts/mirrors/#Replacing Automatically Mirrored Files">
+<uri link="::general-concepts/mirrors/#Replacing automatically mirrored files">
mirrors</uri>.
</p>
</body>
diff --git a/general-concepts/mirrors/text.xml
b/general-concepts/mirrors/text.xml
index 927a3a6..5bc8f73 100644
--- a/general-concepts/mirrors/text.xml
+++ b/general-concepts/mirrors/text.xml
@@ -70,7 +70,8 @@ fetch and start distributing the new version.
<p>
Updating an existing distfile is generally cause for concern and must be done
-with care, see <uri link="::general-concepts/manifest/#Updating Manifests"/>.
+with care, see
+<uri link="::general-concepts/manifest/#Updating Manifest files"/>.
</p>
<p>
diff --git a/general-concepts/sandbox/text.xml
b/general-concepts/sandbox/text.xml
index 8dcaeb1..06da4d3 100644
--- a/general-concepts/sandbox/text.xml
+++ b/general-concepts/sandbox/text.xml
@@ -22,7 +22,7 @@ generally <b>not</b> the correct solution.
<p>
See <uri link="::function-reference/sandbox-functions/"/> for details on
sandbox-related functions. See <uri
-link="::appendices/common-problems/#Handling Access Violations"/> for
suggestions
+link="::appendices/common-problems/#Handling access violations"/> for
suggestions
on fixing sandbox-related build problems.
</p>
</body>
diff --git a/general-concepts/slotting/text.xml
b/general-concepts/slotting/text.xml
index a0fb1e1..f45263f 100644
--- a/general-concepts/slotting/text.xml
+++ b/general-concepts/slotting/text.xml
@@ -41,7 +41,7 @@ possible that the user may have <c>foo-2.0</c> installed and
no <c>foo-1.x</c> a
<p>
To <c>DEPEND</c> upon a package in a specific slot, refer to
-<uri link="::general-concepts/dependencies/#SLOT Dependencies"/>.
+<uri link="::general-concepts/dependencies/#SLOT dependencies"/>.
</p>
</body>
@@ -55,7 +55,7 @@ but it's undesirable or inconvenient to allow some of these
versions to be insta
simultaneously. In <c>EAPI=5</c> and higher, this situation can be handled by
using sub-slots, which are delimited from the regular slot by a <c>/</c>
character,
as in <c>SLOT="slot/subslot"</c>. Packages can
-<uri link="::general-concepts/dependencies/#Slot Operators">request to be
+<uri link="::general-concepts/dependencies/#Slot operators">request to be
automatically rebuilt</uri> when the subslot of a runtime dependency changes.
</p>
diff --git a/general-concepts/tree/text.xml b/general-concepts/tree/text.xml
index e686b54..f1877fd 100644
--- a/general-concepts/tree/text.xml
+++ b/general-concepts/tree/text.xml
@@ -102,7 +102,7 @@ U+0021 to U+007E (see also
<uri
link="https://www.gentoo.org/glep/glep-0031.html#suitable-characters-for-file-and-directory-names";>
GLEP 31</uri>). Any characters that have a special meaning in Bash or in
<c>SRC_URI</c> should also be avoided. If necessary, upstream files can be
-<uri link="::ebuild-writing/variables/#Renaming Sources">renamed</uri> using
+<uri link="::ebuild-writing/variables/#Renaming sources">renamed</uri> using
<c>-></c> syntax.
</p>
diff --git a/keywording/text.xml b/keywording/text.xml
index 4174249..4360b49 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -241,7 +241,7 @@ manually removed during the testing process, which is
cumbersome.
<important>
When committing, make sure that you reference any bugs in the commit message.
-See <uri link="::ebuild-maintenance/git/#Git Commit Message Format"/> for how
+See <uri link="::ebuild-maintenance/git/#Git commit message format"/> for how
to do this.
</important>
diff --git a/profiles/categories/text.xml b/profiles/categories/text.xml
index 70dfe8f..c6bfa49 100644
--- a/profiles/categories/text.xml
+++ b/profiles/categories/text.xml
@@ -16,7 +16,7 @@ Please consult the gentoo-dev mailing list before adding a
new category.
<p>
The <c>categories</c> file is a straight list. For descriptions, see <uri
-link="::ebuild-writing/misc-files/metadata/#Category Metadata"/>.
+link="::ebuild-writing/misc-files/metadata/#Category metadata"/>.
</p>
</body>
diff --git a/profiles/use.mask/text.xml b/profiles/use.mask/text.xml
index 4de9686..543d439 100644
--- a/profiles/use.mask/text.xml
+++ b/profiles/use.mask/text.xml
@@ -38,7 +38,7 @@ additions are sorted chronologically, starting at the top of
the file
</p>
<p>
-See <uri link="::general-concepts/use-flags/#noblah USE Flags"/> for more
discussion.
+See <uri link="::general-concepts/use-flags/#noblah USE flags"/> for more
discussion.
</p>
</body>
diff --git a/quickstart/text.xml b/quickstart/text.xml
index f311ad9..32e3ede 100644
--- a/quickstart/text.xml
+++ b/quickstart/text.xml
@@ -195,7 +195,7 @@ failed.
<p>
In the ctags example, we didn't tell Portage about any dependencies. As it
happens, that's ok, because ctags only needs a basic toolchain to compile and
-run (see <uri link="::general-concepts/dependencies/#Implicit System
Dependency"/>
+run (see <uri link="::general-concepts/dependencies/#Implicit system
dependency"/>
for why we don't need to depend upon those explicitly). However, life is rarely
that simple.
</p>
@@ -233,7 +233,7 @@ Again, you can see the ebuild header and the various
informational variables. In
<c>SRC_URI</c>, <c>${PN}</c> is used to get the package's
name <e>without</e> the version suffix (there are more of these
variables <d/> see
-<uri link="::ebuild-writing/variables/#Predefined Read-Only Variables"/>).
+<uri link="::ebuild-writing/variables/#Predefined read-only variables"/>).
</p>
<p>
@@ -300,7 +300,8 @@ Note the <c>${FILESDIR}/${P}-destdir.patch</c> <d/> this
refers to
<c>detox-1.1.0-destdir.patch</c>, which lives in the <c>files/</c>
subdirectory in the Gentoo repository. Larger patch files must go on your
developer's space at <c>dev.gentoo.org</c> rather than in <c>files/</c> or
-mirrors <d/> see <uri link="::general-concepts/mirrors/#Gentoo Mirrors"/> and
+mirrors <d/>
+see <uri link="::general-concepts/mirrors/#Suitable download hosts"/> and
<uri link="::ebuild-writing/functions/src_prepare/eapply/"/>.
</p>
diff --git a/tools-reference/bash/text.xml b/tools-reference/bash/text.xml
index 1c2148e..57c3d56 100644
--- a/tools-reference/bash/text.xml
+++ b/tools-reference/bash/text.xml
@@ -486,7 +486,7 @@ done < some_file
</codesample>
<p>
-See <uri link="::ebuild-writing/error-handling/#die and Subshells"/>
+See <uri link="::ebuild-writing/error-handling/#die and subshells"/>
for an explanation of why <c>while read < file</c> should
be used over <c>cat file | while read</c>.
</p>
diff --git a/tools-reference/text.xml b/tools-reference/text.xml
index 781d4af..7ed3ce3 100644
--- a/tools-reference/text.xml
+++ b/tools-reference/text.xml
@@ -12,7 +12,7 @@ ebuilds.
<p>
Please keep in mind the need for
-<uri link="::ebuild-writing/error-handling/#The die Function">error
handling</uri>
+<uri link="::ebuild-writing/error-handling/#The die function">error
handling</uri>
when using these tools in ebuilds.
</p>
</body>
