[release-notes: 1/4] explaining that grub goes in the MBR, not the partition. Some XML cleanup.

[Pete Travis]

commit 07da8be1221ddeda641a1c9ffd02404080c30c88
Author: Pete Travis <immanetize at fedoraproject.org>
Date:   Thu Jan 3 23:13:30 2013 -0700

    explaining that grub goes in the MBR, not the partition. Some XML cleanup.

 en-US/Installation.xml |   24 ++++++++++++++++++++----
 1 files changed, 20 insertions(+), 4 deletions(-)
---
diff --git a/en-US/Installation.xml b/en-US/Installation.xml
index ecb6491..4c28c4b 100644
--- a/en-US/Installation.xml
+++ b/en-US/Installation.xml
@@ -22,14 +22,30 @@
   <section>
     <title>New Installer User Interface</title>
     <para>
-      The <application>anaconda</application> installer has been totally redesigned for Fedora 18. Users will now have more flexibility in how they configure their installation. Some tasks will run in the background to speed the installation process. Consult the Fedora 18 <productname>Installation Guide</productname> at <ulink type="http" url="https://docs.fedoraproject.org">https://docs.fedoraproject.org</ulink> for more information.
+      The <application>anaconda</application> installer has been totally redesigned for Fedora 18.  Users will now have more flexibility in how they configure their installation. Some tasks will run in the background to speed the installation process. Consult the Fedora 18 <productname>Installation Guide</productname> at <ulink type="http" url="https://docs.fedoraproject.org">https://docs.fedoraproject.org</ulink> for more information.
     </para>
     <note>
+      <title>Advanced Features</title>
     	<para>
-    		<title>Advanced Features</title>
-    			System configuration with <application>anaconda</application> is more powerful and flexible through the use of <feature>kickstart</feature> files.  Kickstart files automate installation and accommodate advanced requirements, such as multiple desktop environments, atypical storage, and more. Learn more about kickstart options in the <productname>Installation Guide</productname>. 
+    		
+    			System configuration with <application>anaconda</application> is more powerful and flexible through the use of <function>kickstart</function> files. Kickstart files automate installation and accommodate advanced requirements not presented in the GUI, such as multiple desktop environments, atypical storage, and more. Learn more about kickstart options in the <productname>Installation Guide</productname>. 
 		</para>    
-    </</note>	
+    </note>	
+    <section>
+      <title>Installing grub</title>
+      <para>
+	Fedora has used <application>GRUB2</application> for several releases. A great improvement over legacy <application>GRUB</application>, <application>GRUB2</application> supports more filesystems, virtual block devices such as <application>mdadm</application> and <application>LVM</application>, automatically scans for and configures available operating systems, and presents visual improvements.  This added functionality makes the lives of Fedora users much easier, but comes at the cost of size. <application>GRUB2</application> fits in the <function>Master Boot Record</function> of a drive, but many filesystems do not leave room for <application>GRUB2</application> without special configuration.
+      </para>
+      <para>
+	<application>Anaconda</application> now follows the recommendation of upstream <application>GRUB</application> developers and does not install <application>GRUB2</application> to partitions. Users with multiboot systems are encouraged to make use of GRUB's OS detection:
+	<screen>
+	  <command>
+	    grub2-mkconfig -o /boot/grub2/grub.cfg
+	  </command>
+	</screen>
+	Users can also choose to skip bootloader installation with anaconda. GRUB can be manually installed to a partition with the <function>force</function> option, at the risk of filesystem damage, or another bootloader can be used.
+      </para>
+    </section>
   </section>
   <section>
     <title>Changed package group names</title>