From 9c983ade4d56f9585fd2a806c8ee1650e180b3eb Mon Sep 17 00:00:00 2001
From: Pascal Wittmann <mail@pascal-wittmann.de>
Date: Tue, 2 Jun 2015 11:21:22 +0200
Subject: [PATCH] doc: fix references

---
 doc/language-support.xml | 6 +++---
 doc/stdenv.xml           | 2 +-
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/doc/language-support.xml b/doc/language-support.xml
index 14e8aa7a7ba..def0de1d91f 100644
--- a/doc/language-support.xml
+++ b/doc/language-support.xml
@@ -257,7 +257,7 @@ are provided with all modules included.</para>
     <term><varname>buildEnv</varname></term>
     <listitem><para>
         Function to build python interpreter environments with extra packages bundled together.
-        See <xref linkend="python-build-env" /> for usage and documentation.
+        See <xref linkend="ssec-python-build-env" /> for usage and documentation.
     </para></listitem>
   </varlistentry>
 
@@ -587,7 +587,7 @@ sed -i '/ = data_files/d' setup.py</programlisting>
     <listitem><para>
       There is no need to have global site-packages in Nix. Each package has isolated
       dependency tree and installing any python package will only populate <varname>$PATH</varname>
-      inside user environment. See <xref linkend="python-build-env" /> to create self-contained
+      inside user environment. See <xref linkend="ssec-python-build-env" /> to create self-contained
       interpreter with a set of packages.
     </para></listitem>
   </varlistentry>
@@ -876,7 +876,7 @@ Runtime) instead of the OpenJRE.</para>
   in <link xlink:href="https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/lua-modules/generic/default.nix">
   <filename>pkgs/development/lua-modules/generic/default.nix</filename></link>
   and works similarly to <varname>buildPerlPackage</varname>. (See
-  <xref linkend="ssec-language-perl"/> for details.)
+  <xref linkend="sec-language-perl"/> for details.)
 </para>
 
 <para>
diff --git a/doc/stdenv.xml b/doc/stdenv.xml
index 58310834fd2..4e51db73010 100644
--- a/doc/stdenv.xml
+++ b/doc/stdenv.xml
@@ -59,7 +59,7 @@ build.  To make this easier, the standard environment breaks the
 package build into a number of <emphasis>phases</emphasis>, all of
 which can be overridden or modified individually: unpacking the
 sources, applying patches, configuring, building, and installing.
-(There are some others; see <xref linkend="ssec-stdenv-phases"/>.)
+(There are some others; see <xref linkend="sec-stdenv-phases"/>.)
 For instance, a package that doesn’t supply a makefile but instead has
 to be compiled “manually” could be handled like this: