Merge pull request #2158 from luzpaz/misc-typos

Misc. typos

Cython/Debugger/libcython.py

@@ -900,7 +900,7 @@ class CythonInfo(CythonBase, libpython.PythonInfo):
 
     def lineno(self, frame):
         # Take care of the Python and Cython levels. We need to care for both
-        # as we can't simply dispath to 'py-step', since that would work for
+        # as we can't simply dispatch to 'py-step', since that would work for
         # stepping through Python code, but it would not step back into Cython-
         # related code. The C level should be dispatched to the 'step' command.
         if self.is_cython_function(frame):

Cython/Utility/MemoryView.pyx

@@ -543,7 +543,7 @@ cdef class memoryview(object):
 
     __pyx_getbuffer = capsule(<void *> &__pyx_memoryview_getbuffer, "getbuffer(obj, view, flags)")
 
-    # Some properties that have the same sematics as in NumPy
+    # Some properties that have the same semantics as in NumPy
     @property
     def T(self):
         cdef _memoryviewslice result = memoryview_copy(self)

Demos/benchmarks/bpnn3.py

@@ -41,7 +41,7 @@ class NN(object):
         # create weights
         self.wi = makeMatrix(self.ni, self.nh)
         self.wo = makeMatrix(self.nh, self.no)
-        # set them to random vaules
+        # set them to random values
         for i in range(self.ni):
             for j in range(self.nh):
                 self.wi[i][j] = rand(-2.0, 2.0)

docs/src/quickstart/cythonize.rst

@@ -147,7 +147,7 @@ of ``f`` is known to be a C double.)  A notable exception, however, is
 that an overflow would not occur (and so falls back to ``object`` in case
 Python's bignums are needed).  To allow inference of C integer types, set the
 ``infer_types`` :ref:`directive <compiler-directives>` to ``True``. This directive
-does a work similar to the ``auto`` keyword in C++ for the readers who are familliar
+does a work similar to the ``auto`` keyword in C++ for the readers who are familiar
 with this language feature. It can be of great help to cut down on the need to type
 everything, but it also can lead to surprises. Especially if one isn't familiar with
 arithmetic expressions with c types. A quick overview of those

tests/run/__getattribute_subclasses__.pyx

@@ -208,7 +208,7 @@ cdef class boring_boring_getattr(boring_getattr):
 cdef class getattribute_boring_boring_getattr(boring_boring_getattr):
     """
     __getattribute__ is always tried first, then __getattr__, regardless of where
-    in the inheritance hiarchy they came from.
+    in the inheritance hierarchy they came from.
 
     >>> a = getattribute_boring_boring_getattr()
     >>> (a.getattr_called, a.getattribute_called)
@@ -253,7 +253,7 @@ cdef class getattribute_boring_boring_getattr(boring_boring_getattr):
 cdef class getattr_boring_boring_getattribute(boring_boring_getattribute):
     """
     __getattribute__ is always tried first, then __getattr__, regardless of where
-    in the inheritance hiarchy they came from.
+    in the inheritance hierarchy they came from.
 
     >>> a = getattr_boring_boring_getattribute()
     >>> (a.getattr_called, a.getattribute_called)