Fix various typos in documentation (#1962)

Author: natritmeyer

core/README.md

@@ -13,7 +13,7 @@ When property parsing functionality is not provided by the runner (i.e.
 properties from system properties, environment variables and the
 `cucumber.properties` file.
 
-Note that options provided by `@CucumberOptions` takes precedence over the
+Note that options provided by `@CucumberOptions` take precedence over the
 properties file and CLI arguments take precedence over all.
 
 Supported properties are:
@@ -40,10 +40,10 @@ Each property also has an `UPPER_CASE` and `snake_case` variant. For example
 
 ## Backend ##
 
-Backends consists of two components, a `Backend` and `ObjectFactory`. They are
-respectively responsible for discovering glue classes, registering step definitions
+Backends consist of two components: a `Backend`, and an `ObjectFactory`. They are
+respectively responsible for discovering glue classes, registering step definitions,
 and creating instances of said glue classes. Backend and object factory
-implementations are discovered via SPI
+implementations are discovered via SPI.
 
 ## Plugin ##
 

java8/README.md

@@ -1,7 +1,7 @@
 Cucumber Java8
 ==============
 
-Provides annotation based step definitions. To use add the `cucumber-java8` dependency to your pom.xml:
+Provides lambda based step definitions. To use add the `cucumber-java8` dependency to your pom.xml:
 
 ```xml
 <dependencies>
@@ -86,7 +86,7 @@ Data table types can be declared by calling `DataTableType` in the constructor.
 Depending on the lambda type this will be either a: 
  * `String` -> `io.cucumber.datatable.TableCellTranformer`
  * `Map<String,String>` -> `io.cucumber.datatable.TableEntry`
- * `List<String` -> `io.cucumber.datatable.TableRow`
+ * `List<String>` -> `io.cucumber.datatable.TableRow`
  * `DataTable` -> `io.cucumber.datatable.TableTransformer`
 
 ```java

junit-platform-engine/README.md

@@ -63,7 +63,7 @@ either the Maven Antrun plugin or the Gradle JavaExec task.
             <artifactId>maven-antrun-plugin</artifactId>
             <executions>
                 <execution>
-                    <!--Work around. Surefire does not use JUnits Test Engine discovery functionality -->
+                    <!--Work around. Surefire does not use JUnit's Test Engine discovery functionality -->
                     <id>CLI-test</id>
                     <phase>integration-test</phase>
                     <goals>
@@ -91,8 +91,8 @@ either the Maven Antrun plugin or the Gradle JavaExec task.
     </plugins>
 </build>
 ```
-```groovy
 
+```groovy
 tasks {
 
 	val consoleLauncherTest by registering(JavaExec::class) {
@@ -120,7 +120,7 @@ tests in parallel is available as an opt-in feature. To enable parallel
 execution, set the `cucumber.execution.parallel.enabled` configuration
 parameter to `true`, e.g. in `junit-platform.properties`.
 
-Cucumber supports JUnits `ParallelExecutionConfigurationStrategy` see the
+Cucumber supports JUnit's `ParallelExecutionConfigurationStrategy`; see the
 configuration options below.
 
 ### Exclusive Resources ###
@@ -133,7 +133,6 @@ either locked with a read-write-lock, or a read lock.
 
 For example:
 
- 
 ```gherkin
 Feature: Exclusive resources
 
@@ -149,7 +148,6 @@ Feature: Exclusive resources
    Given this reads resource a
    When it is executed it will
    Then it will not be executed concurrently with the first example
-
 ```
 
 With this configuration: 
@@ -235,7 +233,7 @@ The `UriSelector` supports URI's with a `line` query parameter:
   - `classpath:/com/example/example.feature?line=20`
   - `file:/path/to/com/example/example.feature?line=20`
 
-Any `TestDescriptor` that matches the line *and* its descendents will be 
+Any `TestDescriptor` that matches the line *and* its descendants will be
 included in the discovery result.
 
 ## Tags ##
@@ -267,7 +265,7 @@ The example below will execute `Another tagged scenario`.
 mvn verify -DexcludedGroups="Ignore" -Dgroups="Smoke | Sanity"
 ```
 
-For further information See the relevant documentation on how to select tags:
+For further information on how to select tags see the relevant documentation:
 * [Maven: Filtering by Tags](https://maven.apache.org/surefire/maven-surefire-plugin/examples/junit-platform.html)
 * [Gradle: Test Grouping](https://docs.gradle.org/current/userguide/java_testing.html#test_grouping)
 * [JUnit 5 Console Launcher: Options](https://junit.org/junit5/docs/current/user-guide/#running-tests-console-launcher-options)

junit/README.md

@@ -32,27 +32,26 @@ public class RunCucumberTest {
 }
 ```
 
-This will execute all scenarios in same package as the runner, by default glue
+This will execute all scenarios in the same package as the runner; by default glue
 code is also assumed to be in the same 
 package. The `@CucumberOptions` can be used to provide
 [additional configuration](https://docs.cucumber.io/cucumber/api/#list-configuration-options) 
 to the runner. 
 
-
 ## Using JUnit Rules ##
 
-Cucumber supports JUnits `@ClassRule`, `@BeforeClass` and `@AfterClass` 
-annotations. These will executed before and 
-after all scenarios. Using these is not recommended as it limits the portability
+Cucumber supports JUnit's `@ClassRule`, `@BeforeClass`, and `@AfterClass`
+annotations. These will be executed before and
+after all scenarios. Using these is not recommended as it limits portability
 between different runners; they may not
-execute correctly when using the commandline, [IntelliJ IDEA](https://www.jetbrains.com/help/idea/cucumber.html) or
+execute correctly when using the command line, [IntelliJ IDEA](https://www.jetbrains.com/help/idea/cucumber.html), or
 [Cucumber-Eclipse](https://github.com/cucumber/cucumber-eclipse). Instead it is
-recommended to use Cucumbers `Before` and `After` hooks.
+recommended to use Cucumber's `Before` and `After` hooks.
 
 ## Using other JUnit features ##
 
 The Cucumber runner acts like a suite of a JUnit tests. As such other JUnit
-features such as Custom JUnit 
+features like custom JUnit
 Listeners and Reporters can all be expected to work.
 
 For more information on JUnit, see the [JUnit web site](http://www.junit.org).
@@ -63,8 +62,8 @@ Through [Assume](https://junit.org/junit4/javadoc/4.12/org/junit/Assume.html)
 and [Assumptions](https://junit.org/junit5/docs/5.0.0/api/org/junit/jupiter/api/Assumptions.html) 
 JUnit4 and JUnit5 provide: 
 
->  a collection of utility methods that support conditional test execution based
->  on assumptions.
+> a collection of utility methods that support conditional test execution based
+> on assumptions.
 > 
 > In direct contrast to failed assertions, failed assumptions do not result in a
 > test failure; rather, a failed assumption results in a test being aborted.
@@ -73,7 +72,7 @@ JUnit4 and JUnit5 provide:
 > execution of a given test method — for example, if the test depends on
 > something that does not exist in the current runtime environment. 
 
-The Cucumber runner supports `Assume` and will marked skipped scenarios as 
+The Cucumber runner supports `Assume` and will mark skipped scenarios as
 skipped.
 
 ## Parallel Execution with Maven ##

needle/README.md

@@ -2,7 +2,7 @@
 
 Implements an ObjectFactory that instantiates glue code via [needle](http://needle.spree.de).
 
-This allows easy configurable dependency injection without relying on a full blown DI
-container and automatic mocking of all not explicitly specified dependencies. 
+This allows easy, configurable dependency injection and automatic mocking of all not
+explicitly specified dependencies, without relying on a full blown DI container.
 
-See [needle tutorial](http://needle.spree.de/tutorial) for more information.
+See [needle tutorial](http://needle.spree.de/tutorial.html) for more information.

picocontainer/README.md

@@ -60,7 +60,7 @@ All step classes and their dependencies will be recreated for each
 scenario, even if the scenario in question does not use any steps from
 that particular class.
 
-To improve performance it recommended to lazily create expensive 
+To improve performance it is recommended to lazily create expensive
 resources.
 
 ```java
@@ -84,10 +84,10 @@ public class LazyWebDriver implements Webdriver {
 }
 ```
 
-Step classes or their dependencies which own resources which need cleanup
+Step classes or their dependencies which own resources requiring cleanup
 should implement `org.picocontainer.Disposable` as described in
 [PicoContainer - Component Lifecycle](http://picocontainer.com/lifecycle.html).
-These hooks will run after any Cucumber after hooks hooks.
+These hooks will run after any Cucumber after hooks.
 
 ## Customizing PicoContainer
 

spring/README.md

@@ -42,7 +42,7 @@ public class CucumberSpringConfiguration {
 }
 ```
 
-Note: Cucumber Spring uses Springs `TestContextManager` framework internally.
+Note: Cucumber Spring uses Spring's `TestContextManager` framework internally.
 As a result a single Cucumber scenario will mostly behave like a JUnit test.
 
 For more information configuring Spring tests see:
@@ -71,7 +71,7 @@ public class MyStepDefinitions {
 
 ## Sharing State 
 
-Cucumber Spring creates an application context and using Springs
+Cucumber Spring creates an application context and uses Spring's
 `TestContextManager` framework internally. All scenarios as well as all other
 tests (e.g. JUnit) that use the same context configuration will share one
 instance of the Spring application. This avoids an expensive startup time.

testng/README.md

@@ -62,7 +62,7 @@ public class RunCucumberTest extends AbstractTestNGCucumberTests {
 }
 ```
 
-#### Maven Surefire plugin configuation for parallel execution ####
+#### Maven Surefire plugin configuration for parallel execution ####
 
 ```xml
 <plugins>