Fix typos (#1579)

org.jacoco.core/src/org/jacoco/core/analysis/IClassCoverage.java

@@ -31,7 +31,7 @@ public interface IClassCoverage extends ISourceNode {
 	long getId();
 
 	/**
-	 * Returns if the the analyzed class does match the execution data provided.
+	 * Returns if the analyzed class does match the execution data provided.
 	 * More precisely if execution data is available for a class with the same
 	 * qualified name but with a different class id.
 	 *

org.jacoco.core/src/org/jacoco/core/analysis/ICoverageNode.java

@@ -124,7 +124,7 @@ enum CounterEntity {
 	ICounter getClassCounter();
 
 	/**
-	 * Generic access to the the counters.
+	 * Generic access to the counters.
 	 *
 	 * @param entity
 	 *            entity we're we want to have the counter for

org.jacoco.doc/docroot/doc/agent.html

@@ -28,7 +28,7 @@ <h1>Java Agent</h1>
 <p class="hint">
   If you use the <a href="ant.html">JaCoCo Ant tasks</a> or
   <a href="maven.html">JaCoCo Maven plug-in</a> you don't have to care about the
-  agent and its options directly. This is transparently handled by the them.
+  agent and its options directly. This is transparently handled by them.
 </p>
 
 <p>

org.jacoco.doc/docroot/doc/flow.html

@@ -144,7 +144,7 @@ <h3>Flow Edges</h3>
 
 <p>
   The current JaCoCo implementation ignores edges caused by implicit exceptions
-  and the the method entry. This means we consider SEQUENCE, JUMP, EXIT.
+  and the method entry. This means we consider SEQUENCE, JUMP, EXIT.
 </p>
 
 
@@ -253,7 +253,7 @@ <h2>Probe Insertion Strategy</h2>
   Now let's see how this rules apply to the example snippet above. We see that
   <code>INVOKE d()</code> instruction is the only node with more than one
   incoming edge. So we need to place probes on those edges and another probe on
-  the only exit node. The result is shown the the right box of the diagram
+  the only exit node. The result is shown the right box of the diagram
   above.
 </p>
 
@@ -264,7 +264,7 @@ <h2>Additional Probes Between Lines</h2>
   exceptions thrown for example from invoked methods. If the control flow
   between two probes is interrupted by a exception not explicitly created with
   a <code>throw</code> statement all instruction in between are considered as
-  not covered. This leads to unexpected results especially when the the block of
+  not covered. This leads to unexpected results especially when the block of
   instructions spans multiple lines of source code.
 </p>
 

org.jacoco.doc/docroot/index.html

@@ -101,7 +101,7 @@ <h2>Contents</h2>
 </table>
 
 <p>
-  All libraries as well as the the JaCoCo <a href="doc/maven.html">Maven plug-in</a>
+  All libraries as well as the JaCoCo <a href="doc/maven.html">Maven plug-in</a>
   are also available from the Maven <a href="doc/repo.html">repository</a>.
 </p>
 

org.jacoco.report/src/org/jacoco/report/IReportGroupVisitor.java

@@ -37,7 +37,7 @@
 public interface IReportGroupVisitor {
 
 	/**
-	 * Called to add a bundle to the the report.
+	 * Called to add a bundle to the report.
 	 *
 	 * @param bundle
 	 *            a bundle to include in the report