diff --git a/README.md b/README.md
index 726d82f..817ceeb 100644
--- a/README.md
+++ b/README.md
@@ -59,6 +59,8 @@
 - Doesn't pollute the global namespace (everything is in namespace ```doctest```) and doesn't drag **any** headers with it
 - Very [**portable**](doc/markdown/features.md#extremely-portable) C++98 - per commit tested on CI with over 330 different builds (static analysis, sanitizers...)
 
+![cost-of-including-the-framework-header](scripts/data/benchmarks/header.png)
+
 This allows the framework to be used in more ways than any other - tests can be written directly in the production code!
 
 Mantra: *Tests can be considered a form of documentation and should be able to reside near the production code which they test.*
diff --git a/doc/markdown/roadmap.md b/doc/markdown/roadmap.md
index ecb3b90..c444e06 100644
--- a/doc/markdown/roadmap.md
+++ b/doc/markdown/roadmap.md
@@ -72,7 +72,7 @@
         - see slide 38 here - https://github.com/boostcon/cppnow_presentations_2017/blob/master/05-19-2017_friday/effective_cmake__daniel_pfeifer__cppnow_05-19-2017.pdf
     - should test crash handling
     - should test more config options
-    - don't cheat for maxing out code coverage (see [coverage_maxout.cpp](../../examples/coverage_maxout.cpp)
+    - don't cheat for maxing out code coverage (see [coverage_maxout.cpp](../../examples/all_features/coverage_maxout.cpp))
     - should test C++11 stuff - perhaps inspect the CMAKE_CXX_FLAGS for -std=c++11 on the CI and add more targets/tests
     - test tricky stuff like expressions with commas in asserts
 
diff --git a/doc/markdown/testcases.md b/doc/markdown/testcases.md
index ed26d46..64be816 100644
--- a/doc/markdown/testcases.md
+++ b/doc/markdown/testcases.md
@@ -120,7 +120,7 @@
 
 - **```skip(bool = true)```** - marks the test case to be skipped from execution - unless the ```--no-skip``` option is used
 - **```may_fail(bool = true)```** - doesn't fail the test if any given assertion fails (but still reports it) - this can be useful to flag a work-in-progress, or a known issue that you don't want to immediately fix but still want to track in the your tests
-- **```should_fail("text")```** - like **```may_fail()```** but fails the test if it passes - his can be useful if you want to be notified of accidental, or third-party, fixes
+- **```should_fail(bool = true)```** - like **```may_fail()```** but fails the test if it passes - his can be useful if you want to be notified of accidental, or third-party, fixes
 - **```expected_failures(int)```** - defines the number of assertions that are expected to fail within the test case - reported as failure when the number of failed assertions is different than the declared expected number of failures
 - **```timeout(double)```** - fails the test case if its execution exceeds this limit (in seconds) - but doesn't terminate it - that would require subprocess support
 - **```test_suite("name")```** - can be used on test cases to override (or just set) the test suite they are in
diff --git a/scripts/random_dev_notes.md b/scripts/random_dev_notes.md
index c28abf1..dbd877f 100644
--- a/scripts/random_dev_notes.md
+++ b/scripts/random_dev_notes.md
@@ -1,4 +1,11 @@
 
+static to inline for exception translator registration
+
+try to forward declare std::string and specialize the string maker for it or something like that
+
+look into this for making dealing with compiler versions easier
+https://github.com/kobalicek/cc_detect/blob/master/cc_detect.h
+
 https://github.com/philsquared/Catch/issues/980
 
 == when making a new release: