Docs: misc markup fixes and adjust an out of date paragraph about oracles.

docs/source/index.rst

@@ -26,7 +26,7 @@ Read on to learn:
    inthebox
    getting-set-up
    data-model
-       consensus
+   consensus
    messaging
    running-the-demos
    node-administration
@@ -36,7 +36,7 @@ Read on to learn:
    :maxdepth: 2
    :caption: Tutorials
 
-   tutorial_contract
+   tutorial-contract
    protocol-state-machines
    oracles
 

docs/source/node-administration.rst

@@ -8,7 +8,7 @@ Monitoring your node
 --------------------
 
 Like most Java servers, the node exports various useful metrics and management operations via the industry-standard
-`JMX infrastructure <https://en.wikipedia.org/wiki/Java_Management_Extensions>`_. JMX is a standard _in-process_ API
+`JMX infrastructure <https://en.wikipedia.org/wiki/Java_Management_Extensions>`_. JMX is a standard API
 for registering so-called _MBeans_ ... objects whose properties and methods are intended for server management. It does
 not require any particular network protocol for export. So this data can be exported from the node in various ways:
 some monitoring systems provide a "Java Agent", which is essentially a JVM plugin that finds all the MBeans and sends

docs/source/oracles.rst

@@ -176,11 +176,11 @@ Implementation involves the following steps:
 2. Defining a lower level service class, that binds network messages to the API.
 3. Defining a protocol using the :doc:`protocol-state-machines` framework to make it easy for a client to interact
    with the oracle.
+4. Constructing it (when advertised) in ``AbstractNode``.
 
 An example of how to do this can be found in the ``NodeInterestRates.Oracle``, ``NodeInterestRates.Service`` and
-``RateFixProtocol`` classes. The exact details of how this code works will change in future, so for now consulting
-the protocols tutorial and the code for the server-side oracles implementation will have to suffice. There will be more
-detail added once the platform APIs have settled down.
+``RateFixProtocol`` classes.
 
-Currently, there's no network map service, so the location and identity keys of an oracle must be distributed out of
-band.
+The exact details of how this code works will change in future, so for now consulting the protocols tutorial and the
+code for the server-side oracles implementation will have to suffice. There will be more detail added once the
+platform APIs have settled down.