Small tweaks in headings for consistency

W. Trevor King: I dropped everything from the original 23ba35f except
for the testing/README.md modification.

Conflicts:
	version-control/README.md

diff --git a/testing/README.md b/testing/README.md
index 1edf7f61b0dc62be3fe65749fdc7f2405a44c3d2..d577306cd8e141d42bd2776a7a2df4ec13904c89 100755 (executable)
--- a/testing/README.md
+++ b/testing/README.md
@@ -4,7 +4,6 @@ Thanks to Gordon Webster, the [Digital Biologist](http://www.digitalbiologist.co
 
 ## Detecting errors
 
-
 What we know about software development - code reviews work. Fagan (1976) discovered that a rigorous inspection can remove 60-90% of errors before the first test is run. M.E., Fagan (1976). [Design and Code inspections to reduce errors in program development](http://www.mfagan.com/pdfs/ibmfagan.pdf). IBM Systems Journal 15 (3): pp. 182-211.
 
 What we know about software development - code reviews should be about 60 minutes long. Cohen (2006) discovered that all the value of a code review comes within the first hour, after which reviewers can become exhausted and the issues they find become ever more trivial. J. Cohen (2006). [Best Kept Secrets of Peer Code Review](http://smartbear.com/SmartBear/media/pdfs/best-kept-secrets-of-peer-code-review.pdf). SmartBear, 2006. ISBN-10: 1599160676. ISBN-13: 978-1599160672.
@@ -296,13 +295,13 @@ TDD delivers tests and a function - no risk of us leaving the tests "till later"
 
 Refactor code with security of tests to flag any changes made introduce a bug.
 
-## Conclusions and further information
+## Summary
 
 Testing
 
-* Saves us time.
-* Gives us confidence that our code does what we want and expect it to.
-* Promotes trust that our code, and so our research, is correct.
+* Saves time.
+* Gives confidence that code does what we want and expect it to.
+* Promotes trust that code, and so research, is correct.
 
 Remember [Geoffrey Chang](http://en.wikipedia.org/wiki/Geoffrey_Chang)