[PATCH] docs: Commandline and menu entry commands are now separated

[Glenn Washburn]

The menu entry commands now have their own section. Change the wording in
the section that they were in to reflect this.

Signed-off-by: Glenn Washburn <development@efficientek.com>
---
 docs/grub.texi | 11 +++++------
 1 file changed, 5 insertions(+), 6 deletions(-)

diff --git a/docs/grub.texi b/docs/grub.texi
index 1324175fbe3f..9d4adf0b8ab6 100644
--- a/docs/grub.texi
+++ b/docs/grub.texi
@@ -3167,9 +3167,8 @@ The command-line interface provides a prompt and after it 
an editable
 text area much like a command-line in Unix or DOS. Each command is
 immediately executed after it is entered@footnote{However, this
 behavior will be changed in the future version, in a user-invisible
-way.}. The commands (@pxref{Command-line and menu entry commands}) are a
-subset of those available in the configuration file, used with exactly
-the same syntax.
+way.}. The commands (@pxref{Commands}) are a subset of those available
+in the configuration file, used with exactly the same syntax.
 
 Cursor movement and editing of the text on the line can be done via a
 subset of the functions available in the Bash shell:
@@ -3910,7 +3909,7 @@ shell}.
 * Menu-specific commands::
 * Loader commands::
 * General commands::
-* Command-line and menu entry commands::
+* Command-line commands::
 * Networking commands::
 * Undocumented commands::
 @end menu
@@ -4283,8 +4282,8 @@ printed.
 @end deffn
 
 
-@node Command-line and menu entry commands
-@section The list of command-line and menu entry commands
+@node Command-line commands
+@section The list of command-line commands
 
 These commands are usable in the command-line and in menu entries.  If
 you forget a command, you can run the command @command{help}
-- 
2.34.1