+ pass "make spellcheck"

peps/pep-0757.rst

@@ -482,7 +482,7 @@ API example::
 This might work for the GMP, as it has :c:func:`!mpz_limbs_read()` and
 :c:func:`!mpz_limbs_write()` functions, that can provide required access to
 internals of :c:struct:`!mpz_t`.  Other libraries may require using temporary
-bufferes and then mpz_import/export-like functions on their side.
+buffers and then mpz_import/export-like functions on their side.
 
 The major drawback of this approach is that it's much more complex on the
 CPython side (i.e. actual conversion between different layouts).  For example,
@@ -553,7 +553,7 @@ This might look as a simplification from the API designer point of view, but
 will be less convenient for end users.  They will have to follow Python
 development, benchmark different variants for exporting small integers (is that
 obvious why above case was chosen instead of :c:func:`PyLong_AsInt64`?), maybe
-support different code paths for various CPython versions or accross different
+support different code paths for various CPython versions or across different
 Python implementations.