Bug #56520 for DBM-Deep: [PATCH] Fix spelling errors

Hi, the attached patch was introduced in Debian to fix several spelling errors in the documentation. Please consider applying it in the next release. Regards, Ansgar

Author: gregor herrmann <gregoa@debian.org> Description: spelling mistakes Forwarded: no --- libdbm-deep-perl.orig/lib/DBM/Deep.pod +++ libdbm-deep-perl/lib/DBM/Deep.pod @@ -192,7 +192,7 @@ type => DBM::Deep->TYPE_ARRAY ); -B<Note:> Specifing the C<type> parameter only takes effect when beginning +B<Note:> Specifying the C<type> parameter only takes effect when beginning a new DB file. If you create a DBM::Deep object with an existing file, the C<type> will be loaded from the file header, and an error will be thrown if the wrong type is passed in. @@ -737,7 +737,7 @@ =head2 set_filter() -This method takes two paramters - the filter type and the filter subreference. +This method takes two parameters - the filter type and the filter subreference. The four types are: =over @@ -1197,7 +1197,7 @@ =head1 SPONSORS Stonehenge Consulting (L<http://www.stonehenge.com/>) sponsored the -developement of transactions and freespace management, leading to the 1.0000 +development of transactions and freespace management, leading to the 1.0000 release. A great debt of gratitude goes out to them for their continuing leadership in and support of the Perl community. --- libdbm-deep-perl.orig/lib/DBM/Deep/Engine.pm +++ libdbm-deep-perl/lib/DBM/Deep/Engine.pm @@ -107,7 +107,7 @@ Other DBMSes use transaction logs (a separate file, generally) to achieve Durability. As DBM::Deep is a single-file, we would have to do something -similar to what SQLite and BDB do in terms of committing using synchonized +similar to what SQLite and BDB do in terms of committing using synchronized writes. To do this, we would have to use a much higher RAM footprint and some serious programming that make my head hurts just to think about it.