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 <http://docs.python.org/library/>`_, which can
+  `standard library <http://docs.python.org/library/>`_, which can
   includes modules for regular expressions, file IO, fraction handling,
   object serialization, and much more.
 
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()``,