Adjust function pairs.

Author: ZeroIntensity

peps/pep-0788.rst

@@ -277,8 +277,8 @@ beyond repair. In turn, this PEP intends to completely deprecate the existing
 is rejected, all of the APIs can be replaced with more correct ``PyThreadState``
 functions in the current C API:
 
-- :c:func:`PyGILState_Ensure`: :c:func:`PyThreadState_Swap` / :c:func:`PyThreadState_New`
-- :c:func:`PyGILState_Release`: :c:func:`PyThreadState_Clear` / :c:func:`PyThreadState_Delete`
+- :c:func:`PyGILState_Ensure`: :c:func:`PyThreadState_Swap` & :c:func:`PyThreadState_New`
+- :c:func:`PyGILState_Release`: :c:func:`PyThreadState_Clear` & :c:func:`PyThreadState_Delete`
 - :c:func:`PyGILState_GetThisThreadState`: :c:func:`PyThreadState_Get`
 - :c:func:`PyGILState_Check`: ``PyThreadState_GetUnchecked() != NULL``
 
@@ -767,7 +767,7 @@ make the ownership and lifetime of the thread state clearer:
 This was ultimately rejected for two reasons:
 
 -  The proposed API has closer usage to
-   :c:func:`PyGILState_Ensure` / :c:func:`PyGILState_Release`, which helps
+   :c:func:`PyGILState_Ensure` & :c:func:`PyGILState_Release`, which helps
    ease the transition for old codebases.
 -  It's `significantly easier <https://discuss.python.org/t/83959/15>`_
    for code-generators like Cython to use, as there isn't any additional