Fixing md formatting sphinixification issues (#3510)

docs/source/corda-nodes-index.rst

@@ -12,5 +12,5 @@ Nodes
    clientrpc
    shell
    node-database
-   node-administration
+   node-database-access-h2
-   out-of-process-verification
+   node-administration

docs/source/design/sgx-infrastructure/design.md

@@ -10,34 +10,34 @@ Kubernetes for parts specific to that.
 
 The main idea behind the infrastructure is to provide a highly available cluster of enclave services (hosts) which can
 serve enclaves on demand. It provides an interface for enclave business logic that's agnostic with regards to the
-infrastructure, similar to [serverless architectures](details/serverless.md). The enclaves will use an opaque reference
+infrastructure, similar to serverless architectures. The enclaves will use an opaque reference
-to other enclaves or services in the form of [enclave channels](details/channels.md). Channels hides attestation details
+to other enclaves or services in the form of enclave channels. Channels hides attestation details
 and provide a loose coupling between enclave/non-enclave functionality and specific enclave images/services implementing
 it. This loose coupling allows easier upgrade of enclaves, relaxed trust (whitelisting), dynamic deployment, and
 horizontal scaling as we can spin up enclaves dynamically on demand when a channel is requested.
 
+For more information see:
+
+.. toctree::
+   :maxdepth: 1
+   
+   details/serverless.md
+   details/channels.md
+   
 ## Infrastructure components
 
 Here are the major components of the infrastructure. Note that this doesn't include business logic specific
 infrastructure pieces (like ORAM blob storage for Corda privacy model integration).
 
-* [**Distributed key-value store**](details/kv-store.md):
+.. toctree::
-  Responsible for maintaining metadata about enclaves, hosts, sealed secrets and CPU locality.
+   :maxdepth: 1
-  
+   
-* [**Discovery service**](details/discovery.md)
+   details/kv-store.md
-  Responsible for resolving an enclave channel to a specific enclave image and a host that can serve it using the
+   details/discovery.md
-  metadata in the key-value store.
+   details/host.md
-
+   details/enclave-storage.md
-* [**Enclave host**](details/host.md):
+   details/ias-proxy.md
-  This is a service capable of serving enclaves and driving the underlying traffic. Third party components like Intel's
+   
-  SGX driver and aesmd also belong here.
-
-* [**Enclave storage**](details/enclave-storage.md):
-  Responsible for serving enclave images to hosts. This is a simple static content server.
-
-* [**IAS proxy**](details/ias-proxy.md):
-  This is an unfortunate necessity because of Intel's requirement to do mutual TLS with their services.
-
 ## Infrastructure interactions
 
 * **Enclave deployment**:
@@ -54,17 +54,23 @@ infrastructure pieces (like ORAM blob storage for Corda privacy model integratio
 
 ## Decisions to be made
 
-* [**Strategic roadmap**](decisions/roadmap.md)
+.. toctree::
-* [**CPU certification method**](decisions/certification.md)
+   :maxdepth: 1
-* [**Enclave language of choice**](decisions/enclave-language.md)
+   
-* [**Key-value store**](decisions/kv-store.md)
+   decisions/roadmap.md
+   decisions/certification.md
+   decisions/enclave-language.md
+   decisions/kv-store.md
 
 ## Further details
 
-* [**Attestation**](details/attestation.md)
+.. toctree::
-* [**Calendar time for data at rest**](details/time.md)
+   :maxdepth: 1
-* [**Enclave deployment**](details/enclave-deployment.md)
+   
-
+   details/attestation.md
+   details/time.md
+   details/enclave-deployment.md
+   
 ## Example deployment
 
 This is an example of how two Corda parties may use the above infrastructure. In this example R3 is hosting the IAS 
@@ -75,4 +81,4 @@ the enclave image store (although R3 will need to have a repository of the signe
 We may also decide to go the other way and have R3 host the enclave hosts and the discovery service, shared between
 parties (if e.g. they don't have access to/want to maintain SGX capable boxes).
 
-![Example SGX deployment](Example%20SGX%20deployment.png)
+![Example SGX deployment](ExampleSGXdeployment.png)

docs/source/index.rst

@@ -78,6 +78,7 @@ We look forward to seeing what you can do with Corda!
       design/kafka-notary/design.md
       design/monitoring-management/design.md
       design/sgx-integration/design.md
+      design/sgx-infrastructure/design.md
 
    .. toctree::
       :caption: Participate

docs/source/serialization-index.rst

@@ -2,7 +2,6 @@ Serialization
 =============
 
 .. toctree::
-
    :caption: Other docs
    :maxdepth: 1