Editorial mdlint and vale updates in the Concepts/Privacy dir

docs/Concepts/Privacy/Multi-Tenancy.md

@@ -1,32 +1,37 @@
+---
 description: Multi-tenancy
-<!--- END of page meta data -->
+---
 
 # Multi-tenancy
 
-By default, each participant in a privacy network uses its own Besu and Orion
-node.
+By default, each participant in a privacy network uses its own Besu and Orion node.
 
-Multi-tenancy allows multiple participants to use the same Besu and
-Orion node. Each participant is called a Tenant, and the Operator is the
-owner of the Besu and Orion node.
+Multi-tenancy allows multiple participants to use the same Besu and Orion node. Each participant is
+a _tenant_, and the operator is the _owner_ of the Besu and Orion node.
 
 !!! important
-    The Operator is responsible for [configuring multi-tenancy](../../Tutorials/Privacy/Configuring-Multi-Tenancy.md), and has 
+
+    The operator is responsible for
+    [configuring multi-tenancy](../../Tutorials/Privacy/Configuring-Multi-Tenancy.md), and has
     access to all tenant data.
-    
+
 ![Multi-tenancy](../../images/Multi-tenancy.png)
 
 !!! important
-    Ensure the multi-tenant Orion node client API is configured to allow access only by the multi-tenant Besu node. Access to your data is secured through Besu using multi-tenancy mode.
 
-    If not configured to allow access only by the multi-tenant Besu node, other
-    Orion clients including other Besu nodes may be able to access tenant data.
+    Ensure the multi-tenant Orion node client API is configured to allow access only by the
+    multi-tenant Besu node. Access to your data is secured through Besu using multi-tenancy mode.
+
+    If not configured to allow access only by the multi-tenant Besu node, other Orion clients,
+    including other Besu nodes, might be able to access tenant data.
 
