From ca240c247921a47062d764f625c024d86b1c5b6f Mon Sep 17 00:00:00 2001 From: Jeff Hammerbacher Date: Sat, 22 Feb 2014 18:59:01 -0500 Subject: [PATCH] "faster on tracks" => "back on track faster" --- docs/writing/tests.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/writing/tests.rst b/docs/writing/tests.rst index 4e87491..05faace 100644 --- a/docs/writing/tests.rst +++ b/docs/writing/tests.rst @@ -40,7 +40,7 @@ Some general rules of testing: - If you are in the middle of a development session and have to interrupt your work, it is a good idea to write a broken unit test about what you want to develop next. When coming back to work, you will have a pointer to where you were and get - faster on tracks. + back on track faster. - The first step when you are debugging your code is to write a new test pinpointing the bug. While it is not always possible to do, those bug