Python 3.4.0rc1 release: Updated pydoc topics, fixed suspicious markup errors.
diff --git a/Doc/library/asyncio-eventloop.rst b/Doc/library/asyncio-eventloop.rst
index 3955f72..c9721b4 100644
--- a/Doc/library/asyncio-eventloop.rst
+++ b/Doc/library/asyncio-eventloop.rst
@@ -77,7 +77,7 @@
Create and return a new event loop object according to this policy's rules.
If there's need to set this loop as the event loop of the current context,
- :meth`set_event_loop` must be called explicitly.
+ :meth:`set_event_loop` must be called explicitly.
Access to the global loop policy
--------------------------------
diff --git a/Doc/library/enum.rst b/Doc/library/enum.rst
index 7f800e3..bce4966 100644
--- a/Doc/library/enum.rst
+++ b/Doc/library/enum.rst
@@ -30,7 +30,7 @@
.. class:: Enum
Base class for creating enumerated constants. See section
- :ref:`Functional API` for an alternate construction syntax.
+ `Functional API`_ for an alternate construction syntax.
.. class:: IntEnum
@@ -421,7 +421,7 @@
>>> Animals = Enum('Animals', 'ant bee cat dog', module=__name__)
The new pickle protocol 4 also, in some circumstances, relies on
-:attr:``__qualname__`` being set to the location where pickle will be able
+:attr:`__qualname__` being set to the location where pickle will be able
to find the class. For example, if the class was made available in class
SomeData in the global scope::
diff --git a/Doc/library/unittest.rst b/Doc/library/unittest.rst
index eea21d3..6ec3609 100644
--- a/Doc/library/unittest.rst
+++ b/Doc/library/unittest.rst
@@ -1917,13 +1917,13 @@
By default this runner shows :exc:`DeprecationWarning`,
:exc:`PendingDeprecationWarning`, :exc:`ResourceWarning` and
- :exc:`ImportWarning` even if they are :ref:`ignored by default <warning-
- ignored>`. Deprecation warnings caused by :ref:`deprecated unittest methods
- <deprecated-aliases>` are also special-cased and, when the warning filters
- are ``'default'`` or ``'always'``, they will appear only once per-module, in
- order to avoid too many warning messages. This behavior can be overridden
- using the :option:`-Wd` or :option:`-Wa` options and leaving *warnings* to
- ``None``.
+ :exc:`ImportWarning` even if they are :ref:`ignored by default
+ <warning-ignored>`. Deprecation warnings caused by :ref:`deprecated unittest
+ methods <deprecated-aliases>` are also special-cased and, when the warning
+ filters are ``'default'`` or ``'always'``, they will appear only once
+ per-module, in order to avoid too many warning messages. This behavior can
+ be overridden using the :option:`-Wd` or :option:`-Wa` options and leaving
+ *warnings* to ``None``.
.. versionchanged:: 3.2
Added the ``warnings`` argument.
diff --git a/Doc/whatsnew/3.4.rst b/Doc/whatsnew/3.4.rst
index dcd9284..faa35f0 100644
--- a/Doc/whatsnew/3.4.rst
+++ b/Doc/whatsnew/3.4.rst
@@ -1708,7 +1708,7 @@
Changes in the C API
--------------------
-* :c:func:`PyEval_EvalFrameEx`, :c:func:`PyObject_Repr(), and
+* :c:func:`PyEval_EvalFrameEx`, :c:func:`PyObject_Repr`, and
:c:func:`PyObject_Str`, along with some other internal C APIs, now include
a debugging assertion that ensures they are not used in situations where
they may silently discard a currently active exception. In cases where