Author: Armin Rigo <[email protected]>
Branch:
Changeset: r3066:3dcec7271e97
Date: 2018-01-11 08:14 +0000
http://bitbucket.org/cffi/cffi/changeset/3dcec7271e97/
Log: Merged in cosmo0920/cffi/fix-typo (pull request #84)
Fix typo
diff --git a/doc/source/cdef.rst b/doc/source/cdef.rst
--- a/doc/source/cdef.rst
+++ b/doc/source/cdef.rst
@@ -701,7 +701,7 @@
-------------------------------
A few C libraries are actually hard to use correctly in a ``dlopen()``
-setting. This is because most C libraries are intented for, and tested
+setting. This is because most C libraries are intended for, and tested
with, a situation where they are *linked* with another program, using
either static linking or dynamic linking --- but from a program written
in C, at start-up, using the linker's capabilities instead of
diff --git a/doc/source/installation.rst b/doc/source/installation.rst
--- a/doc/source/installation.rst
+++ b/doc/source/installation.rst
@@ -114,7 +114,7 @@
PKG_CONFIG_PATH=/usr/local/opt/libffi/lib/pkgconfig pip install cffi
-Aternatively, **on OS/X 10.6** (Thanks Juraj Sukop for this)
+Alternatively, **on OS/X 10.6** (Thanks Juraj Sukop for this)
For building libffi you can use the default install path, but then, in
``setup.py`` you need to change::
diff --git a/doc/source/using.rst b/doc/source/using.rst
--- a/doc/source/using.rst
+++ b/doc/source/using.rst
@@ -28,7 +28,7 @@
*New in version 1.11:* in addition to ``wchar_t``, the C types
``char16_t`` and ``char32_t`` work the same but with a known fixed size.
In previous versions, this could be achieved using ``uint16_t`` and
-``int32_t`` but without automatic convertion to Python unicodes.
+``int32_t`` but without automatic conversion to Python unicodes.
Pointers, structures and arrays are more complex: they don't have an
obvious Python equivalent. Thus, they correspond to objects of type
_______________________________________________
pypy-commit mailing list
[email protected]
https://mail.python.org/mailman/listinfo/pypy-commit