-    You can [configure TLS between Besu and Orion](../TLS.md) with the [`whitelist`](https://docs.orion.pegasys.tech/en/latest/Tutorials/TLS/#clientconnectiontlsservertrust) trust mode to secure access.
+    To secure access, you can [configure TLS between Besu and Orion](../TLS.md) with the
+    [`whitelist`](https://docs.orion.pegasys.tech/en/latest/Tutorials/TLS/#clientconnectiontlsservertrust)
+    trust mode.
 
-Multi-tenancy validates that tenants are permitted to use the specified HTTP or
-Websocket JSON-RPC requests, and the tenant has access to the requested privacy
-data. Private data is segregated, and each tenant uses a JWT token for
-authentication.
+Multi-tenancy validates that tenants have permission to use the specified HTTP or Websocket
+JSON-RPC requests, and the tenant has access to the requested privacy data. There is segregation of
+private data, and each tenant uses a JWT token for authentication.
 
-The JWT token can be created [externally or internally](../../HowTo/Interact/APIs/Authentication.md).
+You can create the JWT token either 
+[externally or internally](../../HowTo/Interact/APIs/Authentication.md).

docs/Concepts/Privacy/Privacy-Groups.md

@@ -1,76 +1,88 @@
-description: Privacy
-<!--- END of page meta data -->
+---
+description: Privacy groups
+---
 
-# Privacy Groups 
+# Privacy groups
 
-A privacy group is a group of nodes identified by a unique privacy group ID by Orion. Each private transaction is 
-stored in Orion with the privacy group ID.
+A privacy group is a group of nodes identified by a unique privacy group ID by Orion. Each private
+transaction is stored in Orion with the privacy group ID.
 
-The Besu nodes maintain the public world state for the blockchain and a private state for each privacy group. 
-The private states contain data that is not shared in the globally replicated world state. 
+The Besu nodes maintain the public world state for the blockchain and a private state for each
+privacy group. The private states contain data that is not shared in the globally replicated world
+state.
 
-## Privacy Types 
+## Privacy types
 
-Besu implements two types of privacy: 
+Besu implements two types of privacy:
 
-* EEA-compliant privacy - private transactions include `privateFor` as the recipient.
-* Besu-extended privacy - private transactions include `privacyGroupId` as the recipient.
+* Enterprise Ethereum Alliance (EEA) privacy, where private transactions include `privateFor` as
+the recipient.
+* Besu-extended privacy, where private transactions include `privacyGroupId` as the recipient.
 
-Both privacy types create privacy groups and store private transactions with their privacy group in Orion. 
+Both privacy types create privacy groups and store private transactions with their privacy group in
+Orion.
 
 ![Privacy Groups](../../images/PrivacyGroups.png)
 
 !!! note
-    The Orion nodes are not shown above for clarity only.  To send private transactions, 
-    each Besu node must have an associated Orion node. 
 
-### Access between States 
+    For clarity, the Orion nodes are not shown in the previous diagram. To send private
+    transactions, each Besu node must have an associated Orion node.
+
+### Access between states
 
 A contract in a privacy group:
 
 * Can read or write to a contract in the same privacy group.
-* Can read from the public state including public contracts. 
-* Cannot access contracts from a different privacy group. 
+* Can read from the public state including public contracts.
+* Cannot access contracts from a different privacy group.
 
 A public contract cannot access a private contract.
 
-### EEA-compliant Privacy 
+### Enterprise Ethereum Alliance privacy
+
+In the privacy implementation complying with the
+[EEA Client Specification](https://entethalliance.org/technical-documents/) the group of nodes
+specified by `privateFrom` and `privateFor` form a privacy group with a unique privacy group ID
+provided by Orion.
 
-In our privacy implementation complying with the [EEA Client Specification](https://entethalliance.org/technical-documents/)
-the group of nodes specified by `privateFrom`and `privateFor` form a privacy group and are given a unique 
-privacy group ID by Orion.  
+!!! example
 
-!!! example 
-    The diagram above illustrates two privacy groups enabling: 
+    The previous diagram illustrates two privacy groups enabling:
 
-    * A, B, and C to send transactions that are private from D 
-    * A, C, and D to send transactions that are private from B 
+    * A, B, and C to send transactions that are private from D.
+    * A, C, and D to send transactions that are private from B.
 
-    Using EEA-compliant privacy, to send private transactions between A, B, and C, A initialises a contract in a private transaction with
-    B and C specified as the `privateFor` and A specified as the `privateFrom`. Initialising the contract 
-    creates a privacy group consisting of A, B, and C. For the ABC private state to remain consistent, 
-    A, B, and C must be included on transactions (as either `privateFrom` or `privateFor`) even if they are 
-    between two of the three parties.
+    Using EEA-compliant privacy, to send private transactions between A, B, and C, A initializes a
+    contract in a private transaction with B and C specified as the `privateFor` and A specified as
+    the `privateFrom`. Initializing the contract creates a privacy group consisting of A, B, and C.
+    For the ABC private state to remain consistent, A, B, and C must be included on transactions
+    (as either `privateFrom` or `privateFor`) even if they are between only two of the three
+    parties.
 
-    To send private transactions between A, C, and D, C initialises a different contract in a private transaction with
-    A and D specified as the `privateFor` and C specified as the `privateFrom`. Initialising the contract 
-    creates a privacy group consisting of  A, C, and D. For the ACD private state to remain consistent, 
-    A, C, and D must be included on transactions (as either `privateFrom` or `privateFor`) even if they are 
-    between two of the three parties.
+    To send private transactions between A, C, and D, C initializes a different contract in a
+    private transaction with A and D specified as the `privateFor` and C specified as the
+    `privateFrom`. Initializing the contract creates a privacy group consisting of  A, C, and D.
+    For the ACD private state to remain consistent, A, C, and D must be included on transactions
+    (as either `privateFrom` or `privateFor`) even if they are between only two of the three
+    parties.
 
 
-### Besu-extended Privacy 
+### Besu-extended privacy
 
-In our extended privacy implementation, a privacy group is created using [`priv_createPrivacyGroup`](../../Reference/API-Methods.md#priv_createprivacygroup)
-and private transactions sent to the privacy group ID. 
+The Besu-extended privacy implementation creates a privacy group using
+[`priv_createPrivacyGroup`](../../Reference/API-Methods.md#priv_createprivacygroup) with private
+transactions sent to the privacy group ID.
+
+!!! example
 
-!!! example 
-    Using the same privacy groups as above. 
+    Using the same privacy groups as in the previous example.
 
-    Using Besu-extended privacy, to send private transactions between A, B, and C, A creates a privacy 
-    group consisting of A, B, and C. The privacy group ID is specified when sending private transactions and 
-    A, B, and C are recipients of all private transactions sent to the privacy group. 
+    Using Besu-extended privacy, to send private transactions between A, B, and C, A creates a
+    privacy group consisting of A, B, and C. The privacy group ID is specified when sending private
+    transactions and A, B, and C are recipients of all private transactions sent to the privacy
+    group.
 
-    To send private transactions between A, C, and D, A creates a privacy group consisting of A, C, and D.
-    The privacy group ID of this group is specified when sending private transactions with A, C, and D 
-    as recipients. 
+    To send private transactions between A, C, and D, A creates a privacy group consisting of A, C,
+    and D. The privacy group ID of this group is specified when sending private transactions with A,
+    C, and D as recipients.

docs/Concepts/Privacy/Privacy-Overview.md

@@ -1,35 +1,44 @@
+---
 description: Privacy
-<!--- END of page meta data -->
+---
 
 # Privacy
 
-Privacy in Besu refers to the ability to keep transactions private between the involved participants. 
-Other participants cannot access the transaction content or list of participants.
+In Besu, privacy refers to the ability to keep transactions private between the involved
+participants. Other participants cannot access the transaction content or list of participants.
 
 !!! important
-    For production systems requiring private transactions: 
-        
-    * We recommend using a network with a consensus mechanism supporting transaction finality. For example, 
-    [IBFT 2.0](../../HowTo/Configure/Consensus-Protocols/IBFT.md).
-    * Orion must be [highly available and run in a separate instance to Besu](../../HowTo/Use-Privacy/Run-Orion-With-Besu.md).
-
-!!! important
+
+    For production systems requiring private transactions:
+
+    * It is recommended you use a network with a consensus mechanism supporting transaction
+    finality, such as [IBFT 2.0](../../HowTo/Configure/Consensus-Protocols/IBFT.md).
+    * Orion must be [highly available and run in a separate instance to Besu].
+
     Using private transactions with [pruning](../Pruning.md) is not supported.
 
-## Private Transaction Manager
+## Private transaction manager
 
-Besu uses a Private Transaction Manager to implement privacy. For example, [Orion](http://docs.orion.pegasys.tech).  
-Each Besu node that sends or receives private transactions requires an associated Orion node. 
+Besu uses a private transaction manager, [Orion](http://docs.orion.pegasys.tech), to implement
+privacy. Each Besu node sending or receiving private transactions requires an associated Orion
+node.
 
 ![Orion Nodes](../../images/OrionNodes.png)
 
-Private transactions are passed from the Besu node to the associated Orion node. The Orion node
-encrypts and directly distributes (that is, point to point) the private transaction to Orion nodes 
-participating in the transaction. 
+Private transactions pass from the Besu node to the associated Orion node. The Orion node
+encrypts and directly distributes (that is, point-to-point) the private transaction to the Orion
+nodes participating in the transaction.
+
+By default, each participant in a privacy network uses its own Besu and Orion node.
+[Multi-tenancy](Multi-Tenancy.md) allows multiple participants to use the same Besu and Orion node.
 
 By default, each participant in a privacy network uses its own Besu and Orion
 node. [Multi-tenancy](Multi-Tenancy.md) allows multiple participants to use the same Besu and Orion
 node.
 
 !!! tip
-    Private Transaction Managers are also known as Enclaves.
+
+    Private Transaction Managers are also refered to as Enclaves.
+
+<!-- Links -->
+[highly available and run in a separate instance to Besu]: ../../HowTo/Use-Privacy/Run-Orion-With-Besu.md