Fix typos (#342)

Most of them found and fixed by codespell
(https://github.com/codespell-project/codespell).

Signed-off-by: Sebastian Pipping <[email protected]>

Author: hartwork

README

@@ -480,7 +480,7 @@ LCOV features and capabilities fall into 7 major categories:
 
           See "xml2lcov --help" fir brief instructions on how to use
           the translator.
-          See the Coburtura documention for directions on how to
+          See the Coburtura documentation for directions on how to
           generate XML data.
 
      Other languages can be integrated using a similar approach.

bin/genhtml

@@ -4221,7 +4221,7 @@ sub new
     ];
     # we will call the $annotateObj->line(int) to collect annotate data
     #   for certain lines - to find out of a non-code line is in a
-    #   continguous region by the same author, in the same SHA or etc.
+    #   contiguous region by the same author, in the same SHA or etc.
     $self->[NEXT] = shift(@{$self->[STACK]});
     if (defined($self->[NEXT]) && $self->[NEXT] != 1) {
         _computeContextBefore($self, 0);
@@ -4237,7 +4237,7 @@ sub _computeContextBefore
     my $data     = $self->[LINECOV_HASH];
     my $annotate = $self->[ANNOTATE_OBJ];
     # find contiguous source region which matches the select criteria.
-    #   That might include non-code lined (e.g., commments)
+    #   That might include non-code lined (e.g., comments)
     for (my $l = $self->[NEXT] - 1; $l > $prev; --$l) {
         my $lineData     = $data->{$l} if exists($data->{$l});
         my $annotateData = $annotate->line($l);
@@ -4246,7 +4246,7 @@ sub _computeContextBefore
                                          $self->[ANNOTATE_OBJ]->path(), $l);
         ++$count;
     }
-    # region of interest is the (possibly empty) contigous region we found
+    # region of interest is the (possibly empty) contiguous region we found
     # plus the number of context lines
     $self->[LINES_BEFORE] = $num_context_lines + $count;
 }
@@ -10086,7 +10086,7 @@ sub write_file_table_entry(*$$@)
             if ($page_type eq 'owner') {
                 $entry .= 'N' . $id;
             } else {
-                die("unexepected page type $page_type")
+                die("unexpected page type $page_type")
                     unless $page_type eq 'date';
                 $entry .= 'B' . $SummaryInfo::ageHeaderToBin{$id};
             }
@@ -13147,7 +13147,7 @@ sub write_file_table(*$$$$$$)
                                       SummaryInfo::LINE_DATA)
                  ]);
             # there might not be optional test data for some tests - that type was
