Condense batch transactions documentation to be more concise

Co-authored-by: aviggiano <[email protected]>

Author: Copilot

README.md

@@ -60,58 +60,19 @@ safe.proposeTransactionWithSignature(weth, abi.encodeCall(IWETH.withdraw, (0)),
 
 #### Batch transactions
 
-For proposing multiple transactions together, use `proposeTransactions`:
-
 ```solidity
-address[] memory targets = new address[](2);
-bytes[] memory datas = new bytes[](2);
-
-targets[0] = address(contract1);
-datas[0] = abi.encodeCall(Contract1.someFunction, ());
-
-targets[1] = address(contract2);
-datas[1] = abi.encodeCall(Contract2.anotherFunction, ());
-
 safe.proposeTransactions(targets, datas, sender, "m/44'/60'/0'/0/0");
 ```
 
-If you need to pre-compute the signature for batch transactions (e.g., when using a Ledger), you must:
-
-1. Get the target and data for the batch transaction using `getProposeTransactionsTargetAndData`:
+For pre-computed signatures with hardware wallets:
 
 ```solidity
 (address to, bytes memory data) = safe.getProposeTransactionsTargetAndData(targets, datas);
-```
-
-2. Sign the transaction with `Enum.Operation.DelegateCall` (**NOT** `Call`):
-
-```solidity
 bytes memory signature = safe.sign(to, data, Enum.Operation.DelegateCall, sender, "m/44'/60'/0'/0/0");
-```
-
-3. Propose the transactions with the signature:
-
-```solidity
 safe.proposeTransactionsWithSignature(targets, datas, sender, signature);
 ```
 
-**⚠️ CRITICAL**: Batch transactions **MUST** use `Enum.Operation.DelegateCall` to preserve `msg.sender` across sub-calls. 
-
-**Common Mistake**: If you sign with `Enum.Operation.Call` instead of `DelegateCall`, the Safe API will reject your transaction with an error about an incorrect signer address. The signer address reported in the error will not match your actual signing address because the signature will be invalid.
-
-**Correct usage**:
-```solidity
-// ✓ CORRECT - Use DelegateCall for batch transactions
-bytes memory signature = safe.sign(to, data, Enum.Operation.DelegateCall, sender, derivationPath);
-safe.proposeTransactionsWithSignature(targets, datas, sender, signature);
-```
-
-**Incorrect usage**:
-```solidity
-// ✗ WRONG - Using Call instead of DelegateCall will cause signature validation to fail
-bytes memory signature = safe.sign(to, data, Enum.Operation.Call, sender, derivationPath);
-safe.proposeTransactionsWithSignature(targets, datas, sender, signature);
-```
+**⚠️ Important**: Batch transactions require `Enum.Operation.DelegateCall` (not `Call`). Using `Call` causes signature validation errors.
 
 ### Requirements