docs(README): update readme to add more clear multisend docs

Author: fubuloubu

README.md

@@ -45,24 +45,28 @@ $ python3 setup.py install
 
 ## Quick Usage
 
-To use the plugin, first use the CLI extension to add a safe you created:
+To use the plugin, first use the Ape CLI extension to add a safe you want to control:
 
 ```sh
-ape safe add --network ethereum:mainnet "my-safe.eth" my-safe
+# ape safe add ADDRESS ALIAS
+ape safe add --network ethereum:mainnet my-safe.eth my-safe
 ```
 
 If you made a mistake or just need to remove the safe, use the `remove` command:
 
 ```sh
+# ape safe remove ALIAS
 ape safe remove my-safe --yes
 ```
 
-**NOTE** `--yes` is a way to skip the prompt.
+```{note}
+`--yes` is a way to skip the prompt.
+```
 
-If you only add one safe, you will not have to specify which safe to use other commands.
+If you only have one safe, you will not have to specify which safe to use other commands.
 Otherwise, for most `pending` commands, you specify the safe to use (by alias) via the `--safe` option.
 
-Additionally, you can configure a safe to use as the default in your `ape-config.yaml` file:
+Additionally, you can configure a safe to use as the default when no `--safe` argument is present by configuring the following in your `ape-config.yaml` file:
 
 ```yaml
 safe:
@@ -76,28 +80,17 @@ or via `pyproject.toml`:
 default_safe = "my-safe"
 ```
 
-To specify via environment variable, do:
+or specify via environment variable:
 
 ```sh
-APE_SAFE_DEFAULT_SAFE="my-safe"
+export APE_SAFE_DEFAULT_SAFE="my-safe"
 ```
 
-**NOTE**: To avoid always needing to specify `--network`, you can set a default ecosystem, network, and provider in your config file.
-Here is an example:
-
-```yaml
-default_ecosystem: ethereum
-
-ethereum:
-  default_network: mainnet
-  mainnet:
-    default_provider: infura
+```{note}
+To avoid always needing to specify `--network`, you can set a default ecosystem, network, and provider in your config file.
+The rest of the guide will not specify `--network` on each command but assume it matches the network your Safe is on.
 ```
 
-The rest of the guide will not specify `--network` on each command but assume the correct one is set in the config file.
-
----
-
 Once you have a safe, you can view pending transactions:
 
 ```sh
@@ -106,14 +99,14 @@ ape safe pending list
 
 ```{note}
 You must specify the environment variable `APE_SAFE_GATEWAY_API_KEY=` to use the Safe Gateway API.
-Get an API key at https://developer.safe.global/.
+Get an API key at the [Safe Developer Portal](https://developer.safe.global).
 ```
 
 It should show transactions like this:
 
 ```sh
-Transaction 8 rejection (1/2) safe_tx_hash=0x09ab9a229fc60da66ec0fa8fa886ab7c95902fdf5df5a5009ba06010fbb9a9a7
-Transaction 8 transfer  (1/2) safe_tx_hash=0xed43d80255bcd5ffacb755e8f51bee825913373705d6baea006419d2a33a0a5b
+Transaction 8 rejection (1/2) safe_tx_hash=0x09ab...a9a7
+Transaction 8 transfer  (1/2) safe_tx_hash=0xed43...0a5b
 ```
 
 Use the `--verbose` flag to see more information about each transaction:
