Fix various typos in documentation and code (#2660)

Author: mlvandijk

.spotless/intelij-idea.importorder renamed to .spotless/intellij-idea.importorder

@@ -1,4 +1,4 @@
-# Organize import order using Intelij IDEA defaults
+# Organize import order using IntelliJ IDEA defaults
 # Escaped hashes sort static methods last: https://github.com/diffplug/spotless/issues/306
 1=
 2=javax

CONTRIBUTING.md

@@ -7,7 +7,7 @@ We appreciate that. Do keep the following in mind:
 * When you send a [pull requests](https://help.github.com/articles/using-pull-requests), 
   please include tests to go along with it.
 * Want to paste some code or output? Put \`\`\` on a line above and below your 
-  code/output. See [Github Flavored Markdown](https://help.github.com/articles/github-flavored-markdown)'s 
+  code/output. See [GitHub Flavored Markdown](https://help.github.com/articles/github-flavored-markdown)'s 
   *Fenced Code Blocks* for details.
 
 ## Formatting Java

cucumber-archetype/README.md

@@ -1,7 +1,6 @@
 # Cucumber Archetype
 
-This is a Maven Archetype for setting up an empty Cucumber project. Used by the
-the [10-Minute Cucumber Tutorial](https://docs.cucumber.io/guides/10-minute-tutorial/).
+This is a Maven Archetype for setting up an empty Cucumber project. Used by the [10-Minute Cucumber Tutorial](https://docs.cucumber.io/guides/10-minute-tutorial/).
 
 ```shell
 mvn archetype:generate                                  \

cucumber-bom/README.md

@@ -1,6 +1,6 @@
 # Bill of Materials
 
-It is fairly common for one project to use more than one cucumber dependency. To
+It is fairly common for one project to use more than one Cucumber dependency. To
 keep these version in sync a Bill of Materials can be used.
 
 ## Usage

cucumber-core/README.md

@@ -4,7 +4,7 @@ Cucumber Core
 Provides components needed to discover, parse and execute feature files. The
 core is designed with a few extension systems and plugin points. You
 typically don't depend directly on `cucumber-core` but rather use the different
-sub modules together e.g. `cucumber-junit` and `cucumber-java`.     
+submodules together e.g. `cucumber-junit` and `cucumber-java`.     
 
 ## Properties, Environment variables, System Options ##
 
@@ -14,7 +14,7 @@ Note that the CLI arguments take precedence over all.
 
 Note that the `cucumber-junit-platform-engine` is provided with properties
 by the Junit Platform rather than Cucumber. See
-[junit-platform-engine Configuration Options](../junit-platform-engine#configuration-options)
+[junit-platform-engine Configuration Options](../cucumber-junit-platform-engine#configuration-options)
 for more information.
 
 Supported properties are:

cucumber-deltaspike/README.md

@@ -25,12 +25,13 @@ public class BellyStepdefs {
     private Belly belly;
 
     //normal step code ...
+}
 ```
 
 This ObjectFactory doesn't start or stop any [Scopes](https://docs.oracle.com/javaee/6/tutorial/doc/gjbbk.html), so all beans live inside the default scope (Dependent). Now cucumber requested a instance of your stepdefinitions for every step, which means cdi create a new instance for every step and for all injected fields. This behaviour makes it impossible to share a state inside a szenario.
 
 To bybass this, you must annotate your class(es) with `@javax.inject.Singleton`:
-1. on stepdefintions: now the ojectfactory will creates only one instance include injected fields per scenario and both injected fields and stepdefinitions can be used to share state inside a scenario.
+1. on stepdefintions: now the ojectfactory will create only one instance include injected fields per scenario and both injected fields and stepdefinitions can be used to share state inside a scenario.
 2. on any other class: now the objectfactory will create a new instance of your stepdefinitions per step and stepdefinitions can not be used to share state inside a scenario, only the annotated classes can be used to share state inside a scenario
 
 you can also combine both approaches.
@@ -43,10 +44,11 @@ public class BellyStepdefs {
     private Belly belly;
 
     //normal step code ...
+}
 ```
 It is not possible to use any other scope than Dependent this means alsoi it is not possible to share a state over two or more scenarios, every scenario start with a clean environment.
 
-To enable this objectfactory add the folling dependency to your classpath:
+To enable this objectfactory add the following dependency to your classpath:
 ```xml
 <dependency>
     <groupId>io.cucumber</groupId>

cucumber-java/README.md

@@ -156,7 +156,7 @@ Notes:
 
  1. When used in combination with Junit 5, Maven Surefire, and/or Failsafe use 
     version `3.0.0-M5` or later.
- 2. When used in combination with Junit 5 and InteliJ IDEA failures in before
+ 2. When used in combination with Junit 5 and IntelliJ IDEA failures in before
     all and after all hooks do not fail a test run.
 
 ### Before / After

cucumber-java8/README.md

@@ -240,7 +240,7 @@ public class StepDefinitions implements En {
     public StepDefinitions() {
         DataTableType((Map<String, String> entry) -> new User(
             entry.get("firstname"),
-            entry.get("lastname")
+            entry.get("lastname"),
             entry.get("nationality")
         ));
 

cucumber-junit/README.md

@@ -1,7 +1,7 @@
 Cucumber JUnit 
 ==============
 
-Use JUnit to execute cucumber scenarios. To use add the `cucumber-junit`
+Use JUnit to execute Cucumber scenarios. To use add the `cucumber-junit`
 dependency to your pom.xml:
 
 ```xml
@@ -45,16 +45,16 @@ 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 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 Cucumber's hooks](../java#beforeall--afterall).
+[Cucumber-Eclipse](https://github.com/cucumber/cucumber-eclipse). Instead, it is
+recommended to [use Cucumber's hooks](../cucumber-java#beforeall--afterall).
 
 ## Using other JUnit features ##
 
 The Cucumber runner acts like a suite of a JUnit tests. As such other 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).
+For more information on JUnit, see the [JUnit website](http://www.junit.org).
 
 ## Assume ## 
 

cucumber-testng/README.md

@@ -1,7 +1,7 @@
 Cucumber TestNG 
 ==============
 
-Use TestNG to execute cucumber scenarios. To use add the `cucumber-testng` dependency to your pom.
+Use TestNG to execute Cucumber scenarios. To use add the `cucumber-testng` dependency to your pom.
 
 ```xml
 <dependencies>