#42 good to print

Zuehlke · May 2, 2019 · 7c4b10f · 7c4b10f
1 parent 86b7330
commit 7c4b10f
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/articles/coding-on-purpose.md b/articles/coding-on-purpose.md
@@ -22,7 +22,7 @@ Unfortunately, there are many areas that make no reference at all to the goal. S
 
 * **Code** (and most other models of software, like UML diagrams), which is mostly imperative in its nature, just declares *how* something is achieved but does not state *why*. Although the purpose was hopefully clear to the person writing the code, it is likely to be unknown to the poor coder maintaining the code years later.
 * I've seen too many **bad user stories** that either don't state a goal and benefit or if they do, it's just a wild guess by somebody who wanted to satisfy the template structure. And worse: higher level items like *epics* fail to mention the *purpose* even more often.
-* **BDD (Behaviour Driven Design)** typically uses the *Given, When, Then* pattern, which only describes what the software does, but not why.
+* **BDD (Behaviour Driven Design)** typically uses the *Given-When-Then* pattern, which only describes what the software does, but not why.
 * Many consulting companies **get told *what* to build** instead of *what problem to solve* or *what outcome to achieve*.
 * **Bad managers / leaders** might tell you *what* to build instead of *what outcome to strive for*.
 

diff --git a/articles/how-to-deal-with-flaky-system-tests.md b/articles/how-to-deal-with-flaky-system-tests.md
@@ -21,7 +21,7 @@ As soon as one test fails, insist on fixing it. Otherwise people might start ign
 
 ### Control as much as possible
 
-The more control you have over the system under test (SUT) and the test data, the higher your chances of getting the tests stable. There are many ways to increase control, here are some important ones:
+The more control you have over the system under test (SUT) and the test data, the higher your chances of getting the tests stable. There are many ways to increase control. Here are some important ones:
 
 * Preferably use system tests that cover only the system you are responsible for (at runtime) rather than system integration tests that also include the systems of other teams. This requires simulators to mock the other systems out.
 * Define the exact versions of the libraries you are using in the code, so that you don't get surprised by unintended updates that introduce issues.