Week 11 exercises.

Author: dham

doc/source/11_further_object-oriented_features.rst

@@ -581,7 +581,7 @@ Exercises
 ---------
 
 Obtain the `skeleton code for these exercises from GitHub classroom
-<>`__. 
+<https://classroom.github.com/a/qTArFlxP    >`__. 
 
 .. proof:exercise::
 
@@ -596,7 +596,7 @@ Obtain the `skeleton code for these exercises from GitHub classroom
     the built-in `logging` module by calling :func:`logging.info` and passing
     the log message.
 
-    The log message should comprise the string "Calling: " followed by the
+    The log message should comprise the string `"Calling: "` followed by the
     function name (accessible using the `__name__` attribute), followed by
     round brackets containing first the :func:`repr` of the positional
     arguments, followed by the key=value pairs the keyword arguments.
@@ -606,7 +606,7 @@ Obtain the `skeleton code for these exercises from GitHub classroom
     The :mod:`groups.groups` module in the skeleton code is the new version
     introduced above, using an :term:`abstract base class`. The
     `log_decorator.log_call` :term:`decorator` has been applied to the
-    :math:`Group._validate` :term:`abstract method`. However, even once you
+    :meth:`Group._validate` :term:`abstract method`. However, even once you
     have implemented this decorator, it never gets called. Your challenge is to
     modify :mod:`groups.groups` so that the decorator is called every time a
     subclass :meth:`_validate` method is called, but **without** moving or