docs: update WalletAccount guide

www/docs/guides/walletAccount.md

@@ -4,46 +4,50 @@ sidebar_position: 9
 
 # WalletAccount
 
-**Use wallets (like Braavos & ArgentX) to sign your transactions in your DAPP.**
+**Use wallets to sign transactions in your DAPP.**
 
-The `WalletAccount` class is similar to the regular `Account` class, but is also able to ask a browser wallet to sign and send a transaction. Some other cool functionalities will be detailed hereunder.
+The [`WalletAccount`](../API/classes/WalletAccount) class is similar to the regular [`Account`](../API/classes/Account) class, with the added ability to ask a browser wallet to sign and send transactions. Some other cool functionalities will be detailed hereunder.
 
-The private key of a WalletAccount is held in a browser wallet (as ArgentX or Braavos), and any signature is managed by the wallet. You don't have to manage in your DAPP the security of any private key.
+The private key of a `WalletAccount` is held in a browser wallet (such as ArgentX, Braavos, etc.), and any signature is managed by the wallet. With this approach DAPPs don't need to manage the security for any private key.
 
 :::caution
-This class is working only in the scope of a DAPP. You can't use it in a node.js script.
+This class functions only within the scope of a DAPP. It can't be used in a Node.js script.
 :::
 
 ## Architecture
 
 ![](./pictures/WalletAccountArchitecture.png)
 
-If you want to read Starknet, the WalletAccount will read directly the blockchain. That's why at the initialization of a WalletAccount, you need to put in the parameters a Provider instance. It will be used for all reading activities.
+When retrieving information from Starknet, a `WalletAccount` instance will read directly from the blockchain. That is why at the initialization of a `WalletAccount` a [`Provider`](../API/classes/Provider) instance is a required parameter, it will be used for all reading activities.
 
-If you want to write to Starknet, the WalletAccount will ask the browser Wallet to sign and send the transaction, using the Starknet Wallet API to communicate.  
-As several Wallets can be installed in your browser, the WalletAccount needs the ID of one of the available wallets. You can ask `get-starknet` to display a list of available wallets and to provide as a response the identifier of the selected wallet, called a `Starknet Windows Object` (named SWO from now).
+If you want to write to Starknet the `WalletAccount` will ask the browser wallet to sign and send the transaction using the Starknet Wallet API to communicate.
+
+As several wallets can be installed in your browser, the `WalletAccount` needs the ID of one of the available wallets. You can ask `get-starknet` to display a list of available wallets and to provide as a response the identifier of the selected wallet, called a `Starknet Windows Object` (referred to as SWO in the rest of this guide).
 
 ## Select a Wallet
 
