Fix internal references

Internal links referring to sections were broken by the previous
"Sentence case devmanual" commit.

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

4 files changed, 13 insertions, 12 deletions

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>