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>

3 files changed, 15 insertions, 15 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="g2boojum@gentoo.org">
-  <uri link="::tools-reference/cat/#Here Documents"/>
+  <uri link="::tools-reference/cat/#Here documents"/>
 </author>
 <author name="Aaron Walker" email="ka0ttic@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="slarti@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="fuzzyray@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="flameeyes@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="ferdy@gentoo.org">
   <uri link="::archs/alpha/"/>
@@ -123,7 +123,7 @@ Misc
   Search functionality
 </author>
 <author name="Mike Frysinger" email="vapier@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="sam@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>&lt;uri link="::ebuild-writing/file-format/"&gt;Ebuild File
-Format&lt;/uri&gt;</c>, i.e., two colons followed by the relative path from
+<uri link="::ebuild-writing/file-format/">Ebuild file format</uri>, by typing
+<c>&lt;uri link="::ebuild-writing/file-format/"&gt;Ebuild file
+format&lt;/uri&gt;</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>&lt;uri link="::quickstart/#First Ebuild"&gt;First Ebuild&lt;/uri&gt;</c>.
+<uri link="::quickstart/#First ebuild">First ebuild</uri>, type
+<c>&lt;uri link="::quickstart/#First ebuild"&gt;First ebuild&lt;/uri&gt;</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>&lt;uri&gt;</c> element can be used. As a matter of fact,
 I could have written the two examples above in more compact form:
 <c>&lt;uri link="::ebuild-writing/file-format/"/&gt;</c> and
-<c>&lt;uri link="::quickstart/#First Ebuild"/&gt;</c> render as
+<c>&lt;uri link="::quickstart/#First ebuild"/&gt;</c> render as
 <uri link="::ebuild-writing/file-format/"/> and
-<uri link="::quickstart/#First Ebuild"/>, respectively.
+<uri link="::quickstart/#First ebuild"/>, respectively.
 </p>
 
 </body>