* annotate.texi: Add @noindent where needed. From Dmitry

Sivachenko <dima@Chg.RU>.
	* gdb.texinfo: Indexing fix.  From Dmitry Sivachenko.

gdb/doc/ChangeLog

@@ -1,3 +1,9 @@
+2001-06-17  Eli Zaretskii  <eliz@is.elta.co.il>
+
+	* annotate.texi: Add @noindent where needed.  From Dmitry
+	Sivachenko <dima@Chg.RU>.
+	* gdb.texinfo: Indexing fix.  From Dmitry Sivachenko.
+
 2001-06-16  Andrew Cagney  <ac131313@redhat.com>
 
 	* gdb.texinfo (Protocol): Fix typo.  Extra parenthesis.

gdb/doc/annotate.texi

@@ -158,6 +158,7 @@ the annotation looks like
 ^Z^Zvalue-history-end
 @end smallexample
 
+@noindent
 where @var{history-number} is the number it is getting in the value
 history, @var{history-string} is a string, such as @samp{$5 = }, which
 introduces the value to the user, @var{the-value} is the output
@@ -192,6 +193,7 @@ from the @code{backtrace} command), it annotates it as follows:
 ^Z^Zarg-end
 @end smallexample
 
+@noindent
 where @var{argument-name} is the name of the argument,
 @var{separator-string} is text which separates the name from the value
 for the user's benefit (such as @samp{=}), and @var{value-flags} and
@@ -214,6 +216,7 @@ When printing a structure, @value{GDBN} annotates it as follows:
 ^Z^Zfield-end
 @end smallexample
 
+@noindent
 where @var{field-name} is the name of the field, @var{separator-string}
 is text which separates the name from the value for the user's benefit
 (such as @samp{=}), and @var{value-flags} and @var{the-value} have the
@@ -225,6 +228,7 @@ When printing an array, @value{GDBN} annotates it as follows:
 ^Z^Zarray-section-begin @var{array-index} @var{value-flags}
 @end smallexample
 
+@noindent
 where @var{array-index} is the index of the first element being
 annotated and @var{value-flags} has the same meaning as in a
 @code{value-history-begin} annotation.  This is followed by any number
@@ -280,6 +284,7 @@ The frame annotation begins with
 @var{level-string}
 @end smallexample
 
+@noindent
 where @var{level} is the number of the frame (0 is the innermost frame,
 and other frames have positive numbers), @var{address} is the address of
 the code executing in that frame, and @var{level-string} is a string
@@ -428,6 +433,7 @@ the results of the display are annotated:
 ^Z^Zdisplay-end
 @end smallexample
 
+@noindent
 where @var{number} is the number of the display, @var{number-separator}
 is intended to separate the number from what follows for the user,
 @var{format} includes information such as the size, format, or other
@@ -550,6 +556,7 @@ The output from the @code{info breakpoints} command is annotated as follows:
 ^Z^Zbreakpoints-table
 @end smallexample
 
+@noindent
 where @var{header-entry} has the same syntax as an entry (see below) but
 instead of containing data, it contains strings which are intended to
 convey the meaning of each field to the user.  This is followed by any
@@ -663,6 +670,7 @@ annotation continues:
 @var{end-text}
 @end smallexample
 
+@noindent
 where @var{name} is the name of the signal, such as @code{SIGILL} or
 @code{SIGSEGV}, and @var{string} is the explanation of the signal, such
 as @code{Illegal Instruction} or @code{Segmentation fault}.

gdb/doc/gdb.texinfo

@@ -7320,9 +7320,10 @@ treats the use of the operator @code{IN}, or the use of operators
 @code{<=}, and @code{>=} on sets as an error.
 @end quotation
 
-@cindex Modula-2 built-ins
+
 @node Built-In Func/Proc
 @subsubsection Built-in functions and procedures
+@cindex Modula-2 built-ins
 
 Modula-2 also makes available several built-in procedures and functions.
 In describing these, the following metavariables are used: