No pod in internal Net::FTP classes.

[perl5.git] / pod / perlnumber.pod

diff --git a/pod/perlnumber.pod b/pod/perlnumber.pod
index c05b066..44d921c 100644 (file)
--- a/pod/perlnumber.pod
+++ b/pod/perlnumber.pod
@@ -22,11 +22,11 @@ Perl's operator overloading facility is completely ignored here.  Operator
 overloading allows user-defined behaviors for numbers, such as operations
 over arbitrarily large integers, floating points numbers with arbitrary
 precision, operations over "exotic" numbers such as modular arithmetic or
-p-adic arithmetic, and so on.  See L<perlovl> for details.
+p-adic arithmetic, and so on.  See L<overload> for details.
 
 =head1 Storing numbers
 
-Perl can internally represents numbers in 3 different ways: as native
+Perl can internally represent numbers in 3 different ways: as native
 integers, as native floating point numbers, and as decimal strings.
 Decimal strings may have an exponential notation part, as in C<"12.34e-56">.
 I<Native> here means "a format supported by the C compiler which was used
@@ -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...
@@ -54,14 +54,14 @@ The upshot of all this is that Perl cannot store a number like
 12345678901234567 as a floating point number on such architectures without
 loss of information.
 
-Similarly, decimal strings may represent only those numbers which have a
+Similarly, decimal strings can represent only those numbers which have a
 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 operations and numeric conversions"> for details.)
+See L<"Numeric operators and numeric conversions"> for details.)
 
 In fact numbers stored in the native integer format may be stored either
 in the signed native form, or in the unsigned native form.  Thus the limits
@@ -91,7 +91,7 @@ Six such conversions are possible:
 
 These conversions are governed by the following general rules:
 
-=over
+=over 4
 
 =item *
 
@@ -141,7 +141,7 @@ argument as in modular arithmetic, e.g., C<mod 2**32> on a 32-bit
 architecture.  C<sprintf "%u", -1> therefore provides the same result as
 C<sprintf "%u", ~0>.
 
-=over
+=over 4
 
 =item Arithmetic operators except, C<no integer>
 
@@ -182,4 +182,4 @@ Editorial adjustments by Gurusamy Sarathy <gsar@ActiveState.com>
 
 =head1 SEE ALSO
 
-L<perlovl>
+L<overload>