added linea-besu and sequencer into docs

docs/architecture/evm-state-manager/index.mdx

@@ -21,9 +21,9 @@ The state of every account in the zkEVM is represented by a hash: a unique, encr
 
 The relationship between accounts–which accounts control which ones, for example–is represented by a tree structure. The way a small twig is derived from a larger branch, and that from a trunk: in this way, the entire bifurcating, iterative history of the network state is retained.
 
-zkBesu uses a particular version of this technology called a Sparse Merkle Tree: it uses default values to represent certain levels of branching in the tree–and if there has been no change to that default value, it means there has been no activity “further out the branch”, and therefore no need to store data regarding it. This allows the network to be much more efficient, at the level of data storage and other improvements based on that, than other implementations of Merkle trees.
+linea-besu uses a particular version of this technology called a Sparse Merkle Tree: it uses default values to represent certain levels of branching in the tree–and if there has been no change to that default value, it means there has been no activity “further out the branch”, and therefore no need to store data regarding it. This allows the network to be much more efficient, at the level of data storage and other improvements based on that, than other implementations of Merkle trees.
 
-The state manager in zkBesu is relatively simple, and has two main functions: updating the state of the network, and proof generation.
+The state manager in linea-besu is relatively simple, and has two main functions: updating the state of the network, and proof generation.
 
 - The sequencer executes a block, and sends it not only to the trace generator for it to do its job, but also to the state manager. Upon receiving an executed block from the sequencer, the state manager updates the state, in the Merkle tree, of every account that was affected, as documented in the trace data.
 - The new values, represented by new hashes, are now the state of the network following that block.

docs/architecture/network-data.md

@@ -22,7 +22,7 @@ By leveraging the expertise and resources of Infura, Consensys, and the Ethereum
 #### Client-facing RPC-API nodes
 
 - These nodes do the “traditional” work of EVM nodes: on the one hand, they are receiving updated network state information from the sequencer and state manager, and providing information about that state to users and dapps when they request it. On the other, they are receiving incoming transactions.
-- All that traffic means that Infura is running them behind a load balancer, and bringing their expertise in scaling blockchain networks across the operation. Those transactions submitted by users are therefore balanced across the nodes, and are thereby routed into the memory pool, for subsequent ingestion and processing by the Coordinator and sequencer in zkBesu.
+- All that traffic means that Infura is running them behind a load balancer, and bringing their expertise in scaling blockchain networks across the operation. Those transactions submitted by users are therefore balanced across the nodes, and are thereby routed into the memory pool, for subsequent ingestion and processing by the Coordinator and sequencer in linea-besu.
 
 #### Archive Nodes
 

docs/architecture/sequencer/index.mdx

@@ -15,6 +15,6 @@ The sequencer does a number of things: - Determines the order–the _sequence_
 
 ### How does it do it?
 
-Currently, Linea’s execution client is zkGeth, a version of geth that has been modified to work with zk-proving technology. However, Linea is building **zkBesu**: leveraging the full power of the Consensys stack by using the same Besu client software that is used to execute blocks on Ethereum coupled with a plugin system.  Besu will help the Linea stack with compatibility, reliability, ease of maintenance, and of course will help the Linea team ensure compatibility, stability, ease of maintenance in their client, and of course helps them get their network launched much faster than building from scratch.
+Currently, Linea’s execution client is zkGeth, a version of geth that has been modified to work with zk-proving technology. However, Linea is building **linea-besu**: leveraging the full power of the Consensys stack by using the same Besu client software that is used to execute blocks on Ethereum coupled with a plugin system.  Lines-besu will help the Linea stack with compatibility, reliability, ease of maintenance, and of course will help the Linea team ensure compatibility, stability, ease of maintenance in their client, and of course helps them get their network launched much faster than building from scratch.
 
 Linea's sequencer takes transactions from the Linea memory pool, and builds them into blocks, just like Besu does on mainnet Ethereum. However, on Linea, it also does a bit of extra work, and communication, with the Coordinator, to ensure that blocks are made in such a way that they can be proven by the zero-knowledge prover, and that they are as compact as possible–doubly important in a situation where all data has to be written in tiny, costly pieces on Ethereum Mainnet. This is done specifically by subsystems within the Sequencer: the Traces Generator and Conflator.

docs/architecture/trace-expansion-proving/index.mdx

@@ -11,7 +11,7 @@ The module responsible for generating the final set of data for a zero-knowledge
 
 ### What does it do?
 
-It receives several sets of information from the Coordinator and zkBesu, and produces a succinct, non-interactive argument of knowledge, or **zkSNARK**.
+It receives several sets of information from the Coordinator and linea-besu, and produces a succinct, non-interactive argument of knowledge, or **zkSNARK**.
 
 ### How does it do it?
 

docs/build-on-linea/run-a-node.mdx

@@ -13,7 +13,7 @@ If you're unfamiliar with how public blockchain networks share the responsibilit
 
 :::note
 
- Running a validator node is currently not possible. The Ethereum client being used in this walkthrough (Geth) will soon be
+ Running a sequencer node is currently not possible. The Ethereum client being used in this walkthrough (Geth) will soon be
   updated, including breaking changes. Please get in touch to make sure we keep
   you posted if you decide to run a node. ** You can run a Dockerized
   version as long as you keep the same parameters.**

docs/build-on-linea/tooling/cross-chain/axelar.md

@@ -4,7 +4,7 @@ title: Axelar Network
 
 # Axelar Network
 
-The [Axelar Network](https://docs.axelar.dev/), is a blockchain of blockchains that allows for universal web3 interoperability. By integrating with Axelar, your Linea based application now has access to the [45+ chains](https://axelarscan.io/) that are also connected via Axelar. As Axelar is a blockchain of blockchains it overcomes many of the challenges of more centralized interoperability solutions. Transactions that go through the Axelar network cannot be censored by any oracle, relayer, or validator.
+The [Axelar Network](https://docs.axelar.dev/), is a blockchain of blockchains that allows for universal web3 interoperability. By integrating with Axelar, your Linea based application now has access to the [45+ chains](https://axelarscan.io/) that are also connected via Axelar. As Axelar is a blockchain of blockchains it overcomes many of the challenges of more centralized interoperability solutions. Transactions that go through the Axelar network cannot be censored by any oracle, relayer, or sequencer.
 
 ## Available Functionality