Merge pull request #6 from dsteinbrunner/patch-1

typo fixes

lib/PPI.pm

@@ -194,7 +194,7 @@ What are the things that people might want a "Perl parser" for.
 Analyzing the contents of a Perl document to automatically generate
 documentation, in parallel to, or as a replacement for, POD documentation.
 
-Allow an indexer to to locate and process all the comments and
+Allow an indexer to locate and process all the comments and
 documentation from code for "full text search" applications.
 
 =item Structural and Quality Analysis
@@ -557,7 +557,7 @@ via the included L<PPI::Dumper>).
       PPI::Token::Structure            ';'
     PPI::Token::Whitespace             '\n'
 
-Please note that in this this example, strings are only listed for the
+Please note that in this example, strings are only listed for the
 B<actual> L<PPI::Token> that contains that string. Structures are listed
 with the type of brace characters it represents noted.
 
@@ -749,7 +749,7 @@ you are B<strongly> encouraged to do so, as the author currently maintains
 over 100 modules and it can take some time to deal with non-"Critical" bug
 reports or patches.
 
-This will also guarentee that your issue will be addressed in the next
+This will also guarantee that your issue will be addressed in the next
 release of the module.
 
 For large changes though, please consider creating a branch so that they

lib/PPI/Document.pm

@@ -457,7 +457,7 @@ sub serialize {
 
 		# This token is a HereDoc.
 		# First, add the token content as normal, which in this
-		# case will definately not contain a newline.
+		# case will definitely not contain a newline.
 		$output .= $Token->content;
 
 		# Now add all of the here-doc content to the heredoc buffer.
@@ -592,7 +592,7 @@ sub index_locations {
 	my @tokens = $self->tokens;
 
 	# Whenever we hit a heredoc we will need to increment by
-	# the number of lines in it's content section when when we
+	# the number of lines in it's content section when we
 	# encounter the next token with a newline in it.
 	my $heredoc = 0;
 

lib/PPI/Dumper.pm

@@ -92,7 +92,7 @@ made much clearer. True/false value, on by default.
 
 Should the dumper show comment tokens. In situations where you have
 a lot of comments, the code can often be made clearer by ignoring
-comment tokens. True/value value, on by default.
+comment tokens. True/false value, on by default.
 
 =item locations
 

lib/PPI/Lexer.pm

@@ -690,7 +690,7 @@ sub _lex_end {
 	$self->_rollback;
 }
 
-# For many statements, it can be dificult to determine the end-point.
+# For many statements, it can be difficult to determine the end-point.
 # This method takes a statement and the next significant token, and attempts
 # to determine if the there is a statement boundary between the two, or if
 # the statement can continue with the token.

lib/PPI/Node.pm

@@ -595,7 +595,7 @@ sub prune {
 }
 
 # This method is likely to be very heavily used, to take
-# it slowly and carefuly.
+# it slowly and carefully.
 ### NOTE: Renaming this function or changing either to self will probably
 ###       break File::Find::Rule::PPI
 sub _wanted {

lib/PPI/Statement/Include.pm

@@ -326,7 +326,7 @@ sub version_literal {
 
 =head2 arguments
 
-The C<arguments> method gives you the rest of the statement after the the
+The C<arguments> method gives you the rest of the statement after the
 module/pragma and module version, i.e. the stuff that will be used to
 construct what gets passed to the module's C<import()> subroutine.  This does
 include the comma, etc. operators, but doesn't include non-significant direct

lib/PPI/Statement/Variable.pm

@@ -168,7 +168,7 @@ sub symbols {
 
 		# Local is much more icky (potentially).
 		# Not that we are actually going to deal with it now,
-		# but having this seperate is likely going to be needed
+		# but having this separate is likely going to be needed
 		# for future bug reports about local() things.
 
 		# This is a slightly better way to check.

lib/PPI/Structure.pm

@@ -23,7 +23,7 @@ type should actually exist in the tree.
 
 =head2 Elements vs Children
 
-A B<PPI::Structure> has an unusual existance. Unlike a L<PPI::Document>
+A B<PPI::Structure> has an unusual existence. Unlike a L<PPI::Document>
 or L<PPI::Statement>, which both simply contain other elements, a
 structure B<both> contains and consists of content.
 

lib/PPI/Token/Magic.pm

@@ -124,7 +124,7 @@ sub __TOKENIZER__on_char {
 
 		if ( $c =~ /^(\$(?:\_[\w:]|::))/ or $c =~ /^\$\'[\w]/ ) {
 			# If and only if we have $'\d, it is not a
-			# symbol. (this was apparently a concious choice)
+			# symbol. (this was apparently a conscious choice)
 			# Note that $::0 on the other hand is legal
 			if ( $c =~ /^\$\'\d$/ ) {
 				# In this case, we have a magic plus a digit.

lib/PPI/Token/Whitespace.pm

@@ -191,7 +191,7 @@ sub __TOKENIZER__on_line_start {
 		}
 		push @{ $t->{perl6} }, join '', @perl6;
 
-		# We only sucked in the block, we don't actially do
+		# We only sucked in the block, we don't actually do
 		# anything to the "use v6..." line. So return as if
 		# we didn't find anything at all.
 		return 1;

lib/PPI/Token/_QuoteEngine/Full.pm

@@ -32,7 +32,7 @@ BEGIN {
 		's'   => { operator => 's',   braced => undef, separator => undef, _sections => 2, modifiers => 1 },
 		'tr'  => { operator => 'tr',  braced => undef, separator => undef, _sections => 2, modifiers => 1 },
 
-		# Y is the little used varient of tr
+		# Y is the little used variant of tr
 		'y'   => { operator => 'y',   braced => undef, separator => undef, _sections => 2, modifiers => 1 },
 
 		'/'   => { operator => undef, braced => 0,     separator => '/',   _sections => 1, modifiers => 1 },
@@ -148,7 +148,7 @@ sub new {
 	### implement a new function of their own.
 	my $self = PPI::Token::new( $class, $init ) or return undef;
 
-	# Do we have a prototype for the intializer? If so, add the extra fields
+	# Do we have a prototype for the initializer? If so, add the extra fields
 	my $options = $quotes{$init} or return $self->_error(
 		"Unknown quote type '$init'"
 	);
@@ -224,7 +224,7 @@ sub _fill {
 	}
 }
 
-# Handle the content parsing path for normally seperated
+# Handle the content parsing path for normally separated
 sub _fill_normal {
 	my $self = shift;
 	my $t    = shift;
@@ -301,7 +301,7 @@ sub _fill_normal {
 	1;
 }
 
-# Handle content parsing for matching crace seperated
+# Handle content parsing for matching brace separated
 sub _fill_braced {
 	my $self = shift;
 	my $t    = shift;

lib/PPI/Tokenizer.pm

@@ -47,7 +47,7 @@ This is where the truism "Only perl can parse Perl" comes from.
 
 PPI uses a completely different approach by abandoning the (impossible)
 ability to parse Perl the same way that the interpreter does, and instead
-parsing the source as a document, using a document structure independantly
+parsing the source as a document, using a document structure independently
 derived from the Perl documentation and approximating the perl interpreter
 interpretation as closely as possible.
 
@@ -533,14 +533,14 @@ sub _process_next_line {
 # Per-character processing methods
 
 # Process on a per-character basis.
-# Note that due the the high number of times this gets
+# Note that due the high number of times this gets
 # called, it has been fairly heavily in-lined, so the code
 # might look a bit ugly and duplicated.
 sub _process_next_char {
 	my $self = shift;
 
 	### FIXME - This checks for a screwed up condition that triggers
-	###         several warnings, amoungst other things.
+	###         several warnings, amongst other things.
 	if ( ! defined $self->{line_cursor} or ! defined $self->{line_length} ) {
 		# $DB::single = 1;
 		return undef;