Correct some typos in geninfo.1 (#320)

* Correct some typos in geninfo.1
* Update man/geninfo.1

Signed-off-by: Ned Batchelder <[email protected]>

Author: nedbat

man/geninfo.1

@@ -1332,7 +1332,7 @@ See the
 .BI "\-\-version\-script " callback_script
 documentation and the sample usage in the lcov regression test examples.
 
-Function converage data follows.
+Function coverage data follows.
 Note that the format of the function coverage data has changed from LCOV 2.2 onward.
 The tool continues to be able to read the old format but now writes only the
 new format.
@@ -1389,14 +1389,14 @@ FNH:<number of function hit>
 
 Note that, as of LCOV 2.2, these numbers count function groups - not the individual aliases.
 
-Branch coverage information is stored which one line per branch:
+Branch coverage information is stored with one line per branch:
 
 .RS
 BRDA:<line_number>,[<exception>]<block>,<branch>,<taken>
 .RE
 
 .I <line_number>
-is the line number where the branch is found - and is expected to to be a non-zero integer.
+is the line number where the branch is found - and is expected to be a non-zero integer.
 .br
 .I <block>
 and
@@ -1412,9 +1412,9 @@ is a string which serves to uniquely identify a particular edge.  For some langu
 .I <branch>
 is an ordered integer index related to expression tree traversal order of the associated conditional.  For others, it may be a meaningful string - see below.
 .I <branch>
-appears in the 'tooltip' popup of the asognciated branch in the
+appears in the 'tooltip' popup of the associated branch in the
 .B genhtml
-output - so human-readable values are helpful to users who are trying to understand coveage results.
+output - so human-readable values are helpful to users who are trying to understand coverage results.
 .br
 .I <taken>
 is either '-' if the corresponding expression was never evaluated (e.g., the basic block containing the branch was never executed) or
@@ -1424,7 +1424,7 @@ a number indicating how often that branch was taken.
 is 'e' (single character) if this is a branch related to exception handling - and is not present if the branch is not related to exceptions.
 Exception branch identification requires compiler support; note that gcc versions older than 9 do not differentiate exception branches.  Geninfo will be able to identify exception branches only if your toolchain version is new enough to support the feature.
 
-The following is an example branch records whose
+The following are example branch records whose
 .I <branch>
 expression values are human-readable strings.
 
@@ -1443,7 +1443,7 @@ In this case, the corresponding code from line 10 is very likely similar to:
    }
 .br
 .RE
-such that associated testcase entered the block ('enable' evaluated to 'true').
+such that the associated testcase entered the block ('enable' evaluated to 'true').
 
 Arbitrarily complicated branch expressions are supported - including branch expressions which contain commas (e.g., in an expression containing a function call).