summaryrefslogtreecommitdiff
path: root/pod/perlfaq3.pod
diff options
context:
space:
mode:
authorJarkko Hietaniemi <jhi@iki.fi>2002-04-29 12:59:01 +0000
committerJarkko Hietaniemi <jhi@iki.fi>2002-04-29 12:59:01 +0000
commited8cf1fe74d9e904232221e5b8001e6eb2d4a8a9 (patch)
treebb70e3f37181d487f954a85ab239d330f5ee24e6 /pod/perlfaq3.pod
parent068ac78d80d6b49d0ecc09d01392eda125ed68e7 (diff)
downloadperl-ed8cf1fe74d9e904232221e5b8001e6eb2d4a8a9.tar.gz
FAQ sync.
p4raw-id: //depot/perl@16265
Diffstat (limited to 'pod/perlfaq3.pod')
-rw-r--r--pod/perlfaq3.pod4
1 files changed, 2 insertions, 2 deletions
diff --git a/pod/perlfaq3.pod b/pod/perlfaq3.pod
index fc32963e8e..abab557a54 100644
--- a/pod/perlfaq3.pod
+++ b/pod/perlfaq3.pod
@@ -1,6 +1,6 @@
=head1 NAME
-perlfaq3 - Programming Tools ($Revision: 1.20 $, $Date: 2002/04/23 23:35:39 $)
+perlfaq3 - Programming Tools ($Revision: 1.21 $, $Date: 2002/04/28 15:51:10 $)
=head1 DESCRIPTION
@@ -593,7 +593,7 @@ copy, you'll have to sacrifice the memory needed to make one.
For "big" data stores (i.e. ones that exceed available memory) consider
using one of the DB modules to store it on disk instead of in RAM. This
-will incur a penalty in access time, but that's probably better that
+will incur a penalty in access time, but that's probably better than
causing your hard disk to thrash due to massive swapping.
=back