Committed fix for RT#35140

[dbsrgits/DBM-Deep.git] / lib / DBM / Deep / Internals.pod

diff --git a/lib/DBM/Deep/Internals.pod b/lib/DBM/Deep/Internals.pod
index cc851ed..132bc9e 100644 (file)
--- a/lib/DBM/Deep/Internals.pod
+++ b/lib/DBM/Deep/Internals.pod
@@ -8,33 +8,33 @@ B<NOTE>: This document is out-of-date. It describes an intermediate file
 format used during the development from 0.983 to 1.0000. It will be rewritten
 soon.
 
-This is a document describing the internal workings of L<DBM::Deep/>. It is
+This is a document describing the internal workings of L<DBM::Deep>. It is
 not necessary to read this document if you only intend to be a user. This
 document is intended for people who either want a deeper understanding of
-specifics of how L<DBM::Deep/> works or who wish to help program
-L<DBM::Deep/>.
+specifics of how L<DBM::Deep> works or who wish to help program
+L<DBM::Deep>.
 
 =head1 CLASS LAYOUT
 
-L<DBM::Deep/> is broken up into five classes in three inheritance hierarchies.
+L<DBM::Deep> is broken up into five classes in three inheritance hierarchies.
 
 =over 4
 
 =item *
 
-L<DBM::Deep/> is the parent of L<DBM::Deep::Array/> and L<DBM::Deep::Hash/>.
+L<DBM::Deep> is the parent of L<DBM::Deep::Array> and L<DBM::Deep::Hash>.
 These classes form the immediate interface to the outside world. They are the
 classes that provide the TIE mechanisms as well as the OO methods.
 
 =item *
 
-L<DBM::Deep::Engine/> is the layer that deals with the mechanics of reading
+L<DBM::Deep::Engine> is the layer that deals with the mechanics of reading
 and writing to the file. This is where the logic of the file layout is
 handled.
 
 =item *
 
-L<DBM::Deep::File/> is the layer that deals with the physical file. As a
+L<DBM::Deep::File> is the layer that deals with the physical file. As a
 singleton that every other object has a reference to, it also provides a place
 to handle datastructure-wide items, such as transactions.
 
@@ -135,10 +135,10 @@ than the key.
 
 =head1 PERFORMANCE
 
-L<DBM::Deep/> is written completely in Perl. It also is a multi-process DBM
+L<DBM::Deep> is written completely in Perl. It also is a multi-process DBM
 that uses the datafile as a method of synchronizing between multiple
 processes. This is unlike most RDBMSes like MySQL and Oracle. Furthermore,
-unlike all RDBMSes, L<DBM::Deep/> stores both the data and the structure of
+unlike all RDBMSes, L<DBM::Deep> stores both the data and the structure of
 that data as it would appear in a Perl program.
 
 =head2 CPU
@@ -260,9 +260,9 @@ Run time was 12 min 3 sec.
 
 =head2 MEMORY USAGE
 
-One of the great things about L<DBM::Deep/> is that it uses very little memory.
+One of the great things about L<DBM::Deep> is that it uses very little memory.
 Even with huge databases (1,000,000+ keys) you will not see much increased
-memory on your process.  L<DBM::Deep/> relies solely on the filesystem for storing
+memory on your process.  L<DBM::Deep> relies solely on the filesystem for storing
 and fetching data.  Here is output from I<top> before even opening a database
 handle: