[ID 20000724.003] Documentation changes for perllocale.pod

[p5sagit/p5-mst-13.2.git] / pod / perlnumber.pod

diff --git a/pod/perlnumber.pod b/pod/perlnumber.pod
index 9f628cc..d179d8c 100644 (file)
--- a/pod/perlnumber.pod
+++ b/pod/perlnumber.pod
@@ -36,10 +36,10 @@ The term "native" does not mean quite as much when we talk about native
 integers, as it does when native floating point numbers are involved.
 The only implication of the term "native" on integers is that the limits for
 the maximal and the minimal supported true integral quantities are close to
-powers of 2.  However, for "native" floats have a most fundamental
+powers of 2.  However, "native" floats have a most fundamental
 restriction: they may represent only those numbers which have a relatively
 "short" representation when converted to a binary fraction.  For example,
-0.9 cannot be respresented by a native float, since the binary fraction
+0.9 cannot be represented by a native float, since the binary fraction
 for 0.9 is infinite:
 
   binary0.1110011001100...
@@ -59,7 +59,7 @@ finite decimal expansion.  Being strings, and thus of arbitrary length, there
 is no practical limit for the exponent or number of decimal digits for these
 numbers.  (But realize that what we are discussing the rules for just the
 I<storage> of these numbers.  The fact that you can store such "large" numbers
-does not mean that that the I<operations> over these numbers will use all
+does not mean that the I<operations> over these numbers will use all
 of the significant digits.
 See L<"Numeric operators and numeric conversions"> for details.)