chore(docs): rename to integrated consensus (#530)

Renames consensus model to "Integrated Consensus"

task: https://app.asana.com/0/1206684215872507/1206757152742609/f

docs/site/docs/learn/omni/architecture.md

@@ -18,14 +18,14 @@ At the heart of Omni's network lies the **Consensus Layer**, powered by the Come
 
 ## The Execution Layer
 
-Parallel to the Consensus Layer is the **Execution Layer**, or the Omni EVM, mirroring the Ethereum L1 execution layer's functionality. This is where users' transactions are processed, and the following features stand out:
+Additional to the Consensus Layer is the **Execution Layer**, or the Omni EVM, mirroring the Ethereum L1 execution layer's functionality. This is where users' transactions are processed, and the following features stand out:
 
 - **Scalable Transaction Processing**: The Omni EVM handles transactions in its mempool, enabling high throughput without overloading the network.
 - **Compatibility with Ethereum Clients**: Omni leverages existing Ethereum execution clients (e.g., Geth, Besu, Erigon), ensuring stability and up-to-date features.
 - **Dynamic Fee Mechanism**: Supporting [EIP-1559](https://eips.ethereum.org/EIPS/eip-1559), the Omni EVM allows for dynamic transaction fees and partial fee burning, optimizing network usage costs.
 
 ## Unifying Consensus and Execution
 
-Omni's dual-chain architecture facilitates **Parallelized Consensus**, allowing validators to simultaneously run consensus for the Omni EVM and cross-network messages. This innovative design, supported by tools like ABCI++ and the Engine API, makes Omni's sub-second finality possible. Validators efficiently attest to the state of external rollup VMs, ensuring seamless state transitions and unified state management.
+Omni's dual-chain architecture facilitates **Integrated Consensus**, allowing validators to simultaneously run consensus for the Omni EVM and cross-network messages. This innovative design, supported by tools like ABCI++ and the Engine API, makes Omni's sub-second finality possible. Validators efficiently attest to the state of external rollup VMs, ensuring seamless state transitions and unified state management.
 
 By separating consensus operations from transaction execution, Omni effectively scales activity across its network and connected rollups. This architecture not only mitigates the risk of network congestion but also enhances the security and reliability of cross-network transactions.

docs/site/docs/learn/omni/consensus.md

@@ -2,13 +2,13 @@
 sidebar_position: 7
 ---
 
-# Omni Parallelized Consensus
+# Omni Integrated Consensus
 
-Omni introduces a groundbreaking approach to blockchain consensus known as **Parallelized Consensus**. This innovative method allows the Omni network to simultaneously process consensus on its Ethereum Virtual Machine (EVM) and manage cross-chain data or messages, known as XBlocks. This dual-path consensus mechanism enhances network performance, ensuring swift and secure validation of transactions and cross-chain interactions.
+Omni introduces a groundbreaking approach to blockchain consensus known as **Integrated Consensus**. This innovative method allows the Omni network to simultaneously process consensus on its Ethereum Virtual Machine (EVM) and manage cross-chain data or messages, known as XBlocks. This dual-path consensus mechanism enhances network performance, ensuring swift and secure validation of transactions and cross-chain interactions.
 
-## How Parallelized Consensus Works
+## How Integrated Consensus Works
 
-Parallelized Consensus in Omni consists of two main sub-processes, each handling a distinct aspect of network operations:
+Integrated Consensus in Omni consists of two main sub-processes, each handling a distinct aspect of network operations:
 
 ### Omni EVM Consensus
 
@@ -27,14 +27,14 @@ Parallelized Consensus in Omni consists of two main sub-processes, each handling
 
 The combined efforts of validating Omni EVM transactions and attesting to `XBlock` hashes culminate in a unified consensus vote. If a proposed block garners approval from two-thirds of the validator set, it is finalized and added to the Omni chain. These finalized blocks encompass both the Omni EVM transactions and attested XBlock hashes, enabling full node operators of specific rollup VMs to reconstruct and verify XBlock contents.
 
-## The Significance of Parallelized Consensus
+## The Significance of Integrated Consensus
 
-Omni's Parallelized Consensus represents a significant leap forward in blockchain technology, enabling:
+Omni's Integrated Consensus represents a significant leap forward in blockchain technology, enabling:
 
 - **Efficient Processing**: By separating the consensus processes for the Omni EVM and `XBlock`s, Omni achieves rapid state transitions and block finalization.
 - **Enhanced Security and Reliability**: The dual-path consensus strengthens the network's integrity, providing robust security for both on-chain transactions and cross-chain communications.
 - **Global Scalability**: This consensus model paves the way for a scalable and interoperable blockchain ecosystem, where diverse networks can communicate and transact seamlessly.
 
-Omni's adoption of Parallelized Consensus underscores its commitment to fostering a more connected and efficient blockchain world, where the boundaries between different chains and technologies blur, creating a unified and powerful platform for decentralized applications and services.
+Omni's adoption of Integrated Consensus underscores its commitment to fostering a more connected and efficient blockchain world, where the boundaries between different chains and technologies blur, creating a unified and powerful platform for decentralized applications and services.
 
-For a deeper dive into Omni's Parallelized Consensus and its impact on blockchain interoperability, [visit the protocol section](../../protocol/introduction.md).
+For a deeper dive into Omni's Integrated Consensus and its impact on blockchain interoperability, [visit the protocol section](../../protocol/introduction.md).

docs/site/docs/protocol/architecture/components.md

@@ -47,20 +47,20 @@ Cosmos’ [ABCI++](https://docs.cometbft.com/v0.37/spec/abci/) is a supplementar
 
 During consensus, validators also use ABCI++ to attest to the state of external Rollup VMs. Omni validators run the state transition function, $f(i, S_n)$, for each Rollup VM and compute the output, $S_{n+1}$.
 
-### Parallelized Consensus & CometBFT
+### Integrated Consensus & CometBFT
 
-Omni introduces Parallelized Consensus, a consensus framework that allows validators to run consensus for the Omni EVM in parallel with consensus for cross-network messages without compromising on performance.
+Omni introduces Integrated Consensus, a consensus framework that allows validators to run consensus for the Omni EVM additional to the consensus framework for cross-network messages without compromising on performance.
 
-Omni’s Parallelized Consensus contains two sub-processes:
+Omni’s Integrated Consensus contains two sub-processes:
 
 - validating state changes within the Omni EVM and
 - attesting to `XBlock` hashes originating from external rollup VMs.
 
-The aggregate Parallelized Consensus process is visualized below.
+The aggregate Integrated Consensus process is visualized below.
 
 <figure>
-  <img src="/img/parallel-consensus.png" alt="Parallel Consensus" />
-  <figcaption>*Parallelized Consensus: Validating Omni EVM State Changes and Rollup `XBlock` Hash Attestation*</figcaption>
+  <img src="/img/integrated-consensus.png" alt="Integrated Consensus" />
+  <figcaption>*Integrated Consensus: Validating Omni EVM State Changes and Rollup `XBlock` Hash Attestation*</figcaption>
 </figure>
 
 1. Every `halo` client runs a node for each rollup VM to check for `XMsg` events emitted from Portal contracts.

docs/site/docs/protocol/introduction.md

@@ -49,7 +49,7 @@ After verifying the contents of a proposed consensus block and appending `XBlock
 
 If the proposal is determined valid by ⅔ of the active validator set, the block is finalized and becomes the latest block committed to the network. These confirmed blocks contain all transactions from the Omni EVM along with the hashes of attested `XBlock`s, allowing anyone with a validator node for a given rollup VM to reconstruct any `XBlock` and verify its contents.
 
-Omni’s [Parallelized Consensus](./architecture/components.md#parallelized-consensus--cometbft) processes state transitions for both the Omni EVM and external VMs, preventing both complementary sub-processes from interfering with one another prior to block finalization. ABCI++ allows validators to keep `XBlock` attestations separate from the single CometBFT transaction within each block.
+Omni’s [Integrated Consensus](./architecture/components.md#integrated-consensus--cometbft) processes state transitions for both the Omni EVM and external VMs, preventing both complementary sub-processes from interfering with one another prior to block finalization. ABCI++ allows validators to keep `XBlock` attestations separate from the single CometBFT transaction within each block.
 
 ## Fee Model