GOOBE the docs some more.

1 files changed, 3 insertions, 3 deletions

diff --git a/doc/expr.n b/doc/expr.n
index 22ced9a..a64431c 100644
--- a/doc/expr.n
+++ b/doc/expr.n
@@ -6,7 +6,7 @@
 '\" See the file "license.terms" for information on usage and redistribution
 '\" of this file, and for a DISCLAIMER OF ALL WARRANTIES.
 '\" 
-'\" RCS: @(#) $Id: expr.n,v 1.28 2007/10/29 01:42:18 dkf Exp $
+'\" RCS: @(#) $Id: expr.n,v 1.29 2007/10/29 11:28:50 dkf Exp $
 '\" 
 .so man.macros
 .TH expr n 8.5 Tcl "Tcl Built-In Commands"
@@ -57,7 +57,7 @@ above, then it is treated as a floating-point number if that is
 possible.  Floating-point numbers may be specified in any of several
 common formats making use of the decimal digits, the decimal point \fB.\fR,
 the characters \fBe\fR or \fBE\fR indicating scientific notation, and
-the sign characters \fB+\fR or \fB-\fR.  For example, all of the
+the sign characters \fB+\fR or \fB\-\fR.  For example, all of the
 following are valid floating-point numbers:  2.1, 3., 6e4, 7.91e+16.
 Also recognized as floating point values are the strings \fBInf\fR
 and \fBNaN\fR making use of any case for each character.
@@ -256,7 +256,7 @@ All internal computations involving floating-point are
 done with the C type \fIdouble\fR.
 When converting a string to floating-point, exponent overflow is
 detected and results in the \fIdouble\fR value of \fBInf\fR or
-\fB-Inf\fR as appropriate.  Floating-point overflow and underflow
+\fB\-Inf\fR as appropriate.  Floating-point overflow and underflow
 are detected to the degree supported by the hardware, which is generally
 pretty reliable.
 .PP