summaryrefslogtreecommitdiffstats
path: root/Doc/faq/design.rst
diff options
context:
space:
mode:
authorIlya Kamenshchikov <ikamenshchikov@gmail.com>2019-07-16 15:13:38 (GMT)
committerRaymond Hettinger <rhettinger@users.noreply.github.com>2019-07-16 15:13:38 (GMT)
commita0f7119f1584db5b32deffb60a68d830673ebbdf (patch)
tree4990234dbf34863b88dd1000cb755ff84ced1699 /Doc/faq/design.rst
parent6a61714cde7037cd9a1bcc11ecccb17fe3081295 (diff)
downloadcpython-a0f7119f1584db5b32deffb60a68d830673ebbdf.zip
cpython-a0f7119f1584db5b32deffb60a68d830673ebbdf.tar.gz
cpython-a0f7119f1584db5b32deffb60a68d830673ebbdf.tar.bz2
bpo-37352: Minor word-smithing for design.rst (GH #14730)
Diffstat (limited to 'Doc/faq/design.rst')
-rw-r--r--Doc/faq/design.rst10
1 files changed, 5 insertions, 5 deletions
diff --git a/Doc/faq/design.rst b/Doc/faq/design.rst
index 387420c..47fc4d4 100644
--- a/Doc/faq/design.rst
+++ b/Doc/faq/design.rst
@@ -641,11 +641,11 @@ to the end of some internal list; an interface specification cannot test that
your :meth:`append` implementation will actually do this correctly, but it's
trivial to check this property in a test suite.
-Writing test suites is very helpful, and you might want to design your code with
-an eye to making it easily tested. One increasingly popular technique,
-test-directed development, calls for writing parts of the test suite first,
-before you write any of the actual code. Of course Python allows you to be
-sloppy and not write test cases at all.
+Writing test suites is very helpful, and you might want to design your code to
+make it easily tested. One increasingly popular technique, test-driven
+development, calls for writing parts of the test suite first, before you write
+any of the actual code. Of course Python allows you to be sloppy and not write
+test cases at all.
Why is there no goto?