multi-tenancy now works with onchain groups (#527)

* multi-tenancy now works with onchain groups

Signed-off-by: Sally MacFarlane <[email protected]>

* capitalization

Signed-off-by: Sally MacFarlane <[email protected]>

Author: macfarla

docs/Concepts/Privacy/Flexible-PrivacyGroups.md

@@ -1,8 +1,8 @@
 ---
-description: Flexible Privacy Groups
+description: Flexible privacy groups
 ---
 
-# Flexible Privacy Groups
+# Flexible privacy groups
 
 Flexible privacy groups use smart contracts to store and maintain the group membership. You can add
 and remove members to and from flexible privacy groups.
@@ -16,16 +16,14 @@ and remove members to and from flexible privacy groups.
 
     Flexible privacy groups are an early access feature. Do not use in production networks.
 
-    Flexible privacy groups are not supported with [multi-tenancy](Multi-Tenancy.md).
-
     The flexible privacy group interfaces might change between releases. There might not be an
     upgrade path from flexible privacy groups created using v1.5 or earlier to enable use of flexible privacy
     group functionality in future versions.
 
     It's not recommended to create flexible privacy groups in a chain with existing
     [offchain privacy groups](Privacy-Groups.md).
 
-## Group Management Contracts
+## Group management contracts
 
 The privacy group management contract bytecode is hard-coded into Hyperledger Besu and when you
 create a privacy group, the contract bytecode is part of the genesis state of the privacy group.
@@ -42,7 +40,7 @@ and upgrade the management contract.
 The owner is identified by the signing key.  Transactions to add and remove participants, or upgrade
 the management contract, must be signed by the same key that signed the group creation transaction.
 
-## Flexible Privacy Group IDs
+## Flexible privacy group IDs
 
 When creating a flexible privacy group, generate the privacy group ID for the group outside of Besu
 and pass the ID as a parameter.

docs/HowTo/Use-Privacy/Use-FlexiblePrivacy.md

@@ -16,8 +16,6 @@ membership of [flexible privacy groups](../../Concepts/Privacy/Flexible-PrivacyG
     [Flexible privacy groups](../../Concepts/Privacy/Flexible-PrivacyGroups.md) are an early access
     feature. Do not use in production networks.
 
-    Flexible privacy groups are not supported with [multi-tenancy](../../Tutorials/Privacy/Configuring-Multi-Tenancy.md).
-
     The flexible privacy group interfaces may change between releases. There may not be an
     upgrade path from flexible privacy groups created using v1.5 or earlier to enable use of flexible privacy
     group functionality in future versions.
@@ -52,7 +50,7 @@ the [web3.js-eea library](https://github.com/PegaSysEng/web3js-eea):
 
 !!! tip
 
-    The Orion logs for Orion 1 and Orion 2 displays `PrivacyGroupNotFound` errors. This is expected
+    The Orion logs for Orion 1 and Orion 2 display `PrivacyGroupNotFound` errors. This is expected
     behavior because private transactions check offchain and onchain to find the privacy group for
     a private transaction.