Updating unit testing page (#430)

* Updates

* Update spacing

Author: MichaelMacaulay

website/pages/en/developing/unit-testing-framework.mdx

@@ -105,7 +105,7 @@ graph test path/to/file.test.ts
 ```sh
 -c, --coverage                Run the tests in coverage mode
 -d, --docker                  Run the tests in a docker container (Note: Please execute from the root folder of the subgraph)
--f  --force                   Binary: Redownloads the binary. Docker: Redownloads the Dockerfile and rebuilds the docker image.
+-f, --force                   Binary: Redownloads the binary. Docker: Redownloads the Dockerfile and rebuilds the docker image.
 -h, --help                    Show usage information
 -l, --logs                    Logs to the console information about the OS, CPU model and download url (debugging purposes)
 -r, --recompile               Forces tests to be recompiled
@@ -990,9 +990,9 @@ Notice that dataSourceMock.resetValues() is called at the end. That's because th
 
 ## Test Coverage
 
-Using **Matchstick**, subgraph developers are able to run a script that will calculate the test coverage of the written unit tests. The tool only works on **Linux** and **MacOS**, but when we add support for Docker (see progress on that [here](https://github.com/LimeChain/matchstick/issues/222)) users should be able to use it on any machine and almost any OS.
+Using **Matchstick**, subgraph developers are able to run a script that will calculate the test coverage of the written unit tests.
 
-The test coverage tool is really simple - it takes the compiled test `wasm` binaries and converts them to `wat` files, which can then be easily inspected to see whether or not the handlers defined in `subgraph.yaml` have actually been called. Since code coverage (and testing as whole) is in very early stages in AssemblyScript and WebAssembly, **Matchstick** cannot check for branch coverage. Instead we rely on the assertion that if a given handler has been called, the event/function for it have been properly mocked.
+The test coverage tool takes the compiled test `wasm` binaries and converts them to `wat` files, which can then be easily inspected to see whether or not the handlers defined in `subgraph.yaml` have been called. Since code coverage (and testing as whole) is in very early stages in AssemblyScript and WebAssembly, **Matchstick** cannot check for branch coverage. Instead we rely on the assertion that if a given handler has been called, the event/function for it have been properly mocked.
 
 ### Prerequisites
 
@@ -1029,7 +1029,7 @@ You could also add a custom `coverage` command to your `package.json` file, like
   },
 ```
 
-Hopefully that should execute the coverage tool without any issues. You should see something like this in the terminal:
+That will execute the coverage tool and you should see something like this in the terminal:
 
 ```sh
 $ graph test -c