Corrections to spelling and grammatical errors.

Extracted from patch submitted by Lajos Veres in RT #123693.

diff --git a/lib/DB.t b/lib/DB.t
index b4b6ecb..e4ee074 100644 (file)
--- a/lib/DB.t
+++ b/lib/DB.t
@@ -337,7 +337,7 @@ SKIP: {
                 '... should increment past lines with no events' );
                 
         ok( ! defined DB::_find_subline('sirnotappearinginthisfilm'),
-                '... should not find nonexistant sub' );
+                '... should not find nonexistent sub' );
 }
 
 # test DB::clr_breaks()

diff --git a/lib/unicore/mktables b/lib/unicore/mktables
index b7bf629..119df82 100644 (file)
--- a/lib/unicore/mktables
+++ b/lib/unicore/mktables
@@ -15424,7 +15424,7 @@ sub make_re_pod_entries($) {
                     }
                 }
 
-                # Ouput both short and single in the same parenthesized
+                # Output both short and single in the same parenthesized
                 # expression, but with only one of 'Single', 'Short' if there
                 # are both items.
                 if ($short_name || $single_form || $table->conflicting) {

diff --git a/perl.h b/perl.h
index c2c4a5c..286e8d0 100644 (file)
--- a/perl.h
+++ b/perl.h
@@ -3541,7 +3541,7 @@ typedef pthread_key_t     perl_key;
    expression, which allows the compiler to generate better machine code.
    In a debug build, ASSUME(x) is a synonym for assert(x). ASSUME(0) means
    the control path is unreachable. In a for loop, ASSUME can be used to hint
-   that a loop will run atleast X times. ASSUME is based off MSVC's __assume
+   that a loop will run at least X times. ASSUME is based off MSVC's __assume
    intrinsic function, see its documents for more details.
 */
 

diff --git a/perlio.c b/perlio.c
index 95b7482..e5ebfd9 100644 (file)
--- a/perlio.c
+++ b/perlio.c
@@ -849,7 +849,7 @@ XS(XS_io_MODIFY_SCALAR_ATTRIBUTES)
     XSRETURN(count);
 }
 
-#endif                          /* USE_ATTIBUTES_FOR_PERLIO */
+#endif                          /* USE_ATTRIBUTES_FOR_PERLIO */
 
 SV *
 PerlIO_tab_sv(pTHX_ PerlIO_funcs *tab)

diff --git a/pp_sort.c b/pp_sort.c
index 7d0e40f..54132b4 100644 (file)
--- a/pp_sort.c
+++ b/pp_sort.c
@@ -894,7 +894,7 @@ S_qsortsvu(pTHX_ SV ** array, size_t num_elts, SVCOMPARE_t compare)
             elements in the middle of the partition, those are the ones we
             pick here (conveniently pointed at by u_right, pc_left, and
             u_left). The values of the left, center, and right elements
-            are refered to as l c and r in the following comments.
+            are referred to as l c and r in the following comments.
          */
 
 #ifdef QSORT_ORDER_GUESS

diff --git a/regcomp.c b/regcomp.c
index 3851d34..b0686c4 100644 (file)
--- a/regcomp.c
+++ b/regcomp.c
@@ -1916,7 +1916,7 @@ then read 'r' and go to state 8 followed by 's' which takes us to state 9 which
 is also accepting. Thus we know that we can match both 'he' and 'hers' with a
 single traverse. We store a mapping from accepting to state to which word was
 matched, and then when we have multiple possibilities we try to complete the
-rest of the regex in the order in which they occured in the alternation.
+rest of the regex in the order in which they occurred in the alternation.
 
 The only prior NFA like behaviour that would be changed by the TRIE support is
 the silent ignoring of duplicate alternations which are of the form:

diff --git a/regcomp.h b/regcomp.h
index de31d65..c17bf62 100644 (file)
--- a/regcomp.h
+++ b/regcomp.h
@@ -232,7 +232,7 @@ struct regnode_charclass_class {
  * extra SV*, used only during its construction and which is not used by
  * regexec.c.  Note that the 'next_off' field is unused, as the SSC stands
  * alone, so there is never a next node.  Also, there is no alignment issue,
- * becase these are declared or allocated as a complete unit so the compiler
+ * because these are declared or allocated as a complete unit so the compiler
  * takes care of alignment.  This is unlike the other regnodes which are
  * allocated in terms of multiples of a single-argument regnode.  SSC nodes can
  * have a pointer field because there is no alignment issue, and because it is