summaryrefslogtreecommitdiff
path: root/ext/DB_File
diff options
context:
space:
mode:
authorPhilip Newton <pne@cpan.org>2001-07-31 08:19:35 +0200
committerJarkko Hietaniemi <jhi@iki.fi>2001-07-31 03:13:35 +0000
commit52ffee896d13714c1dccb2fcbd8662017ceb06bb (patch)
treeaa912a93536af17177d5ffbb3cee8b3c23253702 /ext/DB_File
parentb6e13d972c8df45251560436cb8294ed298c5bb0 (diff)
downloadperl-52ffee896d13714c1dccb2fcbd8662017ceb06bb.tar.gz
Typo in DB_File.pm
Message-Id: <200107310413.f6V4DmL11900@chaos.wustl.edu> p4raw-id: //depot/perl@11512
Diffstat (limited to 'ext/DB_File')
-rw-r--r--ext/DB_File/DB_File.pm2
1 files changed, 1 insertions, 1 deletions
diff --git a/ext/DB_File/DB_File.pm b/ext/DB_File/DB_File.pm
index 289ac0a65c..1df9876206 100644
--- a/ext/DB_File/DB_File.pm
+++ b/ext/DB_File/DB_File.pm
@@ -948,7 +948,7 @@ database.
Duplicate keys are entirely defined by the comparison function.
In the case-insensitive example above, the keys: 'KEY' and 'key'
would be considered duplicates, and assigning to the second one
-would overwirte the first. If duplicates are allowed for (with the
+would overwrite the first. If duplicates are allowed for (with the
R_DUPS flag discussed below), only a single copy of duplicate keys
is stored in the database --- so (again with example above) assigning
three values to the keys: 'KEY', 'Key', and 'key' would leave just