@@ -125,47 +118,51 @@ ape safe pending list --verbose
 There are several operations you can do on a pending transaction:
 
 ```sh
-# Approve a transaction (add your signature)
-ape safe pending approve 0x09ab9a229fc60da66ec0fa8fa886ab7c95902fdf5df5a5009ba06010fbb9a9a7
+# Add more signatures using locally-configured Ape signer(s)
+# NOTE: can specify either SafeTxID or Nonce
+ape safe pending approve 0x09ab...a9a7
 
-# Approve and execute in one step
-ape safe pending approve 2 --execute my_account
+# Add remaining signatures and execute transction w/ account alias `submitter`
+# NOTE: can specify either SafeTxID or Nonce
+ape safe pending approve 2 --execute submitter
 
-# Execute a fully signed transaction
-ape safe pending execute 2
+# Execute an already-signed transaction using `submitter`
+ape safe pending execute 2 --account submitter
 
-# Reject a transaction
+# Create an on-chain rejection for an existing transaction queue item
 ape safe pending reject 2
 ```
 
-## MultiSend Example
+### MultiSend Support
 
-The following example shows how to use multisend to batch transactions:
+Ape Safe allows sending "batched transactions" using the `MultiSend` module:
 
 ```python
-from ape_safe import multisend
 from ape import accounts
+from ape_safe import multisend
 from ape_tokens import tokens
 
+me = accounts.load("my-key")
 safe = accounts.load("my-safe")
 
 # Load some contracts using ape-tokens
 dai = tokens["DAI"]
 vault = tokens["yvDAI"]
 amount = dai.balanceOf(safe)  # How much we want to deposit
 
-# Create a multisend transaction (a transaction that executes multiple calls)
-txn = multisend.MultiSend()
-txn.add(dai.approve, vault, amount)
-txn.add(vault.deposit, amount)
+# Create a multisend batch transaction
+batch = safe.create_batch()
+batch.add(dai.approve, vault, amount)
+batch.add(vault.deposit, amount)
 
-# Fetch signatures from local signers and broadcast if confirmations are met
-txn(sender=safe, gas=0)
+# Fetch signatures from local signer(s)
+# NOTE: will broadcast unless `submit=False`
+batch(submitter=me)
+# OR add to the Safe Gateway for later execution
+batch.propose()
 ```
 
-<<<<<<< HEAD
-
-## Cloud Usage
+### Cloud Environment
 
 To use this plugin in a cloud environment, such as with the [Silverback Platform](https://silverback.apeworx.io), you will need to make sure that you have configured your Safe to exist within the environment.
 The easiest way to do this is to use the `require` configuration item.
@@ -176,15 +173,15 @@ safe:
   require:
     my-safe:
       address: "0x1234...AbCd"
-      deployed_chain_ids: [1, ...]
+      deployed_chain_ids: [1, 10] # Add all deployed chains here
 ```
 
 or in `pyproject.toml`:
 
 ```toml
 [tool.ape.safe.require."my-safe"]
 address = "0x1234...AbCd"
-deployed_chain_ids = [1, ...]
+deployed_chain_ids = [1, 10] # Add all deployed chains here
 ```
 
 To specify via environment variable, do:
@@ -193,25 +190,10 @@ To specify via environment variable, do:
 APE_SAFE_REQUIRE='{"my-safe":{"address":"0x1234...AbCd","deployed_chain_ids":[1,...]}}'
 ```
 
-```{notice}
+```{note}
 If a safe with the same alias as an entry in `require` exists in your local environment, this will skip adding it, even if the existing alias points to a different address than the one in the config item.
 ```
 
-=======
-
-## Documentation
-
-For more detailed documentation, see:
-
-- [Setup](./docs/setup.md) - Configuration and initial setup
-- [Basic Usage](./docs/basic_usage.md) - Essential operations
-- [Safe Management](./docs/safe_management.md) - Adding, listing and removing Safes
-- [Transaction Workflows](./docs/transactions.md) - Understanding the transaction lifecycle
-- [MultiSend](./docs/multisend.md) - Batching transactions
-- [CLI Reference](./docs/cli.md) - Command line interface documentation
-- [API Reference](./docs/api.md) - Python API documentation
-  > > > > > > > 1a59826 (docs: create comprehensive modern documentation)
-
 ## Development
 
 Please see the [contributing guide](CONTRIBUTING.md) to learn more how to contribute to this project.