Update README files

Author: TucksonDev

README.md

@@ -1,6 +1,6 @@
 # Arbitrum Tutorials
 
-This monorepo will help you get started with building on Arbitrum. It provides various simple demos showing and explaining how to interact with Arbitrum — deploying and using contracts directly on L2, moving Ether and tokens betweens L1 and L2, and more.
+This monorepo will help you get started with building on Arbitrum chains. It provides various simple demos showing and explaining how to interact with Arbitrum chains (including Orbit chains) — deploying and using contracts directly on Arbitrum, moving Ether and tokens betweens the parent and child chains, and more.
 
 We show how you can use broadly supported Ethereum ecosystem tooling (Hardhat, Ethers-js, etc.) as well as our special [Arbitrum SDK](https://github.com/OffchainLabs/arbitrum-sdk) for convenience.
 
@@ -16,30 +16,38 @@ yarn install
 
 #### :white_check_mark: Basics
 
-- 🐹 [Pet Shop DApp](./packages/demo-dapp-pet-shop/) (L2 only)
-- 🗳 [Election DApp](./packages/demo-dapp-election/) (L2 only)
+- 🐹 [Pet Shop DApp](./packages/demo-dapp-pet-shop/)
+- 🗳 [Election DApp](./packages/demo-dapp-election/)
 
-#### :white_check_mark: Moving Stuff around
+#### :white_check_mark: Moving stuff around
 
 - ⤴️ 🔹 [Deposit Ether](./packages/eth-deposit/)
 - ⤵️ 🔹 [Withdraw Ether](./packages/eth-withdraw/)
 - ⤴️ 💸 [Deposit Token](./packages/token-deposit/)
 - ⤵️ 💸 [Withdraw token](./packages/token-withdraw/)
-- ⤴️ 🔹 [L2 Alias Control and Fund Transfer Guide](./packages/contract-deposit/)
+- ⤴️ 🔹 [Contract alias control in the child chain, and fund-transfer guide](./packages/contract-deposit/)
 
 #### :white_check_mark: General interop
 
-- 🤝 [Greeter](./packages/greeter/) (L1 to L2)
-- 📤 [Outbox](./packages/outbox-execute/) (L2 to L1)
+- 🤝 [Greeter](./packages/greeter/) (parent to child messages)
+- 📤 [Outbox](./packages/outbox-execute/) (child to parent messages)
 - ⏰ [L1 Confirmation Checker](./packages/l1-confirmation-checker/)
 - ⏰ [L2 block verification in assertion](./packages/l2-block-verification-in-assertion/)
 
-#### :white_check_mark: Advanced Features
+#### :white_check_mark: Advanced features
 
 - ®️ [Arb Address Table](./packages/address-table/)
 - 🌉 [Bridging Custom Token](./packages/custom-token-bridging/)
 - ✈️ [Delayed inbox message(l2MSG)](./packages/delayedInbox-l2msg/)
 - 🎁 [Redeem Retryable Ticket](./packages/redeem-failed-retryable/)
 - 🌀 [Deposit Ether or Tokens from L1 to L3](./packages/l1-l3-teleport/)
 
+## How to run the tutorials against a custom network
+
+As mentioned above, these tutorials use the [Arbitrum SDK](https://github.com/OffchainLabs/arbitrum-sdk), which loads the regular Arbitrum chains by default (Arbitrum One, Arbitrum Nova and Arbitrum Sepolia). You can use these tutorials against any other Arbitrum chain (including Orbit chains), by loading it to the Arbitrum SDK.
+
+To do that, fill the information of your chain in the [`customNetwork.json`](./customNetwork.json) file., which is automatically loaded in all tutorials.
+
+To obtain the information of a specific chain, you can use the method [`prepareArbitrumNetwork`](https://github.com/OffchainLabs/arbitrum-orbit-sdk/blob/main/src/utils/registerNewNetwork.ts#L18) of the Orbit SDK.
+
 <p align="center"><img src="assets/logo.svg" width="300"></p>

packages/address-table/README.md

@@ -1,6 +1,6 @@
-# Address Table Demo
+# Address table demo
 
-The Address table is a precompiled contract on Arbitrum for registering addresses which are then retrievable by an integer index; this saves gas by minimizing precious calldata required to input an address as a parameter.
+The Address table is a precompiled contract on Arbitrum chains for registering addresses which are then retrievable by an integer index; this saves gas by minimizing precious calldata required to input an address as a parameter.
 
 This demo shows a simple contract with affordances to retrieve an address from a contract by its index in the address table, and a client-side script to pre-register the given address (if necessary).
 
@@ -12,15 +12,17 @@ See `exec.js` for inline comments / explanation.
  yarn run exec
 ```
 
-## Config Environment Variables
+## Set environment variables
 
 Set the values shown in `.env-sample` as environmental variables. To copy it into a `.env` file:
 
 ```bash
 cp .env-sample .env
 ```
 
-(you'll still need to edit some variables, i.e., `PRIVATE_KEY` and `CHAIN_RPC`)
+You'll still need to edit some variables, i.e., `PRIVATE_KEY` and `CHAIN_RPC`.
+
+Note that you can also set the environment variables in an `.env` file in the root of the monorepo, which will be available in all tutorials.
 
 ### More info
 

packages/contract-deposit/README.md

@@ -1,33 +1,34 @@
-# L2 alias control and fund transfer guide
+# Contract alias control in the child chain, and fund-transfer guide
 
-`L2 Alias Control and Fund Transfer Guide` is a simple demonstration of how Arbitrum facilitates sending deposits from an L1 contract to L2.
+`Contract alias control in the child chain, and fund-transfer guide` is a simple demonstration of how Arbitrum facilitates sending deposits from a contract in the parent chain, to the child chain.
 
-It will deposit funds to l2 via a l1 contract, and because the inbox contract will alias the sender address if it is a contract,
-this tutorial shows how to control the alias address on l2 via its l1 contract address.
+It will deposit funds to the child chain via a contract deployed to the parent chain, and because the inbox contract will alias the sender address if it is a contract, this tutorial shows how to control the alias address on the child chain via the address of the contract on the parent chain.
 
-This tutorial demonstrates depositing funds to L2 using an L1 contract. Since the Inbox contract changes the sender address if it's a contract [(a.k.a address aliasing)](https://docs.arbitrum.io/how-arbitrum-works/arbos/l1-l2-messaging#address-aliasing), it explains how to manage the new L2 address using the L1 contract address. It's a basic example of how an L1 contract controls its L2 alias and transfers its alias funds to another address. For practical use, we recommend our [funds recovery tool](<(https://github.com/OffchainLabs/arbitrum-funds-recovery-tool)>).
+This tutorial demonstrates depositing funds to the child chain using a contract deployed to the parent chain. Since the Inbox contract changes the sender address if it's a contract [(a.k.a address aliasing)](https://docs.arbitrum.io/how-arbitrum-works/arbos/l1-l2-messaging#address-aliasing), it explains how to manage the aliased address on the child chain using the contract address on the parent chain. It's a basic example of how a contract controls its alias on the child chain, and transfers its funds from the aliased address to another address. For practical use, we recommend our [funds recovery tool](https://github.com/OffchainLabs/arbitrum-funds-recovery-tool).
 
-The script and contracts demonstrate how to interact with Arbitrum's core bridge contracts to create these retryable messages, how to calculate and forward appropriate fees from L1 to L2, and how to use Arbitrum's L1-to-L2 message [address aliasing](https://developer.offchainlabs.com/docs/l1_l2_messages#address-aliasing).
+The script and contracts demonstrate how to interact with Arbitrum's core bridge contracts to create these retryable messages, how to calculate and forward appropriate fees from the parent to the child chain, and how to use Arbitrum's cross-chain message [address aliasing](https://docs.arbitrum.io/how-arbitrum-works/arbos/l1-l2-messaging#address-aliasing).
 
 See [./exec.js](./scripts/exec.js) for inline explanations.
 
-[Click here](https://developer.offchainlabs.com/docs/l1_l2_messages) for more info on retryable tickets.
+[Click here](https://docs.arbitrum.io/how-arbitrum-works/arbos/l1-l2-messaging) for more info on retryable tickets.
 
-### Run demo:
+### Run demo
 
 ```
 yarn start
 ```
 
-## Config environment variables
+## Set environment variables
 
 Set the values shown in `.env-sample` as environmental variables. To copy it into a `.env` file:
 
 ```shell
 cp .env-sample .env
 ```
 
-(you'll still need to edit some variables, i.e., `DEVNET_PRIVKEY`)
+You'll still need to edit some variables, i.e., `PRIVATE_KEY`, `CHAIN_RPC`, `PARENT_CHAIN_RPC` and `TransferTo`.
+
+Note that you can also set the environment variables in an `.env` file in the root of the monorepo, which will be available in all tutorials.
 
 <p align="left">
   <img width="350" height="150" src= "../../assets/logo.svg" />