Merge branch 'main' into add--cryptox

Author: TinaKT

source/mainnet/net/mobile-wallet/update-baker-mw.rst

@@ -775,10 +775,12 @@ Stop validation
 ===============
 
 If you remove a validator, the node that is configured with the :term:`validator keys<private keys>` will stop producing blocks after the next :term:`pay day`.
+
 After the :term:`cool-down period`, the amount that you previously staked is returned to your disposable balance at the next pay day. When you've removed the validator,
 it is recommended that you also remove the keys from the node, but you should only do this after the node has stopped producing blocks, i.e. after the payday.
 If you want to use the node for validation at a later point in time, you'll then have to create a new set of validator keys.
 
+
 If you no longer wish to produce blocks on this account, you can stop validation.
 
 .. dropdown:: |cryptox|

source/mainnet/net/resources/glossary.rst

@@ -130,6 +130,7 @@ Also see the Concordium `Whitepaper <https://developer.concordium.software/gover
 
       A period of time during which the funds are frozen and cannot be spent.
 
+
    Concordium Byzantine Fault Tolerance (BFT) protocol
 
       The consensus protocol for the blockchain. The protocol offers high transaction throughput and lower confirmation time because a block can be produced as soon as the previous block has been signed. The protocol proceeds by rounds. In each round, a predetermined leader among the validators should produce a block. The other validators then sign this block, and their collective signatures are aggregated to form a quorum certificate (QC). This quorum certificate is then included in the next block. If the leader fails to produce a block in the round, or not enough signatures were gathered for a QC, then the validators will instead send timeout messages, which are aggregated to form a timeout certificate (TC). Each block always contains a quorum certificate and may contain a timeout certificate for the previous round if and only if the previous round timed out. When blocks on a common chain in two consecutive rounds have quorum certificates, the block in the first of these rounds (together with its ancestors) is considered final. At this point, the protocol ensures that it cannot be rolled back. The two consecutive blocks must also be within the same epoch.