[Python-checkins] cpython (2.7): Doc: fix default role usage (except in unittest mock docs)

Thu Oct 30 22:27:18 CET 2014

https://hg.python.org/cpython/rev/697c9d778fca
changeset: 93268:697c9d778fca
branch: 2.7
parent: 93264:263395345aa7
user: Georg Brandl <georg at python.org>
date: Thu Oct 30 22:26:26 2014 +0100
summary:
 Doc: fix default role usage (except in unittest mock docs)
files:
 Doc/howto/pyporting.rst | 2 +-
 Doc/library/ctypes.rst | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/Doc/howto/pyporting.rst b/Doc/howto/pyporting.rst
--- a/Doc/howto/pyporting.rst
+++ b/Doc/howto/pyporting.rst
@@ -535,7 +535,7 @@
 '''''''''''''''''''''''''''''''''''''''''''''
 
 With Python 2, when ``map`` was given more than one input sequence it would pad
-the shorter sequences with `None` values, returning a sequence as long as the
+the shorter sequences with ``None`` values, returning a sequence as long as the
 longest input sequence.
 
 With Python 3, if the input sequences to ``map`` are of unequal length, ``map``
diff --git a/Doc/library/ctypes.rst b/Doc/library/ctypes.rst
--- a/Doc/library/ctypes.rst
+++ b/Doc/library/ctypes.rst
@@ -1090,7 +1090,7 @@
 outside of Python's control (e.g. by the foreign code that calls the
 callback), ctypes creates a new dummy Python thread on every invocation. This
 behavior is correct for most purposes, but it means that values stored with
- `threading.local` will *not* survive across different callbacks, even when
+ :class:`threading.local` will *not* survive across different callbacks, even when
 those calls are made from the same C thread.
 
 .. _ctypes-accessing-values-exported-from-dlls:
-- 
Repository URL: https://hg.python.org/cpython
