Author: arnsholt Date: 2009-12-22 01:35:23 +0100 (Tue, 22 Dec 2009) New Revision: 29387

Modified: docs/Perl6/Spec/S02-bits.pod Log: [docs] Fixed two POD typos in S02. Modified: docs/Perl6/Spec/S02-bits.pod =================================================================== --- docs/Perl6/Spec/S02-bits.pod 2009-12-22 00:31:25 UTC (rev 29386) +++ docs/Perl6/Spec/S02-bits.pod 2009-12-22 00:35:23 UTC (rev 29387) @@ -685,7 +685,7 @@ as C<rat64> limit the size of both numerator and denominator, though not to the same size. The numerator should in general be twice the size of the denominator to support user expectations. For instance, -a C<rat8> actually supports C<Rational[int16,uint8], allowing +a C<rat8> actually supports C<Rational[int16,uint8]>, allowing numbers like C<100.01> to be represented, and a C<rat64>, defined as C<Rational[int128,int64]>, can hold the number of seconds since the Big Bang with attosecond precision. Though perhaps not with @@ -714,7 +714,7 @@ For applications that really need arbitrary precision denominators as well as numerators at the cost of performance, C<FatRat> may be used, -which is defined as C<Rational[Int,Int], that is, as arbitrary precision in +which is defined as C<Rational[Int,Int]>, that is, as arbitrary precision in both parts. There is no literal form for a C<FatRat>, so it must be constructed using C<FatRat.new($nu,$de)>. In general, only math operators with at least one C<FatRat> argument will return another