Fixing the spelling of "writeable" to "writable", particularly PyBUF_WRITEABLE.

2 files changed, 2 insertions, 2 deletions

diff --git a/Doc/c-api/abstract.rst b/Doc/c-api/abstract.rst
index 44bd579..515150d 100644
--- a/Doc/c-api/abstract.rst
+++ b/Doc/c-api/abstract.rst
@@ -944,7 +944,7 @@ Buffer Protocol
 
 .. cfunction:: int PyObject_AsWriteBuffer(PyObject *obj, void **buffer, Py_ssize_t *buffer_len)
 
-   Returns a pointer to a writeable memory location.  The *obj* argument must
+   Returns a pointer to a writable memory location.  The *obj* argument must
    support the single-segment, character buffer interface.  On success, returns
    ``0``, sets *buffer* to the memory location and *buffer_len* to the buffer
    length.  Returns ``-1`` and sets a :exc:`TypeError` on error.
diff --git a/Doc/c-api/concrete.rst b/Doc/c-api/concrete.rst
index 8d913ca..ba41fc5 100644
--- a/Doc/c-api/concrete.rst
+++ b/Doc/c-api/concrete.rst
@@ -1882,7 +1882,7 @@ could be used to pass around structured data in its native, in-memory format.
 
    Return a new writable buffer object.  Parameters and exceptions are similar to
    those for :cfunc:`PyBuffer_FromObject`.  If the *base* object does not export
-   the writeable buffer protocol, then :exc:`TypeError` is raised.
+   the writable buffer protocol, then :exc:`TypeError` is raised.
 
 
 .. cfunction:: PyObject* PyBuffer_FromMemory(void *ptr, Py_ssize_t size)