update removed 'Plasma' mentions

Author: EmpieichO

docs/pos/concepts/tokens/pol.md

@@ -68,9 +68,9 @@ Yes, the migration contract includes a feature known as "unmigration." This allo
 
 ## Bridging mechanisms
 
-### How does the modified Plasma Bridge function?
+### How does the modified Bridge function?
 
-The Plasma Bridge will undergo modifications, with community approval, to change the native token of Polygon PoS to the new POL token. Specifically, the following changes are being proposed:
+The Bridge will undergo modifications, with community approval, to change the native token of Polygon PoS to the new POL token. Specifically, the following changes are being proposed:
 
 - Bridging POL to Polygon PoS: if you bridge POL tokens to Polygon PoS, you will receive
 an equal amount of native tokens (POL) on Polygon PoS.

docs/pos/index.md

@@ -1,7 +1,7 @@
 <div class="flex-figure" markdown="1">
 <div class="flex-figure-left" markdown="1">
 # Polygon PoS
-Polygon PoS is an EVM-compatible, hybrid plasma proof-of-stake sidechain for Ethereum, with high throughput and low costs.
+Polygon PoS is an EVM-compatible, proof-of-stake sidechain for Ethereum, with high throughput and low costs.
 </div>
 <div class="flex-figure-right">
 <img src="../img/pos/pos.svg" class="figure figure-right" alt="" />

docs/pos/overview.md

@@ -1,4 +1,4 @@
-The Polygon Proof-of-Stake (PoS) network, originally launched as Matic Network in June 2020, has been upgraded a number of times since inception. Initially designed to scale Ethereum through a hybrid plasma sidechain, a new discussion on the Polygon forum proposes upgrading Polygon PoS into a zero-knowledge (ZK)-based validium on Ethereum.
+The Polygon Proof-of-Stake (PoS) network, originally launched as Matic Network in June 2020, has been upgraded a number of times since inception. Initially designed to scale Ethereum through a sidechain, a new discussion on the Polygon forum proposes upgrading Polygon PoS into a zero-knowledge (ZK)-based validium on Ethereum.
 
 If passed, Polygon PoS would adopt the execution environment of Polygon zkEVM along with a dedicated data availability layer. The new architecture would be inherently interoperable, through an in-development interop-layer, with a broader network of ZK-powered Layer 2 (L2) chains on Ethereum. 
 
@@ -9,28 +9,27 @@ Polygon PoS will continue to be foundational infrastructure for a wide array of
 The following cyclical workflow outlines the operational mechanics of today's Polygon PoS architecture:
 
 1. **User initiates transaction**: On the Polygon PoS chain, typically via a smart contract function call.
-2. **Validation by public plasma checkpoint nodes**: These nodes validate the transaction against the Polygon chain's current state.
+2. **Validation by public checkpoint nodes**: These nodes validate the transaction against the Polygon chain's current state.
 3. **Checkpoint creation and submission**: A checkpoint of the validated transactions is created and submitted to the core contracts on the Ethereum mainnet.
 4. **Verification by core contracts**: Core contracts verify the checkpoint's validity, with the added security of fraud proofs. 
 5. **Transaction execution**: Upon successful verification, the transaction is executed and state changes are committed to the Polygon sidechain.
-6. **Asset transfer (optional)**: If needed, assets can be transferred back to the Ethereum mainnet via the Plasma Exit Queue in the core contracts.
+6. **Asset transfer (optional)**: If needed, assets can be transferred back to the Ethereum mainnet via the Exit Queue in the core contracts.
 7. **Cycle reiteration**: The process can be initiated again by the user, returning to step 1.
 
 
 ## Core contracts on Ethereum 
 
 Ethereum serves as the foundational layer upon which Polygon's PoS architecture is built. Within the Ethereum ecosystem, a set of core contracts play an important role connecting Polygon PoS to Ethereum. These core contracts are responsible for a range of functionalities, from anchoring the Polygon chain to handling asset transfers.
 
-The core contracts on the Ethereum mainnet incorporate two key features for security and functionality: fraud proofs and the Plasma Exit Queue. Fraud proofs act as a security layer, enabling the validation of transactions and state changes to ensure transparency and security across operations. The Plasma Exit Queue manages the safe and efficient transfer of assets back to the Ethereum mainnet, allowing users to seamlessly move assets between the Polygon PoS chain and Ethereum without compromising data integrity or security.
+The core contracts on the Ethereum mainnet incorporate two key features for security and functionality: fraud proofs and the Exit Queue. Fraud proofs act as a security layer, enabling the validation of transactions and state changes to ensure transparency and security across operations. The Exit Queue manages the safe and efficient transfer of assets back to the Ethereum mainnet, allowing users to seamlessly move assets between the Polygon PoS chain and Ethereum without compromising data integrity or security.
 
 
-## Public plasma checkpoint nodes
+## Public checkpoint nodes
 
-Public plasma checkpoint nodes serve as validators in the Polygon PoS architecture. They perform two primary functions: transaction validation and checkpoint submission. When a transaction is initiated on the Polygon PoS chain, these nodes validate the transaction against the current state of the Polygon chain. After validating a set number of transactions, these nodes create a Merkle root of the transaction hashes, known as a "checkpoint," and submit it to the core contracts on the Ethereum mainnet.
+Public checkpoint nodes serve as validators in the Polygon PoS architecture. They perform two primary functions: transaction validation and checkpoint submission. When a transaction is initiated on the Polygon PoS chain, these nodes validate the transaction against the current state of the Polygon chain. After validating a set number of transactions, these nodes create a Merkle root of the transaction hashes, known as a "checkpoint," and submit it to the core contracts on the Ethereum mainnet.
 
 The role of these nodes is crucial as they act as a bridge between the Ethereum mainnet and the Polygon PoS chain. They ensure data integrity and security by submitting cryptographic proofs to the core contracts on Ethereum.
 
-
 ## Polygon sidechain
 
-The Polygon sidechain is where transaction processing occurs. Unlike the Ethereum mainnet, which can get congested and has higher transaction costs, the sidechain offers a more scalable and cost-effective solution. The blocks in the sidechain are validated by the public plasma checkpoint nodes and are organized in a manner that allows for high throughput and low latency.
+The Polygon sidechain is where transaction processing occurs. Unlike the Ethereum mainnet, which can get congested and has higher transaction costs, the sidechain offers a more scalable and cost-effective solution. The blocks in the sidechain are validated by the public checkpoint nodes and are organized in a manner that allows for high throughput and low latency.

docs/tools/matic-js/advanced/exit-util.md

@@ -47,9 +47,9 @@ const proof = await exitUtil.buildPayloadForExit(
 
 ```
 
-### Generating proof using bridge client
+### Generating proof using a bridge client
 
-Every bridge client including **POSClient**, **PlasmaClient** exposes `exitUtil` property.
+Every bridge client including **POSClient** exposes `exitUtil` property.
 
 ```js
 import { POSClient,use } from "@maticnetwork/maticjs"