Proof-read documentation text

[EOstridge]

Is your feature request related to a problem? Please describe.

Users don't want to see errors within the documentation.

Describe the solution you'd like

Proof-read the documentation text and check for the following:

• Fix missing closing brackets (see first screenshot), typos, grammatical errors etc.
• Check whether the timings table (expected run times and performance) should use the more than (>) sign or the less than (<) sign
• Specify what hardware we are running on for the timings table