More markup and spelling fixes.

1 files changed, 6 insertions, 6 deletions

diff --git a/Doc/library/functions.rst b/Doc/library/functions.rst
index 9d843d9..4c06058 100644
--- a/Doc/library/functions.rst
+++ b/Doc/library/functions.rst
@@ -1050,19 +1050,19 @@ are always available.  They are listed here in alphabetical order.
    been overridden in a class. The search order is same as that used by
    :func:`getattr` except that the *type* itself is skipped.
 
-   The ``__mro__`` attribute of the *type* lists the method resolution search
-   order used by both :func:`getattr` and :func:`super`.  The attribue is
-   dynamic and can change whenever the inheritance hierarchy is updated.
+   The :attr:`__mro__` attribute of the *type* lists the method resolution
+   search order used by both :func:`getattr` and :func:`super`.  The attribute
+   is dynamic and can change whenever the inheritance hierarchy is updated.
 
    If the second argument is omitted, the super object returned is unbound.  If
    the second argument is an object, ``isinstance(obj, type)`` must be true.  If
    the second argument is a type, ``issubclass(type2, type)`` must be true (this
    is useful for classmethods).
 
-   There are two typical use cases for "super".  In a class hierarchy with
-   single inheritance, "super" can be used to refer to parent classes without
+   There are two typical use cases for *super*.  In a class hierarchy with
+   single inheritance, *super* can be used to refer to parent classes without
    naming them explicitly, thus making the code more maintainable.  This use
-   closely parallels the use of "super" in other programming languages.
+   closely parallels the use of *super* in other programming languages.
 
    The second use case is to support cooperative multiple inheritance in a
    dynamic execution environment.  This use case is unique to Python and is