Reformatted JSON.md to have one sentence per line

Signed-off-by: jakub-nt <175944085+jakub-nt@users.noreply.github.com>

Author: jakub-nt

JSON.md

@@ -223,7 +223,8 @@ These are copies of the module directories, where it's more "safe" to do things
 ## All available build steps
 
 The build steps below manipulate the temporary files in the steps directories and write results to the output policy set, in `out/masterfiles`.
-Unless otherwise noted, all steps are run inside the module's folder (`out/steps/...`) with sources / file paths relative to that folder, and targets / destinations mentioned below are relative to the output policy set (`out/masterfiles`, which in the end will be deployed as `/var/cfengine/masterfiles`). In `cfbs.json`'s `"steps"`, the build step name must be separated from the rest of the build step by a regular space.
+Unless otherwise noted, all steps are run inside the module's folder (`out/steps/...`) with sources / file paths relative to that folder, and targets / destinations mentioned below are relative to the output policy set (`out/masterfiles`, which in the end will be deployed as `/var/cfengine/masterfiles`).
+In `cfbs.json`'s `"steps"`, the build step name must be separated from the rest of the build step by a regular space.
 
 - `copy <source> <destination>`
   - Copy a single file or a directory recursively.
@@ -450,11 +451,9 @@ cfbs init && cfbs add https://github.com/cfengine/some-repo
 
 ## Modules with input
 
-Some modules allow for users to add module input by responding to questions
-expressed under the `"input"` attribute in `cfbs.json`. User input can be added
-using the `cfbs input <module-name>` command, which stores responses in
-`./<module-name>/input.json`. These responses are translated into augments which
-will be added to `./out/masterfiles/def.json` during `cfbs build`.
+Some modules allow for users to add module input by responding to questions expressed under the `"input"` attribute in `cfbs.json`.
+User input can be added using the `cfbs input <module-name>` command, which stores responses in `./<module-name>/input.json`.
+These responses are translated into augments which will be added to `./out/masterfiles/def.json` during `cfbs build`.
 
 ### Create single file example
 
@@ -490,10 +489,8 @@ The `"input"` attribute takes a list of input definitions as illustrated below.
 }
 ```
 
-From the example above, we can see that the `"input"` list contains one input
-definition. By running the command `cfbs input create-single-file`, the input
-definition will be copied into `./create-single-file/input.json` along with the
-user responses.
+From the example above, we can see that the `"input"` list contains one input definition.
+By running the command `cfbs input create-single-file`, the input definition will be copied into `./create-single-file/input.json` along with the user responses.
 
 ```
 $ cfbs input create-single-file
@@ -511,10 +508,8 @@ $ cat ./create-single-file/input.json
 ]
 ```
 
-By running `cfbs build`, augments will be generated from
-`./create-single-file/input.json` and added to `./out/masterfiles/def.json`.
-Note that this is dependant on the `"input ./input.json def.json"` build step in
-`cfbs.json`.
+By running `cfbs build`, augments will be generated from `./create-single-file/input.json` and added to `./out/masterfiles/def.json`.
+Note that this is dependent on the `"input ./input.json def.json"` build step in `cfbs.json`.
 
 ```
 $ cfbs build
@@ -538,13 +533,12 @@ $ cat ./out/masterfiles/def.json
 }
 ```
 
-From the example above we can see our beloved `filename`-variable along with a
-class generated by the autorun dependency. Studying our variable closer, we can
-see that a namespace, bundle, and a comment, were automatically assigned some
-default values. I.e. `cfbs`, the module name canonified, and `Added by 'cfbs
-input'` respectivy. These defaults can easily be overridden using the
-`namespace`, `bundle`, and `comment` attributes in the variable definition. E.g.
-the following variable definition;
+From the example above we can see our beloved `filename`-variable along with a class generated by the autorun dependency.
+Studying our variable closer, we can see that a namespace, bundle, and a comment, were automatically assigned some default values.
+I.e. `cfbs`, the module name canonified, and `Added by 'cfbs
+input'` respectively.
+These defaults can easily be overridden using the `namespace`, `bundle`, and `comment` attributes in the variable definition.
+E.g. the following variable definition;
 
 ```json
       "input": [
@@ -575,9 +569,8 @@ would produce the following augment;
 
 ### Create a single file with content example
 
-A module that creates empty files is not too impressive on its own. Let us
-instead try to extend our previous example by having the module also ask for
-file contents.
+A module that creates empty files is not too impressive on its own.
+Let us instead try to extend our previous example by having the module also ask for file contents.
 
 ```json
 {
@@ -615,9 +608,8 @@ file contents.
 }
 ```
 
-As you can see from the example above, the extension would only require us to
-add another variable to the input definition. Let's have a look at the results
-from running `cfbs input` with our extension module.
+As you can see from the example above, the extension would only require us to add another variable to the input definition.
+Let's have a look at the results from running `cfbs input` with our extension module.
 
 ```
 $ cfbs input create-single-file-with-content
@@ -651,9 +643,9 @@ $ cat ./out/masterfiles/def.json
 
 ### Create multiple files example
 
-Sometimes we would like a module to support taking an arbritary number of
-inputs. This can be done using a variable definition of type list. Let's extend
-our first example from creating a single to multiple files.
+Sometimes we would like a module to support taking an arbritary number of inputs.
+This can be done using a variable definition of type list.
+Let's extend our first example from creating a single to multiple files.
 
 ```json
 {
@@ -702,8 +694,7 @@ What file should this module create? /tmp/create-multiple-files-2.txt
 Do you want to create another file? no
 ```
 
-The _*./create-multiple-files/input.json*_ file would look similar to the
-following JSON:
+The _*./create-multiple-files/input.json*_ file would look similar to the following JSON:
 
 ```json
 [
@@ -725,8 +716,7 @@ following JSON:
 ]
 ```
 
-And if we build our project we can expect something similar to the following
-output:
+And if we build our project we can expect something similar to the following output:
 
 ```
 $ cfbs build
@@ -755,8 +745,7 @@ $ cat ./out/masterfiles/def.json
 
 ### Create multiple files with content example
 
-As a final example, let's see how we can build a module that takes an arbritary
-number of filename and content pairs as input.
+As a final example, let's see how we can build a module that takes an arbitrary number of filename and content pairs as input.
 
 ```json
 {