nightmorph    12/10/31 06:22:47

  Modified:             grub2-migration.xml
  Log:
  minor typo + punctuation fixes. also updated license to cc-by-sa 3.0. no 
content changes, so no revbump.

Revision  Changes    Path
1.3                  xml/htdocs/doc/en/grub2-migration.xml

file : 
http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/grub2-migration.xml?rev=1.3&view=markup
plain: 
http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/grub2-migration.xml?rev=1.3&content-type=text/plain
diff : 
http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/grub2-migration.xml?r1=1.2&r2=1.3

Index: grub2-migration.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/grub2-migration.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- grub2-migration.xml 27 Jul 2012 16:52:33 -0000      1.2
+++ grub2-migration.xml 31 Oct 2012 06:22:47 -0000      1.3
@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/grub2-migration.xml,v 1.2 
2012/07/27 16:52:33 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/grub2-migration.xml,v 1.3 
2012/10/31 06:22:47 nightmorph Exp $ -->
 
 <guide>
 <title>GRUB2 migration from GRUB Legacy</title>
@@ -15,7 +15,7 @@
 </abstract>
 
 <!-- The content of this document is licensed under the CC-BY-SA license -->
-<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
+<!-- See http://creativecommons.org/licenses/by-sa/3.0 -->
 <license/>
 
 <version>2</version>
@@ -158,15 +158,15 @@
 
 <p>
 Because a broken GRUB configuration could mean an unbootable
-system, we want to test our GRUB2 configuration before making it permenant.
+system, we want to test our GRUB2 configuration before making it permanent.
 To do this we will chainload GRUB2 from GRUB Legacy. This is done by adding
 a new section into <path>/boot/grub/grub.conf</path>. An example is shown
 below.
 </p>
 
 <note>
-Beaware that your root maybe different from <c>(hd0,0)</c> used in the
-example and make sure you reuse the same root value from your
+Be aware that your root may be different from <c>(hd0,0)</c> used in the
+example, and make sure you reuse the same root value from your
 <path>/boot/grub/grub.conf</path>.
 </note>
 
@@ -187,12 +187,12 @@
 </pre>
 
 <p>
-At this point you should reboot your machine and select the
-<c>GRUB2 Chainload</c> from the GRUB menu when your machine begins to boot.
-You will be presented with another GRUB menu which should advertise itself
-as GRUB 2.0.0 or higher at the top and show your available kernel(s) to boot.
-Should this not work, simply reboot your system and pick your normal boot
-option instead of <c>GRUB2 Chainload</c>.
+At this point you should reboot your machine and select <c>GRUB2 Chainload</c>
+from the GRUB menu when your machine begins to boot.  You will be presented 
with
+another GRUB menu which should advertise itself as GRUB 2.0.0 or higher at the
+top and show your available kernel(s) to boot.  Should this not work, simply
+reboot your system and pick your normal boot option instead of <c>GRUB2
+Chainload</c>.
 </p>
 
 </body>
@@ -202,13 +202,13 @@
 <body>
 
 <p>
-At this point if everything worked successfully you can replace GRUB Legacy
+At this point, if everything worked successfully, you can replace GRUB Legacy
 and remove it from your system.
 </p>
 
 <note>
 Since you've rebooted your system, you may need to mount <path>/boot</path>
-again. You should also take note to use your boot drive path instead of
+again. Make sure to use your own boot drive path instead of
 <path>/dev/sda</path>.
 </note>
 




Reply via email to