Remove QBFT consensus early access warning (#956)

Signed-off-by: Lucas Saldanha <[email protected]>

Co-authored-by: Sally MacFarlane <[email protected]>

Author: lucassaldanha

docs/Concepts/Consensus-Protocols/Overview-Consensus.md

@@ -12,11 +12,6 @@ Besu implements the following consensus protocols:
 * [Quorum IBFT 1.0](../../HowTo/Configure/Consensus-Protocols/QuorumIBFT.md) (proof of authority).
 * [QBFT](../../HowTo/Configure/Consensus-Protocols/QBFT.md) (proof of authority).
 
-!!! warning
-
-    QBFT is currently an early access feature. It is not recommended for production networks with
-    business critical impact.
-
 The `config` property in the genesis file specifies the consensus protocol for a chain.
 
 !!! example

docs/HowTo/Configure/Consensus-Protocols/QBFT.md

@@ -7,11 +7,6 @@ description: Hyperledger Besu QBFT proof of authority (PoA) consensus protocol i
 Hyperledger Besu implements the QBFT proof of authority (PoA) consensus protocol. Private networks
 can use QBFT.
 
-!!! warning
-
-    QBFT is currently an early access feature. It is not recommended for production networks with
-    business critical impact.
-
 In QBFT networks, approved accounts, known as validators, validate transactions and blocks.
 Validators take turns to create the next block. Before inserting the block onto the chain, a
 super-majority (greater than 66%) of validators must first sign the block.

docs/Tutorials/Private-Network/Create-QBFT-Network.md

@@ -4,11 +4,6 @@ description: Hyperledger Besu private network using the QBFT (proof of authority
 
 # Create a private network using the QBFT (proof of authority) consensus protocol
 
-!!! warning
-
-    QBFT is currently an early access feature. It is not recommended for production networks with
-    business critical impact.
-
 A private network provides a configurable network for testing. This private network uses the
 [QBFT (proof of authority) consensus protocol](../../HowTo/Configure/Consensus-Protocols/QBFT.md).