[m-rev.] diff: update docs to reflect my recent change

[Mark Brown]

Estimated hours taken: 0.1
Branches: main

doc/user_guide.texi:
	Update the documentation to reflect the recent change I made to
	the declarative debugger's output formatting.  This should have
	been committed with that change, but was overlooked.

Index: doc/user_guide.texi
===================================================================
RCS file: /home/mercury1/repository/mercury/doc/user_guide.texi,v
retrieving revision 1.337
diff -u -r1.337 user_guide.texi
--- doc/user_guide.texi	31 Oct 2002 14:47:24 -0000	1.337
+++ doc/user_guide.texi	3 Nov 2002 07:09:14 -0000
@@ -3322,14 +3322,11 @@
 
 When seeking to determine the validity of
 the assertion corresponding to an EXIT event,
-the declarative debugger prints the exit atom,
-on a single line if possible,
-and prints the question @samp{Valid?} for the user to answer.
-If the atom does not fit on one line,
-the predicate/function name is printed on the first line and
-the arguments are printed one per line
-using the same mechanism that the debugger uses to print values.
-This means they may be abbreviated if they are too large.
+the declarative debugger prints the exit atom
+followed by the question @samp{Valid?} for the user to answer.
+The atom is printed using
+the same mechanism that the debugger uses to print values,
+which means some arguments may be abbreviated if they are too large.
 
 When seeking to determine the validity of
 the assertion corresponding to a FAIL event,
--------------------------------------------------------------------------
mercury-reviews mailing list
post:  mercury-reviews at cs.mu.oz.au
administrative address: owner-mercury-reviews at cs.mu.oz.au
unsubscribe: Address: mercury-reviews-request at cs.mu.oz.au Message: unsubscribe
subscribe:   Address: mercury-reviews-request at cs.mu.oz.au Message: subscribe
--------------------------------------------------------------------------