Merge pull request #22 from Ragin-LundF/develop

Documentation for Release

CHANGELOG.md

@@ -2,13 +2,13 @@
 
 ## Absolute file path support
 
-Files can be added as relative path to a previously given base path or with an "absolute" path with the prefix `absolutePath:`.
-In the last case the system is using the base classpath as root.
+Files can be added as a relative path to a previously given base path or with an "absolute" path with the prefix `absolutePath:`.
+In the last case, the system is using the base classpath as root.
 
-## Validate response http code and body together
+## Validate response HTTP code and body together
 ```gherkin
 Scenario:
-  Then Then I ensure that the response code is 201 and the body is equal to
+  Then I ensure that the response code is 201 and the body is equal to
     """
     {
       "field": "value",
@@ -20,12 +20,16 @@ In this case, the response status code is part of the sentence, and the JSON is
 Here it is also possible to use [JSON Unit](https://github.com/lukas-krecan/JsonUnit) syntax to validate dynamic elements.
 
 
-## Validate response http code and body together with a JSON file
+## Validate response HTTP code and body together with a JSON file
 ```gherkin
 Scenario:
   Then I ensure that the response code is 200 and the body is equal to the file "response.json"
 ```
 
+In this case, the response status code, and the JSON file are written together in one sentence.
+Here it is also possible to use [JSON Unit](https://github.com/lukas-krecan/JsonUnit) syntax to validate dynamic elements.
+
+
 # Release 1.16.0
 - Changing the body manipulation with creating numbers from `<number> characters` to `<number> bdd_lib_numbers` (e.g. `10 bdd_lib_numbers`).
 - Adding `bdd_lib_uuid` to generate random UUIDs

README.md

@@ -364,10 +364,10 @@ Scenario:
 In this case, the JSON is written directly under the sentence and enclosed in three double quotation marks.
 Here it is also possible to use [JSON Unit](https://github.com/lukas-krecan/JsonUnit) syntax to validate dynamic elements.
 
-#### Validate response http code and body together
+#### Validate response HTTP code and body together
 ```gherkin
 Scenario:
-  Then Then I ensure that the response code is 201 and the body is equal to
+  Then I ensure that the response code is 201 and the body is equal to
     """
     {
       "field": "value",
@@ -377,17 +377,17 @@ Scenario:
 
 In this case, the response status code is part of the sentence, and the JSON is written directly under the sentence and enclosed in three double quotation marks.
 Here it is also possible to use [JSON Unit](https://github.com/lukas-krecan/JsonUnit) syntax to validate dynamic elements.
-
 
-#### Validate response http code and body together with a JSON file
+
+#### Validate response HTTP code and body together with a JSON file
 ```gherkin
 Scenario:
   Then I ensure that the response code is 200 and the body is equal to the file "response.json"
 ```
 
 In this case, the response status code, and the JSON file are written together in one sentence.
 Here it is also possible to use [JSON Unit](https://github.com/lukas-krecan/JsonUnit) syntax to validate dynamic elements.
- 
+
 
 #### Read from Response and set it to a `Feature` context
 ```gherkin