diff --git a/content/conclusions.md b/content/conclusions.md
index 8cd28a0..d2872a7 100644
--- a/content/conclusions.md
+++ b/content/conclusions.md
@@ -1,6 +1,7 @@
 # Conclusions and recommendations
 
 ## The basics
+
 - Learn one test framework well enough for basics
   - Explore and use the good tools that exist out there
   - An incomplete list of testing frameworks can be found in the [Quick Reference](quick-reference)
@@ -9,11 +10,12 @@
 - Automate tests
   - Faster feedback and reduce the number of surprises
 
+
 ## Going more in-depth
 
 - Strike a healthy balance between unit tests and integration tests
 - As the code gets larger and the chance of undetected bugs
-  increases, tests should increase.
+  increases, tests should increase
 - When adding new functionality, also add tests
 - When you discover and fix a bug, also commit a test against this bug
 - Use code coverage analysis to identify untested or unused code
@@ -32,6 +34,6 @@ what are some of the easy starting points?
   end-to-end test with sample data, or sample parameters.  This is
   useful as an example anyway.
 
-- A local testing framework + Github actions is very easy!  And works
+- A local testing framework + GitHub actions is very easy!  And works
   well in the background - you do whatever you want and get an email
   if you break things.  It's actually pretty freeing.