Fix typos.

docs/src/reference/extension_types.rst

@@ -102,7 +102,7 @@ Properties
 
 * The ``__get__()``, ``__set__()``, and ``__del__()`` methods are all optional.
 
- * If they are ommitted, An exception is raised when an access attempt is made.
+ * If they are omitted, An exception is raised when an access attempt is made.
 
 * Below, is a full example that defines a property which can..
 
@@ -364,7 +364,7 @@ Extension Types and None
 
 * When accessing an extension type's C-attributes, **make sure** it is not ``None``.
 
- * Cython does not check this for reasons of efficency.
+ * Cython does not check this for reasons of efficiency.
 
 * Be very aware of exposing Python functions that take extension types as arguments::
 
@@ -418,7 +418,7 @@ External and Public Types
 Public
 ======
 
-* When an extention type is declared ``public``, Cython will generate a C-header (".h") file.
+* When an extension type is declared ``public``, Cython will generate a C-header (".h") file.
 * The header file will contain the declarations for it's **object-struct** and it's **type-object**.
 * External C-code can now access the attributes of the extension type.
 
@@ -459,7 +459,7 @@ External
     #. When declaring an external extension type...
 
      * Don't declare any methods, because they are Python method class the are not needed.
-     * Similiar to **structs** and **unions**, extension classes declared inside a ``cdef extern from`` block only need to declare the C members which you will actually need to access in your module.
+     * Similar to **structs** and **unions**, extension classes declared inside a ``cdef extern from`` block only need to declare the C members which you will actually need to access in your module.
 
 
 Name Specification Clause

docs/src/reference/language_basics.rst

@@ -297,7 +297,7 @@ Optional Arguments
 Keyword-only Arguments
 =======================
 
-* As in Python 3, ``def`` functions can have keyword-only argurments listed after a ``"*"`` parameter and before a ``"**"`` parameter if any::
+* As in Python 3, ``def`` functions can have keyword-only arguments listed after a ``"*"`` parameter and before a ``"**"`` parameter if any::
 
     def f(a, b, *args, c, d = 42, e, **kwds):
         ...

docs/src/tutorial/numpy.rst

@@ -3,7 +3,7 @@ Working with NumPy
 =======================
 
 You can use NumPy from Cython exactly the same as in regular Python, but by
-doing so you are loosing potentially high speedups because Cython has support
+doing so you are losing potentially high speedups because Cython has support
 for fast access to NumPy arrays. Let's see how this works with a simple
 example.
 

docs/src/userguide/pyrex_differences.rst

@@ -310,7 +310,7 @@ Synonyms
 Source code encoding
 ======================
 
-.. TODO: add the links to the relevent PEPs
+.. TODO: add the links to the relevant PEPs
 
 Cython supports PEP 3120 and PEP 263, i.e. you can start your Cython source
 file with an encoding comment and generally write your source code in UTF-8.

docs/src/userguide/source_files_and_compilation.rst

@@ -26,7 +26,7 @@ platform for generating an extension module. For these options look at the
 official Python documentation.
 
 The other, and probably better, way is to use the :mod:`distutils` extension
-provided with Cython. The benifit of this method is that it will give the
+provided with Cython. The benefit of this method is that it will give the
 platform specific compilation options, acting like a stripped down autotools.