From 82716b3fdba74ae0ddf1f05b7d81b17a16b56503 Mon Sep 17 00:00:00 2001 From: "S. Matthew English" Date: Wed, 18 Jan 2017 14:02:21 +0100 Subject: [PATCH] enforcing consistency of capitalization changing outlying instances of "Notaries" to "notaries", reconciling them with the rest of the document --- docs/source/consensus.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/source/consensus.rst b/docs/source/consensus.rst index e542f25670..8ca2826622 100644 --- a/docs/source/consensus.rst +++ b/docs/source/consensus.rst @@ -46,8 +46,8 @@ Multiple notaries More than one notary can exist in the network. This gives the following benefits: -* **Custom behaviour**. We can have both validating and privacy preserving Notaries -- parties can make a choice based on their specific requirements -* **Load balancing**. Spreading the transaction load over multiple Notaries will allow higher transaction throughput in the platform overall +* **Custom behaviour**. We can have both validating and privacy preserving notaries -- parties can make a choice based on their specific requirements +* **Load balancing**. Spreading the transaction load over multiple notaries will allow higher transaction throughput in the platform overall * **Low latency**. Latency could be minimised by choosing a notary physically closer the transacting parties A transaction should only be signed by a notary if all of its input states point to it.