Fix typos

Author: kaklakariada

content/2017/01/24/test-coverage-pitfalls.md

@@ -16,11 +16,11 @@ I used the [Mockito](http://mockito.org/) mocking framework to verify that an in
 
 The error was hiding in a regular expression which read
 
-"Needs:\\s*(\\w+(?:,\\s*\\w+)+)"
+    "Needs:\\s*(\\w+(?:,\\s*\\w+)+)"
 
 instead of
 
-"Needs:\\s*(\\w+(?:,\\s*\\w+)*)"
+    "Needs:\\s*(\\w+(?:,\\s*\\w+)*)"
 
 Notice the asterisk in the end.
 

content/2018/10/13/openfasttrace-2-0-0-released.md

@@ -8,12 +8,12 @@ params:
 
 This release is a big step forward. One new feature, a few small fixes and a lot of code improvements that gives us a much cleaner and more uniform API, better test coverage and lower overall complexity.
 
-But a new API also means we had to break backward compatibility to achieve something that the existing API would not allow since it had a separation of report and export mode: you can now reuse an import that already ran to create both reports and exports from it without redoing the import. This is a considerable speed-up (and we call the project Open**Fast**Trace for a reason. Runtime efficiency was and will always be one of our main design principles.
+But a new API also means we had to break backward compatibility to achieve something that the existing API would not allow since it had a separation of report and export mode: you can now reuse an import that already ran to create both reports and exports from it without redoing the import. This is a considerable speed-up (and we call the project Open**Fast**Trace for a reason). Runtime efficiency was and will always be one of our main design principles.
 
 You can find examples of [how to use the API in the user guide](https://github.com/itsallcode/openfasttrace/blob/master/doc/user_guide.md#oft-api) and in OFTs own code of course.
 
 Thanks to Christoph for his patience during his review of the giant change set that the API rework caused!
 
 Enjoy the new and improved API.
 
-Happy tracing.
+Happy tracing.

content/2018/12/19/slow-bash-auto-completion.md

@@ -8,6 +8,8 @@ params:
 
 Today I found a nice [hint on a Cygwin forum on how to debug slow Bash auto-completion](http://www.cygwin.com/ml/cygwin/2010-07/msg00516.html):
 
+```bash
 set -vx
+```
 
-What that does is that it make all the steps visible that the completion uses to come to a result.  No you just have to look if one sticks out especially.
+What that does is that it make all the steps visible that the completion uses to come to a result.  No you just have to look if one sticks out especially.

content/2019/03/09/time-recording-tool.md

@@ -30,7 +30,7 @@ To keep track of my working time I wrote a little time recording tool called Whi
     - Working time of 8h Monday to Friday
     - Mandatory break of 45 minutes after 6 hours of working
 
-# Architectural Descsions
+# Architectural Decisions
 
 The architecture separates business logic (sub-project logic) from the user interface (`textui`). This allows you to add additional user interfaces e.g. using JavaFX or Swing.
 
@@ -96,4 +96,4 @@ We use JSON for storage because this enables the user to manually make changes (
 2019-03-08 Fri WORK      08:00 - 18:30 break: 00:45, interr.: 01:20, working time: 08:25, overtime: 00:25, Acc. overtime: -07:20, 1h 20min of interruption
 2019-03-09 Sat WEEKEND                 break: 00:00, working time: 00:00, overtime: 00:00, Acc. overtime: -07:20, Saturday and Sunday automatically detected, no need to add them here.
 Total overtime: PT-7H-20M
-```
+```