Fix assorted docs warnings

Author: jerith

docs/applications/turn_channels_api.rst

@@ -1,11 +1,13 @@
 Turn Channels API (EXPERIMENTAL: DO NOT USE IN PRODUCTION)
--------------------
+----------------------------------------------------------
 
 This application provides bidirectional messaging over HTTP, intended
 for integration with `Turn's Channels API <https://whatsapp.turn.io/docs/api/channel_api>`_.
 
 Currently this only supports text message types. A future iteration will support other types.
 
+.. py:currentmodule:: vumi2.applications.turn_channels_api
+
 Configuration
 ^^^^^^^^^^^^^
 
@@ -143,17 +145,17 @@ Inbound messages that are ``POST``\ed to :py:data:`turn_api_url`/messages have t
 .. http:post:: /<turn_api_url>/messages
 
    :<json dict contact: Information about the contact who sent the message.
-    :<json str contact.id: The Turn contact ID, which is an MSISDN.
-    :<json dict contact.profile: The contact's profile information.
-        :<json str contact.profile.name: The contact's name.
+   :<json str contact.id: The Turn contact ID, which is an MSISDN.
+   :<json dict contact.profile: The contact's profile information.
+   :<json str contact.profile.name: The contact's name.
 
    :<json dict message: The message received from the user.
-    :<json str message.type: The type of message. Currently only ``text`` is supported.
-    :<json dict message.text: Required when message type is ``text``.
-        :<json str message.text.body: The text content of the message.
-    :<json str message.from: The user ID as an MSISDN. A Channel can respond to a user using this ID.
-    :<json str message.id: The ID for the message that was received by the Channel.
-    :<json int message.timestamp: Unix timestamp indicating when the message was received from the user.
+   :<json str message.type: The type of message. Currently only ``text`` is supported.
+   :<json dict message.text: Required when message type is ``text``.
+   :<json str message.text.body: The text content of the message.
+   :<json str message.from: The user ID as an MSISDN. A Channel can respond to a user using this ID.
+   :<json str message.id: The ID for the message that was received by the Channel.
+   :<json int message.timestamp: Unix timestamp indicating when the message was received from the user.
 
 **Example response**:
 
@@ -224,4 +226,4 @@ A in-memory cache that stores the last inbound message for each user. This is us
 In memory state cache
 """""""""""""""""""""
 
-See `Message Caches <../message_caches.rst>`_ for more information.
+See `Message Caches <../message_caches.rst>`_ for more information.

docs/config.rst

@@ -8,6 +8,8 @@ the previous layer. These layers are, in order of highest to lowest priority:
 #. :ref:`environment-variables`
 #. :ref:`configuration-file`
 
+.. py:currentmodule:: vumi2.config
+
 .. _base-worker-configuration:
 
 Base worker configuration

docs/message_caches.rst

@@ -3,6 +3,8 @@ Message Caches
 
 A message cache will store messages and events to be retrieved at a later stage. Currently it's only being used for the :ref:`to-address-router`, to store outbound messages to reference at a later stage, to route events.
 
+.. py:currentmodule:: vumi2.message_caches
+
 .. _memory-message-cache:
 
 Memory Message Cache

docs/routers.rst

@@ -4,6 +4,8 @@ Routers
 Routers manage moving messages between transports and applications according to a
 specified set of rules.
 
+.. py:currentmodule:: vumi2.routers
+
 .. _to-address-router:
 
 To address router

docs/transports/smpp.rst

@@ -4,15 +4,14 @@ This transport is an `SMPP 3.4`_ client, mostly used for SMS.
 
 .. _SMPP 3.4: https://support.nowsms.com/discus/messages/1/SMPP_v3_4_Issue1_2-24857.pdf
 
+.. py:currentmodule:: vumi2.transports.smpp
 
 Configuration
 ^^^^^^^^^^^^^
 The transport has the following configuration options:
 
 All the configuration items from the base worker, which you can find at :ref:`base-worker-configuration`
 
-.. py:currentmodule:: vumi2.transports.smpp
-
 .. py:data:: transport_name
    :type: str