Merge branch 'master' into webacy-1573

arbitrum-docs/build-decentralized-apps/arbitrum-vs-ethereum/01-comparison-overview.mdx

@@ -18,11 +18,11 @@ Time in L2s is tricky. The timing assumptions one is used to making about Ethere
 
 ## RPC methods
 
-Although the majority of RPC methods follow the same behavior than in Ethereum, some methods might produce a different result, or add more information, when used on an Arbitrum chain. You can find more information about these differences in [RPC methods](/build-decentralized-apps/arbitrum-vs-ethereum/03-rpc-methods.mdx).
+Although the majority of RPC methods follow the same behavior as Ethereum, some methods might produce a different result, or add more information, when used on an Arbitrum chain. You can find more information about these differences in [RPC methods](/build-decentralized-apps/arbitrum-vs-ethereum/03-rpc-methods.mdx).
 
 ## Solidity support
 
-You can deploy Solidity contracts onto Arbitrum just like you do Ethereum. There are only a few minor differences in behavior. Find more information about it in [Solidity support](/build-decentralized-apps/arbitrum-vs-ethereum/04-solidity-support.mdx).
+You can deploy Solidity contracts onto Arbitrum just like you do on Ethereum. There are only a few minor differences in behavior. Find more information about it in [Solidity support](/build-decentralized-apps/arbitrum-vs-ethereum/04-solidity-support.mdx).
 
 ## Fees
 

arbitrum-docs/launch-orbit-chain/how-tos/fast-withdrawals.mdx

@@ -197,6 +197,6 @@ The following parameters need to be configured in those nodes.
 
 :::note
 
-Immediately after configuring fast withdrawals, your chain may not operate at full speed yet. This ramp-up is because the validators must work through the backlog of assertions that have yet to be confirmed. You will see a series of 'NodeCreated' and 'NodeConfirmed' events. Once the backlog is processed, your chain should operate fully at speed.
+Immediately after configuring fast withdrawals - your chain may not be operating fully at speed yet. This is because the validators have to work through the backlog of assertions which were not yet confirmed. You will see a series of NodeCreated and NodeConfirmed events. Once the backlog has been processed, your chain should operate fully at speed.
 
 :::

arbitrum-docs/launch-orbit-chain/infra-options-orbit-chains.md

@@ -46,10 +46,9 @@ For applications that require the ability to transfer assets to chains outside o
 - [Across](https://across.to/)
 - [Decent](https://www.decent.xyz/)
 
-## Data availability Committee Operators
+## Data availability providers for AnyTrust Chains
 
-To reduce transaction fees for Orbit chains, you can configure a Data Availability (DA) solution that stores chain data off-chain with Anytrust Chains.
-If you are enabling Fast Withdrawals, you will set up a Data Availability Committee (DAC). We currently recommend (for security and decentralization purposes) to configure a DAC with at least 3 nodes. Here are a few providers:
+AnyTrust protocol offers native support data availability. If you are turning on Fast Withdrawals, we recommend having at least 3 members as part of your Data Availability Committee. Here are some providers we recommend:
 
 - [Chainbase](https://chainbase.com/)
 - [Ankr](https://www.ankr.com/)
@@ -95,7 +94,7 @@ RPC endpoints are the primary interface through which users and developers inter
 - [QuickNode](https://www.quicknode.com?utm_source=arb-docs)
 - [Sequence](https://sequence.xyz/node-gateway)
 
-## Alternative Data availability
+## Alternative data availability
 
 One way to reduce transaction fees for Orbit chains is to configure a Data Availability (DA) solution that stores chain data off-chain. Although the AnyTrust protocol offers native support for this functionality (and is configurable by default on Orbit AnyTrust chains), the following third-party providers give you another way to store data off-chain. Note that using these services will limit your chain's ability to leverage AnyTrust protocol improvements as they relate to transaction fee and DA configurability:
 

arbitrum-docs/stylus/quickstart.mdx

@@ -25,7 +25,7 @@ This guide will get you started with <a data-quicklook-from="stylus">Stylus</a>'
 <details>
 <summary>Rust toolchain</summary>
 
-Follow the instructions on [Rust Lang's installation page](https://www.rust-lang.org/tools/install) to install a complete Rust toolchain (v1.81 or older, v1.82 is currently not supported) on your system. After installation, ensure you can access the programs `rustup`, `rustc`, and `cargo` from your preferred terminal application.
+Follow the instructions on [Rust Lang's installation page](https://www.rust-lang.org/tools/install) to install a complete Rust toolchain (v1.81 or newer) on your system. After installation, ensure you can access the programs `rustup`, `rustc`, and `cargo` from your preferred terminal application.
 
 </details>
 

arbitrum-docs/stylus/using-cli.mdx

@@ -21,7 +21,7 @@ Cargo stylus is a plugin to the standard cargo tool for developing Rust programs
 <details>
 <summary>Rust toolchain</summary>
 
-Follow the instructions on [Rust Lang's installation page](https://www.rust-lang.org/tools/install) to install a complete Rust toolchain (v1.81 or older; v1.82 is currently not supported) on your system. After installation, ensure you can access the programs `rustup`, `rustc`, and `cargo` from your preferred terminal application.
+Follow the instructions on [Rust Lang's installation page](https://www.rust-lang.org/tools/install) to install a complete Rust toolchain (v1.81 or newer) on your system. After installation, ensure you can access the programs `rustup`, `rustc`, and `cargo` from your preferred terminal application.
 
 </details>