From 20ef62656f126abd9c0951e253d837fec7106da7 Mon Sep 17 00:00:00 2001 From: Jason Rhinelander Date: Wed, 21 Sep 2016 13:39:02 -0400 Subject: [PATCH] Fix minor documentation spelling mistakes --- docs/advanced.rst | 6 +++--- docs/faq.rst | 4 ++-- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/advanced.rst b/docs/advanced.rst index d905b30d0..867e853ce 100644 --- a/docs/advanced.rst +++ b/docs/advanced.rst @@ -540,7 +540,7 @@ pybind11 provides a few convenience macros such as in the preprocessor (which has no concept of types), they *will* get confused by commas in a template argument such as ``PYBIND11_OVERLOAD(MyReturnValue, myFunc)``. In this case, the preprocessor assumes that the comma indicates -the beginnning of the next parameter. Use a ``typedef`` to bind the template to +the beginning of the next parameter. Use a ``typedef`` to bind the template to another name and use it in the macro to avoid this problem. @@ -670,7 +670,7 @@ functions: .def_readwrite("contents", &MyClass::contents); In this case, properties can be read and written in their entirety. However, an -``append`` operaton involving such a list type has no effect: +``append`` operation involving such a list type has no effect: .. code-block:: pycon @@ -1524,7 +1524,7 @@ or ``py::array::f_style``. void f(py::array_t array); The ``py::array::forcecast`` argument is the default value of the second -template paramenter, and it ensures that non-conforming arguments are converted +template parameter, and it ensures that non-conforming arguments are converted into an array satisfying the specified requirements instead of trying the next function overload. diff --git a/docs/faq.rst b/docs/faq.rst index cc4804629..538f8dcc2 100644 --- a/docs/faq.rst +++ b/docs/faq.rst @@ -121,7 +121,7 @@ can be compiled independently from another. Following this approach will 2. enable parallel builds (if desired). 3. allow for faster incremental builds. For instance, when a single class - definiton is changed, only a subset of the binding code will generally need + definition is changed, only a subset of the binding code will generally need to be recompiled. How can I create smaller binaries? @@ -131,7 +131,7 @@ To do its job, pybind11 extensively relies on a programming technique known as *template metaprogramming*, which is a way of performing computation at compile time using type information. Template metaprogamming usually instantiates code involving significant numbers of deeply nested types that are either completely -removed or reduced to just a few instrutions during the compiler's optimization +removed or reduced to just a few instructions during the compiler's optimization phase. However, due to the nested nature of these types, the resulting symbol names in the compiled extension library can be extremely long. For instance, the included test suite contains the following symbol: