diff --git a/Changes b/Changes index 4aae7996c..23e1955a8 100644 --- a/Changes +++ b/Changes @@ -1039,7 +1039,7 @@ ***************************************************************************** * * -* BELOW THIS POINT ARE THE SEPERATE CHANGELOGS FOR Test-Simple, Test2, AND * +* BELOW THIS POINT ARE THE SEPARATE CHANGELOGS FOR Test-Simple, Test2, AND * * Test-Stream. * * * ***************************************************************************** diff --git a/lib/Test2/API.pm b/lib/Test2/API.pm index b4504fa07..422b046a7 100644 --- a/lib/Test2/API.pm +++ b/lib/Test2/API.pm @@ -946,7 +946,7 @@ documentation for details on how to best use it. =head1 ENVIRONMENT VARIABLES -See L for a list of meaningul environment variables. +See L for a list of meaningful environment variables. =head1 MAIN API EXPORTS @@ -1585,7 +1585,7 @@ which case new strings will be passed in. These are purely informative, you can =item test2_add_pending_diag($diag1, $diag2) Add a diagnostics message that will be issued the next time a context in which -a failure occured is released. +a failure occurred is released. This can also be thought of like this: "If the next bit causes a failed assertion, add this diagnostics message". diff --git a/lib/Test2/API/InterceptResult.pm b/lib/Test2/API/InterceptResult.pm index 8e5a1ee2d..c174afd39 100644 --- a/lib/Test2/API/InterceptResult.pm +++ b/lib/Test2/API/InterceptResult.pm @@ -483,7 +483,7 @@ These are essentially: $events->grep(causes_failure => @{$PARAMS{args}}) B C and C are both aliases for -eachother in events, so these methods are effectively aliases here as well. +each other in events, so these methods are effectively aliases here as well. It returns a new instance containing only the events that cause failure. diff --git a/lib/Test2/Env.pm b/lib/Test2/Env.pm index 8b434ec92..baf2aa1a8 100644 --- a/lib/Test2/Env.pm +++ b/lib/Test2/Env.pm @@ -80,8 +80,8 @@ Test2 sets this variable when tests are running. =head1 TEST2_ENABLE_PLUGINS -This can be used to force plugins to be loaded whent he Test2 API is loaded. It -takes a list of one or more plugin names seperated by comma. If the module name +This can be used to force plugins to be loaded when he Test2 API is loaded. It +takes a list of one or more plugin names separated by comma. If the module name does not have a '+' in front of it then the C namespace is assumed and added. If a '+' is present at the start of a module name it will be stripped and no further modification will be made. @@ -98,7 +98,7 @@ Set by Test2 when tests are running. =head1 TS_MAX_DELTA Used to determine how many max lines of output will be provided when is() finds -a deep data strucgture mismatch. +a deep data structure mismatch. =head1 SOURCE diff --git a/lib/Test2/Hub.pm b/lib/Test2/Hub.pm index a8d19cf1c..0553b5aa7 100644 --- a/lib/Test2/Hub.pm +++ b/lib/Test2/Hub.pm @@ -40,7 +40,7 @@ use Test2::Util::HashBase qw{ { no warnings 'once'; - # Support an originally mispelled method name, at least 1 downstream + # Support an originally misspelled method name, at least 1 downstream # release already uses it. It will be fixed, but we do not want to break # things before it is fixed. *surpress_release_error = \&suppress_release_error; diff --git a/lib/Test2/Manual/Testing/Introduction.pm b/lib/Test2/Manual/Testing/Introduction.pm index fd859fbb9..129d7292e 100644 --- a/lib/Test2/Manual/Testing/Introduction.pm +++ b/lib/Test2/Manual/Testing/Introduction.pm @@ -153,7 +153,7 @@ Which produces: ( LAUNCH ) job 1 example.t ( NOTE ) job 1 Seeded srand with seed '20171014' from local date. [ PASS ] job 1 + 1 is true, so this will pass - [ PLAN ] job 1 Expected asserions: 1 + [ PLAN ] job 1 Expected assertions: 1 ( PASSED ) job 1 example.t ================================================================================ diff --git a/lib/Test2/Manual/Tooling/Nesting.pm b/lib/Test2/Manual/Tooling/Nesting.pm index 7138598f4..0206503c9 100644 --- a/lib/Test2/Manual/Tooling/Nesting.pm +++ b/lib/Test2/Manual/Tooling/Nesting.pm @@ -51,7 +51,7 @@ The naive way to do this is to write a C function like this: This will appear to work fine, and you might not notice any problems, I -=head2 WHATS WRONG WITH IT? +=head2 WHAT'S WRONG WITH IT? The problems with the naive approach become obvious if things start to fail. The diagnostics that tell you what file and line the failure occurred on will be diff --git a/lib/Test2/Mock.pm b/lib/Test2/Mock.pm index cfeeb07e9..a78a1317a 100644 --- a/lib/Test2/Mock.pm +++ b/lib/Test2/Mock.pm @@ -425,7 +425,7 @@ sub _inject { && (reftype($orig) ne 'SCALAR' || defined($$orig)); $syms->{"$sig$sym"} ||= []; - push @{$syms->{"$sig$sym"}} => $orig; # Might be undef, thats expected + push @{$syms->{"$sig$sym"}} => $orig; # Might be undef, that's expected if ($self->{+_TRACK} && $sig eq '&') { my $sub_tracker = $self->{+SUB_TRACKING}; diff --git a/lib/Test2/V0.pm b/lib/Test2/V0.pm index 54b1e7eec..04ca28fc5 100644 --- a/lib/Test2/V0.pm +++ b/lib/Test2/V0.pm @@ -289,7 +289,7 @@ This plugin has no configuration. =head1 ENVIRONMENT VARIABLES -See L for a list of meaningul environment variables. +See L for a list of meaningful environment variables. =head1 API FUNCTIONS diff --git a/t/Test2/modules/Util.t b/t/Test2/modules/Util.t index 73108aa65..b1131c9f3 100644 --- a/t/Test2/modules/Util.t +++ b/t/Test2/modules/Util.t @@ -36,7 +36,7 @@ use Test2::Util qw/ { for my $try (\&try, Test2::Util->can('_manual_try'), Test2::Util->can('_local_try')) { my ($ok, $err) = $try->(sub { die "xxx" }); - ok(!$ok, "cought exception"); + ok(!$ok, "caught exception"); like($err, qr/xxx/, "expected exception"); ($ok, $err) = $try->(sub { 0 }); diff --git a/t/modules/AsyncSubtest.t b/t/modules/AsyncSubtest.t index 677359820..6a928dc44 100644 --- a/t/modules/AsyncSubtest.t +++ b/t/modules/AsyncSubtest.t @@ -39,7 +39,7 @@ intercept { }; isa_ok($one, $CLASS); -is($one->hub->ast, exact_ref($one), "Can retrieve AST fromthe hub"); +is($one->hub->ast, exact_ref($one), "Can retrieve AST from the hub"); like( $one,