From bdcfd1e221f996699522295207a0138522f3ada6 Mon Sep 17 00:00:00 2001 From: Jens Rantil Date: Sun, 10 Jun 2012 18:53:37 +0200 Subject: [PATCH 1/2] Minor spelling fix --- 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 717d26e89..0a8479dc1 100644 --- a/docs/writing/tests.rst +++ b/docs/writing/tests.rst @@ -47,7 +47,7 @@ Some general rules of testing: catching test are among the most valuable piece of code in your project. - Use long and descriptive names for testing functions. The style guide here is - slighlty different than that of running code, where short names are often + slightly different than that of running code, where short names are often preferred. The reason is testing functions are never called explicitely. ``square()`` or even ``sqr()`` is ok in running code, but in testing code you would has names such as ``test_square_of_number_2()``, From a7d4459c956446ca588af4cd51d55e1af13acf02 Mon Sep 17 00:00:00 2001 From: Jens Rantil Date: Sun, 10 Jun 2012 22:17:48 +0200 Subject: [PATCH 2/2] Another minor spelling fix --- docs/intro/duction.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/intro/duction.rst b/docs/intro/duction.rst index 83b3aa713..e0d4180bc 100644 --- a/docs/intro/duction.rst +++ b/docs/intro/duction.rst @@ -18,7 +18,7 @@ include: Python is sometimes described with the words "batteries included" for its extensive - `stanadard library `_, which can + `standard library `_, which can includes modules for regular expressions, file IO, fraction handling, object serialization, and much more.