-            #  not emabled
+            #  not enabled
             push(@results,
                  [$mcdc_found,
                   $mcdc_hit,

bin/geninfo

@@ -2629,7 +2629,7 @@ sub intermediate_json_to_info($)
                 }
             }
             if ($conditions && @$conditions) {
-                #die("unexpected multiple conditons at $line") if scalar(@$conditions) > 1;
+                #die("unexpected multiple conditions at $line") if scalar(@$conditions) > 1;
                 #lcovutil::debig(1, "MDCD at $filename:$line\n");
                 my $mcdc = $mcdcMap->new_mcdc($fileData, $line);
 

bin/lcov

@@ -494,7 +494,7 @@ OPERATION
 
 OPTIONS
   -i, --initial                   Capture initial zero coverage data
-  --all                           Captuer from both .gcda and lone .gcno files
+  --all                           Capture from both .gcda and lone .gcno files
   -t, --test-name NAME            Specify test name to be stored with data
   -o, --output-file FILENAME      Write data to FILENAME instead of stdout
   -d, --directory DIR             Use .da files in DIR instead of kernel

bin/py2lcov

@@ -31,7 +31,7 @@
 #
 # arguably, should do this in Perl so we could use the lcovutil module utilities
 # In the meantime:  suggested use model is to translate the python XML using this
-# utility, then read it back into lcov for additonal processing.
+# utility, then read it back into lcov for additional processing.
 #
 # @todo figure out/enhance Coverage.py to characterize branch expressions
 # @todo perhaps this should be integrated into the Coverage.py module itself.
@@ -62,7 +62,7 @@ function data because the 'def myFunc(...)' line will acquire a 'hit' count
 of 1 because the python interpreter considers the 'def' to have been executed
 when the line is interpreted (i.e., when the function is defined).
 This will generate an 'inconsistent' error if the function is not executed in
-your tests becasue the (derived) function will have a zero hit count but the
+your tests because the (derived) function will have a zero hit count but the
 first line of the function has a non-zero count.
 Best practice is to either always specify '--no-functions' or never specify
 '--no-functions'.

bin/xml2lcovutil.py

@@ -24,7 +24,7 @@
 #
 # Arguably, this should be done in Perl so we could use lcovutil module utilities.
 # In the meantime:  suggested use model is to translate the XML using this
-# utility, then read it back into lcov for additonal processing.
+# utility, then read it back into lcov for additional processing.
 #
 # @todo figure out how to characterize branch expressions in XML data
 
@@ -84,7 +84,7 @@ class ProcessFile:
 
   - Coverage data merge is problematic.
 
-      o For eample: you have two testcase XML files, each of which hit
+      o For example: you have two testcase XML files, each of which hit
         4 of 8 branches on some line.
 
       o  Does that mean you hit 4 of them (both tests exercised the same

lib/lcovutil.pm

@@ -952,7 +952,7 @@ sub do_mangle_check
 sub configure_callback
 {
     # if there is just one argument, then assume it might be a
-    # concatentation - otherwise, just use straight.
+    # concatenation - otherwise, just use straight.
     my $cb = shift;
     my @args =
         1 == scalar(@_) ?
@@ -1895,7 +1895,7 @@ sub parse_expected_message_counts(@)
                                             ($ignore ? ': ignoring.' : ''));
                 next;
             }
-            # check if syntax look resonable
+            # check if syntax look reasonable
             my $expr = $2;
             if (Scalar::Util::looks_like_number($expr)) {
                 $expected_message_count[$id] = "%C == $expr";
@@ -1948,7 +1948,7 @@ sub explain_once
     #   once - e.g., when two or more child processes generate them
     #   simultaneously.
     #   They will eventually update the parent process state such that
-    #   subseqent children won't report the issues.
+    #   subsequent children won't report the issues.
     my $key = shift;
     if (!exists($explainOnce{$key})) {
         $explainOnce{$key} = 1;
@@ -7443,7 +7443,7 @@ sub _filterFile
     # Note:  this is checking the version of the 'current' file - even if
     #   we are actually reading the baseline version.
     #   - This is what we want, as the 'baseline read' is actually recovering/
-    #     recreating the baseline source fromthe current source and the diff.
+    #     recreating the baseline source from the current source and the diff.
     #   - We already checked that the diff and the coverage DB baseline/current
     #     version data is consistent - so filtering will be accurate as long as
     #     we see the right 'current' source version.
@@ -9176,7 +9176,7 @@ sub merge
     my $readSourceFile;
     my $t = ref($_[0]);
     if (!defined($_[0]) || '' eq $t) {
-        # backward compatiblity - arg is undefined or is a filename
+        # backward compatibility - arg is undefined or is a filename
         $readSourceFile = ReadCurrentSource->new();
         shift unless defined($_[0]);
     } else {

man/genhtml.1

@@ -528,14 +528,14 @@ and
 
 where
 .I $hash
-is a reference to a hask of key/value pairs which are meaningful to you.
+is a reference to a hash of key/value pairs which are meaningful to you.
 This data is stored in the
 .I profile
 database.  See the 'profile' section in man
 .B lcovrc(5)
 for more information.
 
-If your callback is not a perl module - for example, is a shellscript - then it should return a string such that the first word on each line is the key and the remainder is the associated data.  If a key is repeated, then the corresponding data strings are concatentated, separated by newline.
+If your callback is not a perl module - for example, is a shellscript - then it should return a string such that the first word on each line is the key and the remainder is the associated data.  If a key is repeated, then the corresponding data strings are concatenated, separated by newline.
 
 If you want to record only system information, then a shell callback is likely sufficient.  If you want to record any tool-specific/internal information, then you will need to implement a perl module so that your callback will be able to access the information.
 Note that the constructor of your
@@ -614,7 +614,7 @@ path or any parameter contains spaces or shell special characters.
 .IP 3. 3
 If an option is specified multiple times, then the parameters are
 .I not
-split, but are simply concatentated to form the command line - see the examples, below.
+split, but are simply concatenated to form the command line - see the examples, below.
 .br
 For simplicity and ease of understanding:  your command line should
 pass all arguments individually, or all as a comma-separated list - not a mix of the two.
@@ -2509,7 +2509,7 @@ Use this switch if you want some artifact of coverage report generation -
 .I e.g.,
 the coverage criteria check or the serialized coverage DB,
 .B etc.
-- but do not need teh coverage report HTML itself.
+- but do not need the coverage report HTML itself.
 
 
 .RE
@@ -2738,17 +2738,17 @@ whether the condition was sensitized or not. Conditions are shown in the followi
 
 .RS 3
 .IP T: 3
-True sense of subexpression was sensitized: if this subexpression's value had been false, then the condition resut would have been different.
+True sense of subexpression was sensitized: if this subexpression's value had been false, then the condition result would have been different.
 .IP t: 3
 True sense of subexpression was
 .B not
-sensitized:  the conditon result would not change if the subexpression value was different.
+sensitized:  the condition result would not change if the subexpression value was different.
 .IP F:
-False sense of subexpression was sensitized: if this subexpression's value had been true, then the condition resut would have been different.
+False sense of subexpression was sensitized: if this subexpression's value had been true, then the condition result would have been different.
 .IP f:
 False sense of subexpression was
 .B not
-sensitized:  the conditon result would not change if the subexpression value was different.
+sensitized:  the condition result would not change if the subexpression value was different.
 .RE
 
 Note that branch and MC/DC coverage are identical if the condition is
@@ -2779,7 +2779,7 @@ constituent expression changed from true to false (termed the 'true' sense, abov
 .br
 For example, the expression
 .I A || B
-is sensitve to
+is sensitive to
 .I A==true
 when
 .I B==false,
@@ -2981,7 +2981,7 @@ function execution count record (
 .I FN
 ).
 .PP
-.IP "(enhanced LCOV fomat)" 3
+.IP "(enhanced LCOV format)" 3
 function alias record (
 .I FNA
 ) without matching function declaration record (
@@ -3004,7 +3004,7 @@ internal tool issue detected.  Please report this bug along with a testcase.
 
 .IP mismatch: 3
 Incorrect or inconsistent information found in coverage data and/or source code - for example,
-the souce code contains overlapping exclusion directives.
+the source code contains overlapping exclusion directives.
 
 .PP
 
@@ -3436,7 +3436,7 @@ that implements a check for "UNC + LBC + UIC == 0".
 
 .I \*[scriptdir]/threshold.pm
 .RS
-Sample script written as Perl module to check for miminum acceptable
+Sample script written as Perl module to check for minimum acceptable
 line and/or branch and/or and/or MC/DC function coverage.
 For example, the
 .RS

man/geninfo.1

@@ -660,7 +660,7 @@ by default.
 Follow links when searching .gcda files, as well as to decide whether a
 particular (symbolically linked) source directory is "internal" to the project or not - see the
 .I \-\-no\-external
-option, above, for more inforamtion.
+option, above, for more information.
 The
 .I \-\-follow command line option is equivalent to the
 .I geninfo_follow_symlinks
@@ -928,7 +928,7 @@ internal tool issue detected.  Please report this bug along with a testcase.
 
 .IP mismatch: 3
 Incorrect information found in coverage data and/or source code - for example,
-the souce code contains overlapping exclusion directives.
+the source code contains overlapping exclusion directives.
 .PP
 
 .IP missing: 3
@@ -1542,7 +1542,7 @@ is the line number where the condition is found - and is expected to be a non-ze
 .I <groupSize>
 and
 .I <index>
-serve to uniquely define a particular elemenet in the expression tree of a particular conditional found on the associated line.
+serve to uniquely define a particular element in the expression tree of a particular conditional found on the associated line.
 .br
 Within a particular line and group,
 .I <index>
@@ -1555,7 +1555,7 @@ is either
 .I "f"
 or
 .I "t",
-indicating whether the condition is sensitive to the indicated change - that is, does the condition outcome change if the corresponging changes from 'false' to 'true' or from 'tru' to 'false, respectively.
+indicating whether the condition is sensitive to the indicated change - that is, does the condition outcome change if the corresponding changes from 'false' to 'true' or from 'tru' to 'false, respectively.
 
 
 .I <taken>
@@ -1566,7 +1566,7 @@ as the number of times that the expression was sensitized where others may treat
 as a boolean - 1:sensitized or 0: not sensitized.
 
 .I <expression>
-is an arbitary string, intended to be a meaningful string which will help the user to understand the condition context - see below.
+is an arbitrary string, intended to be a meaningful string which will help the user to understand the condition context - see below.
 .I <expression>
 appears in the 'tooltip' popup of the associated MC/DC condition in the
 .B genhtml

man/lcov.1

@@ -777,11 +777,11 @@ One or more
 .I \-\-substitution
 patterns and/or a
 .I \-\-resolve-script
-may be specified.  When multiple paterns are specified, they are applied in the order specifed, substitution patterns first followed by the resolve callback.
+may be specified.  When multiple patterns are specified, they are applied in the order specified, substitution patterns first followed by the resolve callback.
 The file search order is:
 .RS
 .IP 1. 3
-Look for file name (unmodifed).
+Look for file name (unmodified).
 .br
 If the file exits: return it.
 .PP
@@ -791,7 +791,7 @@ Apply all substitution patterns in order - the result of the first pattern is us
 If a file corresponding to the resulting name exists:  return it.
 .PP
 .IP 3. 3
-Apply the 'resolve' callback ot the final result of pattern substituions.
+Apply the 'resolve' callback ot the final result of pattern substitutions.
 .br
 If a file corresponding to the resulting name exists:  return it.
 .PP