fix: validator and bridge operator activity

docs/basics/roles.md

@@ -42,22 +42,15 @@ The validators are selected using Delegated Proof of Stake (DPoS). Beside the 12
 Validators are in charge of the following:
 
 * Generating blocks.
-* Operating a validator node.
-* Operating a governor (Governing Validators only).
+* Governing the chain (Governing Validators only).
 
 #### Block generation
 
-Whenever a block is generated, the next validator has to validate incoming transactions and generate a new block.
-
-The block generated by the designated validator has a larger difficult weight. If the designated validator can not produce a block, the other validators generate a new block. In this case, that block has a smaller difficult weight. These difficult weights help nodes have additional facilities to reorganize in case the chain is forked.
-
-#### Validator node operation
-
-Validators operate a validator node and keep the node's software up to date.
+Validators, elected by token holders, run nodes to generate blocks according to a fixed schedule. Each validator is responsible for validating transactions and generating a block during their designated slot. If a validator fails to produce a block, the next validator in the schedule will produce the following block. This process helps maintain the integrity and continuity of the blockchain
 
 #### Chain governance
 
-Governing Validators can propose and vote for changes, such as adding or removing Governing Validators, upgrading smart contracts, and changing thresholds.
+Governing Validators propose and vote for changes, such as adding or removing Governing Validators, upgrading smart contracts, and changing thresholds.
 
 ### Slashing penalties for validators
 
@@ -69,22 +62,22 @@ A bridge operator is someone who runs a *bridge node* to listen for and approve
 
 ### Bridge operator selection
 
-There are 22 bridge operators, which are added or removed through proposals approved by the other operators in the set.
+The initial set of bridge operators was defined according to [REP-0002](https://github.com/axieinfinity/REPs/blob/main/REP-0002/REP-0002.md#bridge-operator-selection). Subsequently, new operators are added and existing ones removed through proposals that receive approval from the incumbent operators.
 
 ### Bridge operator responsibilities
 
 Bridge operators are in charge of the following:
 
-* Approving deposit and withdrawal events between Ronin and Ethereum through operating a bridge node.
+* Listen for deposit and withdrawal events on the bridge.
 * Managing the set of bridge operators and updating token withdrawal thresholds through governance.
 
-#### Bridge node operation
+#### Acknowledging events
 
-Bridge operators run a bridge node for acknowledging any withdrawal and deposit events between the Ronin chain and Ethereum.
+Bridge operators run a bridge node for acknowledging any withdrawal and deposit events between the Ronin and Ethereum chains.
 
 #### Bridge governance
 
-Bridge operators can propose and vote on changes to Ronin Bridge through a governance process. All bridge operators have the same voting power. Any operator can create a proposal to add a new operator, remove an existing operator, map a new token, or pause the bridge. A proposal is executed if it gets approved by 70% of the operators.
+Bridge operators propose and vote on changes to Ronin Bridge through a governance process. All bridge operators have the same voting power. Any operator can create a proposal to add a new operator, remove an existing operator, map a new token, or pause the bridge. A proposal is executed if it gets approved by 70% of the operators.
 
 ### Slashing penalties for bridge operators