-You can ask the `get-starknet` v4 library to display a list of wallets, then it will ask you to make a choice. It will return the SWO of the wallet the user selected.  
-Using the `get-starknet-core` v4 library, you can create your own UI and logic to select the wallet. An example of DAPP using a custom UI : [**here**](https://github.com/PhilippeR26/Starknet-WalletAccount/blob/main/src/app/components/client/WalletHandle/SelectWallet.tsx), where you can select only the wallets compatible with the Starknet wallet API.  
+You can ask the `get-starknet` v4 library to display a list of wallets, then it will ask you to make a choice. It will return the SWO of the wallet the user selected.
+
+Using the `get-starknet-core` v4 library you can create your own UI and logic to select the wallet. An example of DAPP using a custom UI: [**here**](https://github.com/PhilippeR26/Starknet-WalletAccount/blob/main/src/app/components/client/WalletHandle/SelectWallet.tsx), in the example you can select only the wallets compatible with the Starknet Wallet API.  
 ![](./pictures/SelectWallet.png)
 
-So, you instantiate a new WalletAccount with :
+Instantiating a new `WalletAccount`:
 
 ```typescript
 import { connect } from '@starknet-io/get-starknet'; // v4.0.3 min
-import { WalletAccount } from 'starknet'; // v6.10.0 min
+import { WalletAccount } from 'starknet'; // v6.18.0 min
 const myFrontendProviderUrl = 'https://free-rpc.nethermind.io/sepolia-juno/v0_7';
-// standard UI to select a wallet :
+// standard UI to select a wallet:
 const selectedWalletSWO = await connect({ modalMode: 'alwaysAsk', modalTheme: 'light' });
-const myWalletAccount = new WalletAccount({ nodeUrl: myFrontendProviderUrl }, selectedWalletSWO);
+const myWalletAccount = await WalletAccount.connect(
+  { nodeUrl: myFrontendProviderUrl },
+  selectedWalletSWO
+);
 ```
 
-## Use as an account
+## Use as an Account
 
-Once the new WalletAccount is created, you can use all the power of Starknet.js, exactly as a with a normal Account instance.  
-You can use for example `myWalletAccount.execute(call)` or `myWalletAccount.signMessage(typedMessage)` :
+Once a new `WalletAccount` is created, you can use all the power of Starknet.js, exactly as a with a normal `Account` instance, for example `myWalletAccount.execute(call)` or `myWalletAccount.signMessage(typedMessage)`:
 
 ```typescript
 const claimCall = airdropContract.populate('claim_airdrop', {
@@ -57,34 +61,34 @@ const resp = await myWalletAccount.execute(claimCall);
 
 ## Use in a Contract instance
 
-You can connect a WalletAccount with a Contract instance. All reading actions are performed by the provider of the WalletAccount, and all writing actions (that needs a signature) are performed by the browser wallet.
+You can connect a `WalletAccount` with a [`Contract`](../API/classes/Contract) instance. All reading actions are performed by the provider of the `WalletAccount`, and all writing actions (that need a signature) are performed by the browser wallet.
 
 ```typescript
 const lendContract = new Contract(contract.abi, contractAddress, myWalletAccount);
-const qty = await lendContract.get_available_asset(addr); // use of the WalletAccount provider.
+const qty = await lendContract.get_available_asset(addr); // use of the WalletAccount provider
 const resp = await lendContract.process_lend_asset(addr); // use of the browser wallet
 ```
 
-## Use as a provider
+## Use as a Provider
 
-Your WalletAccount instance can be used as a provider :
+Your `WalletAccount` instance can be used as a provider:
 
 ```typescript
 const bl = await myWalletAccount.getBlockNumber();
 // bl = 2374543
 ```
 
-You can use all the methods of the RpcProvider class. Under the hood, the WalletAccount will use the rpc node that you indicated at its instantiation.
+You can use all the methods of the `Provider` class. Under the hood, the `WalletAccount` will use the RPC node that you indicated at its instantiation.
 
 ## Subscription to events
 
-You can subscribe to 2 events :
+You can subscribe to 2 events:
 
-- `accountsChanged` : Triggered each time you change the current account in the wallet.
-- `networkChanged` : Triggered each time you change the current network in the wallet.
+- `accountsChanged`: Triggered each time you change the current account in the wallet.
+- `networkChanged`: Triggered each time you change the current network in the wallet.
 
-At each change of the network, both account and network events are occurring.  
-At each change of the account, only the account event is occurring.
+At each change of the network, both account and network events are emitted.  
+At each change of the account, only the account event is emitted.
 
 ### Subscribe
 
@@ -111,30 +115,31 @@ const handleNetwork: NetworkChangeEventHandler = (chainId?: string, accounts?: s
 selectedWalletSWO.on('networkChanged', handleNetwork);
 ```
 
-### Un-subscribe :
+### Unsubscribe
 
-Similar to subscription, using `.off` method.
+Similar to subscription, by using the `.off` method.
 
 ```typescript
 selectedWalletSWO.off('accountsChanged', handleAccount);
 selectedWalletSWO.off('networkChanged', handleNetwork);
 ```
 
 :::info
-You can subscribe both with the SWO or with a WalletAccount instance.  
-The above examples are using the SWO, because it's the simpler way to process.
+You can subscribe both with the SWO or with a `WalletAccount` instance.  
+The above examples are using the SWO, because it is the simpler way to process.
 :::
 
 ## Direct access to the wallet API entry points
 
-The WalletAccount class is able to interact with all the entrypoints of the Starknet wallet API, including some functionalities that do not exists in an Account class.
-You have a full description of this API [**here**](https://github.com/PhilippeR26/Starknet-WalletAccount/blob/main/doc/walletAPIspec.md).
+The `WalletAccount` class is able to interact with all the entrypoints of the Starknet Wallet API, including some functionalities that do not exists in the `Account` class.
+
+A full description of this API can be found [**here**](https://github.com/PhilippeR26/Starknet-WalletAccount/blob/main/doc/walletAPIspec.md).
 
 Some examples:
 
-### Request a change of wallet network
+### Request to change the wallet network
 
-Using your WalletAccount, you can ask the wallet to change its current network:
+Using your `WalletAccount`, you can ask the wallet to change its current network:
 
 ```typescript
 useEffect(
@@ -154,7 +159,7 @@ useEffect(
 
 ### Request to display a token in the wallet
 
-Using your WalletAccount, you can ask the wallet to display a new token:
+Using your `WalletAccount`, you can ask the wallet to display a new token:
 
 ```typescript
 useEffect(
@@ -177,9 +182,10 @@ useEffect(
 
 ![](./pictures/addToken.png)
 
-## Change of network or account
+## Changing the network or account
+
+When you change the network or the account address a `WalletAccount` instance is automatically updated, however, this can lead to unexpected behavior if one is not careful (reads and writes targeting different networks, problems with Cairo versions of the accounts, ...).
 
-When you change the network or the account address, the WalletAccount is automatically updated, but it can lead to tricky behavior (read and write in different networks, problems of Cairo versions of the accounts, ....).  
 :::warning RECOMMENDATION
-It's strongly recommended to create a new WalletAccount instance each time the network or the account address is changed.
+It is strongly recommended to create a new `WalletAccount` instance each time the network or the account address is changed.
 :::