summaryrefslogtreecommitdiff
path: root/docs/narr/unittesting.rst
diff options
context:
space:
mode:
authorChris McDonough <chrism@agendaless.com>2009-07-05 22:25:26 +0000
committerChris McDonough <chrism@agendaless.com>2009-07-05 22:25:26 +0000
commit727d349420b2f303bd8bb09fbd506113c8ac0f5c (patch)
treec72d17b06f0b2e8be2fa82ac33b9ee5218cf47e9 /docs/narr/unittesting.rst
parent957a9366a72d4ee406e671e4e3652f85e9a5217c (diff)
downloadpyramid-727d349420b2f303bd8bb09fbd506113c8ac0f5c.tar.gz
pyramid-727d349420b2f303bd8bb09fbd506113c8ac0f5c.tar.bz2
pyramid-727d349420b2f303bd8bb09fbd506113c8ac0f5c.zip
Spellcheck.
Diffstat (limited to 'docs/narr/unittesting.rst')
-rw-r--r--docs/narr/unittesting.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/narr/unittesting.rst b/docs/narr/unittesting.rst
index a0d2b551b..22a36318a 100644
--- a/docs/narr/unittesting.rst
+++ b/docs/narr/unittesting.rst
@@ -39,7 +39,7 @@ The testing API provided by ``repoze.bfg`` allows you to simulate
various application registry registrations for use under a unit
testing framework without needing to invoke the actual application
ZCML configuration. For example, if you wanted to test the above
-``view_fn`` (assming it lived in ``my.package``), you could write a
+``view_fn`` (assuming it lived in ``my.package``), you could write a
unittest TestCase that used the testing API.
.. code-block:: python