7 files changed, 9 insertions, 9 deletions
diff --git a/ext/B/B/Asmdata.pm b/ext/B/B/Asmdata.pm
index 17f18dc935..bd130fe540 100644
--- a/ext/B/B/Asmdata.pm
+++ b/ext/B/B/Asmdata.pm
@@ -234,7 +234,7 @@ A simple mapping of the op type number to its type (like 'COP' or 'BINOP').
   my $sv_name = $specialsv_name[$sv_index];
 
 Certain SV types are considered 'special'.  They're represented by
-B::SPECIAL and are refered to by a number from the specialsv_list.
+B::SPECIAL and are referred to by a number from the specialsv_list.
 This array maps that number back to the name of the SV (like 'Nullsv'
 or '&PL_sv_undef').
 
diff --git a/ext/B/B/Bblock.pm b/ext/B/B/Bblock.pm
index 908cc76055..ade81818d4 100644
--- a/ext/B/B/Bblock.pm
+++ b/ext/B/B/Bblock.pm
@@ -186,7 +186,7 @@ B::Bblock - Walk basic blocks
 
 This module is used by the B::CC back end.  It walks "basic blocks".
 A basic block is a series of operations which is known to execute from
-start to finish, with no possiblity of branching or halting.
+start to finish, with no possibility of branching or halting.
 
 It can be used either stand alone or from inside another program.
 
diff --git a/ext/B/B/CC.pm b/ext/B/B/CC.pm
index 14ee6cf322..43064fbcbf 100644
--- a/ext/B/B/CC.pm
+++ b/ext/B/B/CC.pm
@@ -1988,7 +1988,7 @@ with standard Perl but gives a compile-time error with compiled Perl.
 
 =head2 Arithmetic
 
-Compiled Perl programs use native C arithemtic much more frequently
+Compiled Perl programs use native C arithmetic much more frequently
 than standard perl. Operations on large numbers or on boundary
 cases may produce different behaviour.
 
diff --git a/ext/B/B/Concise.pm b/ext/B/B/Concise.pm
index 0798716b04..eacab350d9 100644
--- a/ext/B/B/Concise.pm
+++ b/ext/B/B/Concise.pm
@@ -938,7 +938,7 @@ tree in one of several space-efficient text formats suitable for debugging
 the inner workings of perl or other compiler backends. It can print OPs in
 the order they appear in the OP tree, in the order they will execute, or
 in a text approximation to their tree structure, and the format of the
-information displyed is customizable. Its function is similar to that of
+information displayed is customizable. Its function is similar to that of
 perl's B<-Dx> debugging flag or the B<B::Terse> module, but it is more
 sophisticated and flexible.
 
diff --git a/ext/B/B/Deparse.pm b/ext/B/B/Deparse.pm
index 081fe16c0c..5473b407da 100644
--- a/ext/B/B/Deparse.pm
+++ b/ext/B/B/Deparse.pm
@@ -2327,7 +2327,7 @@ sub indirop {
 	# give bareword warnings in that case. Therefore if context
 	# requires, we'll put parens around the outside "(sort f 1, 2,
 	# 3)". Unfortunately, we'll currently think the parens are
-	# neccessary more often that they really are, because we don't
+	# necessary more often that they really are, because we don't
 	# distinguish which side of an assignment we're on.
 	if ($cx >= 5) {
 	    return "($name2 $args)";
diff --git a/ext/B/B/Terse.pm b/ext/B/B/Terse.pm
index cb2f63b463..d87b881f91 100644
--- a/ext/B/B/Terse.pm
+++ b/ext/B/B/Terse.pm
@@ -83,7 +83,7 @@ This version of B::Terse is really just a wrapper that calls B::Concise
 with the B<-terse> option. It is provided for compatibility with old scripts
 (and habits) but using B::Concise directly is now recommended instead.
 
-For compatiblilty with the old B::Terse, this module also adds a
+For compatibility with the old B::Terse, this module also adds a
 method named C<terse> to B::OP and B::SV objects. The B::SV method is
 largely compatible with the old one, though authors of new software
 might be advised to choose a more user-friendly output format. The
diff --git a/ext/B/t/OptreeCheck.pm b/ext/B/t/OptreeCheck.pm
index c6a58e5ea1..fa1a8252a0 100644
--- a/ext/B/t/OptreeCheck.pm
+++ b/ext/B/t/OptreeCheck.pm
@@ -200,7 +200,7 @@ being tested, and saved into the synthesized property B<wanted>.
 =head2 bcopts => $bcopts || [ @bcopts ]
 
 When getRendering() runs, it passes bcopts into B::Concise::compile().
-The bcopts arg can be a singls string, or an array of strings.
+The bcopts arg can be a single string, or an array of strings.
 
 =head2 errs => $err_str_regex || [ @err_str_regexs ] 
 
@@ -627,7 +627,7 @@ the test-cases; we want the match to be as rigorous as possible, and
 thats easier to achieve when matching against 1 input than 2.
 
 Opcode arguments (text within braces) are disregarded for matching
-purposes.  This loses some info in 'add[t5]', but greatly simplifys
+purposes.  This loses some info in 'add[t5]', but greatly simplifies
 matching 'nextstate(main 22 (eval 10):1)'.  Besides, we are testing
 for regressions, not for complete accuracy.
 
@@ -804,7 +804,7 @@ build's threaded-ness.  This has several benefits:
  1. native reference data allows closer/easier matching by regex.
  2. samples can be eyeballed to grok T-nT differences.
  3. data can help to validate mkCheckRex() operation.
- 4. can develop regexes which accomodate T-nT differences.
+ 4. can develop regexes which accommodate T-nT differences.
  5. can test with both native and cross-converted regexes.
 
 Cross-testing (expect_nt on threaded, expect on non-threaded) exposes