Spell checking

• Two obvious one's
• Most spell checkers do not like "isn't" and "doesn't". Use "is not" and
  "does not" instead

Author: H.Merijn Brand - Tux

.aspell.local.pws

@@ -26,6 +26,7 @@ gz
 indices
 ini
 isn
+Jens
 Jochen
 jwiedATcpan
 jZed
@@ -39,6 +40,7 @@ NVL
 param
 params
 PerlMonks
+polymorphism
 PrintError
 RaiseError
 reentrant
@@ -50,6 +52,7 @@ RSS
 Schubbert
 Sterin
 subquery
+TableA
 UDF
 UDFs
 ve

lib/SQL/Eval.pm

@@ -278,7 +278,7 @@ Hash reference containing additional capabilities.
 =item _gen_access_fastpath
 
 Return a subroutine reference for fast accessing columns for read-only
-access. When the instantiated object doesn't provide own methods for
+access. When the instantiated object does not provide own methods for
 C<column> and C<column_num> a subroutine reference is returned which
 directly access the internal data structures. For all other cases a
 subroutine directly calling C<< $self->column($_[0]) >> is returned.
@@ -512,7 +512,7 @@ indexes.
 =head1 MULTITHREADING
 
 All methods are working with instance-local data only, thus the module
-is reentrant and thread safe, if you either don't share handles between
+is reentrant and thread safe, if you either do not share handles between
 threads or grant serialized use.
 
 =head1 BUGS

lib/SQL/Statement.pm

@@ -1537,7 +1537,7 @@ sub verify_columns
         }
 
         # the following should be probably conditioned on an option,
-        # but I don't know which --BW
+        # but I do not know which --BW
         elsif ( 'USING' eq $join->{clause} )
         {
             my @keys = @{ $join->{keycols} };

lib/SQL/Statement/Function.pm

@@ -27,7 +27,7 @@ SQL::Statement::Function - abstract base class for all function executing terms
 
 =head1 SYNOPSIS
 
-  # this class doesn't have a common constructor, because all derived classes
+  # this class does not have a common constructor, because all derived classes
   # have their special requirements
 
 =head1 DESCRIPTION
@@ -287,7 +287,7 @@ The character to trim - defaults to C<' '>
 
 =item I<\@params>
 
-Expected to be an array with exact 1 element (more aren't evaluated).
+Expected to be an array with exact 1 element (more are not evaluated).
 
 =back
 
@@ -381,7 +381,7 @@ If omitted, everything to the end of the string is returned.
 
 =item I<\@params>
 
-Expected to be an array with exact 1 element (more aren't evaluated).
+Expected to be an array with exact 1 element (more are not evaluated).
 
 =back
 

lib/SQL/Statement/Roadmap.pod

@@ -22,7 +22,7 @@ may help us to design SQL::Statement 2.xx much better.
 =head3 CREATE and DROP of FUNCTION, KEYWORD, OPERATOR, TYPE
 
 SQL::Statement is missing some functions, types, operators etc. It's
-supported to add missing functionality - but the implementation wasn't
+supported to add missing functionality - but the implementation was not
 picked up during the modernizing of column evaluation. See RT#52397
 for some more information.
 

lib/SQL/Statement/Syntax.pod

@@ -283,7 +283,7 @@ Delimited identifiers (table and column names *with* quotes around them) are
 case SENSITIVE so column "foo", "fOo", "FOO" each refer to different columns.
 
 A delimited identifier is *never* equal to a regular identifier (so "foo" and
-foo are two different columns).  But don't do that :-).
+foo are two different columns).  But do not do that :-).
 
 Remember thought that, in L<DBD::CSV> if table names are used directly as file
 names, the case sensitivity depends on the OS e.g. on Windows files named foo,
@@ -373,7 +373,7 @@ are exactly the same:
  my $sth = $dbh->prepare(" SELECT * FROM RUN( 'query.sql' ) ");
 
 If the file contains a statement with placeholders, the values for the
-placehoders can be passed in the call to $sth->execute() as normal. If the
+placeholders can be passed in the call to $sth->execute() as normal. If the
 query.sql file contains "SELECT id,name FROM x WHERE id=?", then these
 two are the same:
 
@@ -402,7 +402,7 @@ Syntax obvious
 
 Surrounded by either single quotes; some characters need to
 be escaped with a backslash, in particular the backslash itself (\\),
-the NUL byte (\0), Line feeds (\n), Carriage return (\r), and the
+the NULL byte (\0), Line feeds (\n), Carriage return (\r), and the
 quotes (\').
 
 B<Note:> Quoting "Strings" using double quotes are recognized as
@@ -461,7 +461,7 @@ the parser, especially keywords like FROM and WHERE that are central to
 parsing the statement.
 
 In the reverse situation, suppose you want to parse some SQL that defines a
-column as type BIG_BLOB.  Since 'BIG_BLOB' isn't a recognized ANSI data type,
+column as type BIG_BLOB.  Since 'BIG_BLOB' is not a recognized ANSI data type,
 an error will be produced by default.  To make the parser treat it as a valid
 data type, you do this: