- revert incorrect change to grub.texi

diff --git a/ChangeLog b/ChangeLog
index 9625c2ddb5ff38750308b276ec02cd921cb2d0ed..00126d41ccadd8e4936588abe73047046be27bd7 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,11 +1,3 @@
-2003-05-23  Jason Thomas  <jason@intology.com.au>
-
-       * docs/grub.texi (Configuration): The documentation had the wrong
-       directory for the menu.lst file, so I corrected this to /boot/grub or
-       /boot/boot/grub with a comment in parenthesises about /boot being a
-       serperate partition.
-       Reported by <bigtoe416@yahoo.co>
-
 2003-05-04  Yoshinori K. Okuji  <okuji@enbug.org>
 
        * docs/grub.texi (partnew): Fixed the inconsistency between the

diff --git a/docs/grub.texi b/docs/grub.texi
index d0102ec03616ae0c893925ad79bb9f0cf189be76..f6bf09e830ecb84448e429c899da64218d28b4a4 100644 (file)
--- a/docs/grub.texi
+++ b/docs/grub.texi
@@ -989,9 +989,7 @@ OS. There's a solution to that - GRUB provides a menu interface
 keys) that will do everything to boot an OS.
 
 To enable the menu, you need a configuration file,
-@file{menu.lst} under the @file{/boot/grub} directory or possibly the
-@file{/boot/boot/grub} directory (if your boot directory is a seperate
-partition). We'll analyze an example
+@file{menu.lst} under the boot directory. We'll analyze an example
 file.
 
 The file first contains some general settings, the menu interface