* Replaced systemProperties with systemPropertyVariables

  * preventing deprecated warnings with surefire/failsafe plugin.
* Fixed some grammar/typos

README.md

@@ -146,10 +146,10 @@ will execute the integration tests which checks the functionality; The second pa
       <!--
        ! currently needed to run integration tests.
       -->
-      <systemProperties>
+      <systemPropertyVariables>
         <maven.version>${maven.version}</maven.version>
         <maven.home>${maven.home}</maven.home>
-      </systemProperties>
+      </systemPropertyVariables>
     </configuration>
     <executions>
       <execution>

itf-documentation/src/main/asciidoc/background/background.adoc

@@ -101,14 +101,14 @@ and a part which is pom like
 * It's bound to versions of Maven core which might caused issues during testing with other versions
   of Maven.
 * https://maven.apache.org/plugin-testing/maven-plugin-testing-harness/getting-started/index.html
-* Also JUnit 4 based.
+* Also, JUnit 4 based.
 
 //TODO: RECONSIDER this content...
 
 === Mock Repository Manager
 
-Currently it's only possible to have a single instance of the mock repository manager running which
-is based on the limited concept cause we need to define it in the `pom.xml`. Of course
+Currently, it's only possible to have a single instance of the mock repository manager running which
+is based on the limited concept because we need to define it in the `pom.xml`. Of course,
 we could start two or more instances but this would make the setup more or less unreadable.
 
 === Why not Spock?

itf-documentation/src/main/asciidoc/usersguide/usersguide.adoc

@@ -305,7 +305,7 @@ did on plain command line and take a look into it. The output of the build has b
 //FIXME: Needs to be implemented
 
 === Several Test Cases
-If we like to define several integration test cases within a single test class `SeveralMavenIT`
+If we like to define some integration test cases within a single test class `SeveralMavenIT`
 we have to define different methods, which are the test cases. This results in the following
 class layout:
 [source,java]
@@ -397,7 +397,7 @@ directory will look like this:
 Based on the structure you can exactly dive into each test case separately and take
 a look at the console output of the test case via `mvn-stdout.log` or maybe in case of errors
 in the `mvn-stderr.log`. In the `project` directory you will find the usual `target` directory,
-which contains the Maven output which might be interesting as well. Furthermore the
+which contains the Maven output which might be interesting as well. Furthermore, the
 local cache (aka maven repository) is available separately for each test case and can be found
 in the `.m2/repository` directory.
 
@@ -1537,7 +1537,7 @@ The `stderr` output can be accessed as well like this:
 
 include::{itfexample}/itf-examples/src/test/java/com/soebes/itf/examples/LogoutputIT.java[tag=error]
 
-A full fledged example can be found `itf-examples/src/test/java/com/soebes/itf/examples/LogoutputIT.java`
+A full-fledged example can be found `itf-examples/src/test/java/com/soebes/itf/examples/LogoutputIT.java`
 within the itf project.
 
 === Expressing Assertions
@@ -1614,7 +1614,7 @@ The next step is to {intellij-remote}[configure remote debugging] which means to
 as port and check if you are using JDK8 or JDK9+ in your configuration.
 
 I recommend to start only a single integration test case via the above described run configuration,
-in debugging mode otherwise all processes woulduse the same port which would result in failure
+in debugging mode otherwise all processes would use the same port which would result in failure
 because only one can use that port.
 
 ==== Eclipse

itf-examples/pom.xml

@@ -131,10 +131,10 @@
               <!--
                ! currently needed to run integration tests.
               -->
-              <systemProperties>
+              <systemPropertyVariables>
                 <maven.version>${maven.version}</maven.version>
                 <maven.home>${maven.home}</maven.home>
-              </systemProperties>
+              </systemPropertyVariables>
               <properties>
                 <configurationParameters>
                   junit.jupiter.execution.parallel.enabled=true

itf-failure-plugin/pom.xml

@@ -161,10 +161,10 @@
             <configuration>
               <forkCount>5</forkCount>
               <reuseForks>true</reuseForks>
-              <systemProperties>
+              <systemPropertyVariables>
                 <maven.version>${maven.version}</maven.version>
                 <maven.home>${maven.home}</maven.home>
-              </systemProperties>
+              </systemPropertyVariables>
               <properties>
                 <configurationParameters>
                   junit.jupiter.execution.parallel.enabled = false

itf-maven-plugin/src/test/resources-its/com/soebes/itf/maven/plugin/ResourcesIT/basic_resources/pom.xml

@@ -50,12 +50,12 @@ under the License.
       <plugin>
         <groupId>org.apache.maven.plugins</groupId>
         <artifactId>maven-failsafe-plugin</artifactId>
-        <version>3.0.0-M5</version>
+        <version>3.1.2</version>
         <configuration>
-          <systemProperties>
+          <systemPropertyVariables>
             <maven.version>${maven.version}</maven.version>
             <maven.home>${maven.home}</maven.home>
-          </systemProperties>
+          </systemPropertyVariables>
         </configuration>
         <executions>
           <execution>