[system-administrators-guide] Update links to new section ID

[stephenw]

commit 01f12ab20a4e33c4c61e8f0079bb9d9bd60e276d
Author: Stephen Wadeley 
Date:   Wed Nov 4 09:08:12 2015 +0100

Update links to new section ID

Making Persistent Changes to a GRUB 2 Menu Using the grubby Tool

en-US/Working_with_the_GRUB_2_Boot_Loader.xml |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)
---
diff --git a/en-US/Working_with_the_GRUB_2_Boot_Loader.xml b/en-US/Working_with_the_GRUB_2_Boot_Loader.xml
index 5b9c600..702eef4 100644
--- a/en-US/Working_with_the_GRUB_2_Boot_Loader.xml
+++ b/en-US/Working_with_the_GRUB_2_Boot_Loader.xml
@@ -34,7 +34,7 @@
         The GRUB 2 configuration file, <filename>grub.cfg</filename>, is generated during installation, or by invoking the <application>/usr/sbin/grub2-mkconfig</application> utility, and is automatically updated by <command>grubby</command> each time a new kernel is installed. When regenerated manually using <application>grub2-mkconfig</application>, the file is generated according to the template files located in <filename class="directory">/etc/grub.d/</filename>, and custom settings in the <filename>/etc/default/grub</filename> file. Edits of <filename>grub.cfg</filename> will be lost any time <application>grub2-mkconfig</application> is used to regenerate the file, so care must be taken to reflect any manual changes in <filename>/etc/default/grub</filename> as well.
    			</para>
         <para>
-          Normal operations on <filename>grub.cfg</filename>, such as the removal and addition of new kernels, should be done using the <command>grubby</command> tool and, for scripts, using <command>new-kernel-pkg</command> tool. If you use <command>grubby</command> to modify the default kernel the changes will be inherited when new kernels are installed. For more information on <command>grubby</command>, see <xref linkend="sec-Configuring_GRUB_2_Using_the_grubby_Tool" />.
+          Normal operations on <filename>grub.cfg</filename>, such as the removal and addition of new kernels, should be done using the <command>grubby</command> tool and, for scripts, using <command>new-kernel-pkg</command> tool. If you use <command>grubby</command> to modify the default kernel the changes will be inherited when new kernels are installed. For more information on <command>grubby</command>, see <xref linkend="sec-Making_Persistent_Changes_to_a_GRUB_2_Menu_Using_the_grubby_Tool" />.
         </para>
         <para>
 The <filename>/etc/default/grub</filename> file is used by the <command>grub2-mkconfig</command> tool, which is used by <systemitem>anaconda</systemitem> when creating <filename>grub.cfg</filename> during the installation process, and can be used in the event of a system failure, for example if the boot loader configurations need to be recreated. In general, it is not recommended to replace the <filename>grub.cfg</filename> file by manually running <filename>grub2-mkconfig</filename> except as a last resort. Note that any manual changes to <filename>/etc/default/grub</filename> require rebuilding the <filename>grub.cfg</filename> file.
@@ -95,7 +95,7 @@ menuentry 'Fedora, with Linux 3.17.4-301.fc21.x86_64' --class fedora --class gnu
       </listitem>
       <listitem>
         <para>
-         To make persistent changes to a running system, see <xref linkend="sec-Configuring_GRUB_2_Using_the_grubby_Tool" />.
+         To make persistent changes to a running system, see <xref linkend="sec-Making_Persistent_Changes_to_a_GRUB_2_Menu_Using_the_grubby_Tool" />.
         </para>
       </listitem>
       <listitem>