chore: reword (MetaMask#1314)

* Update wagmi.md * rewrite * change wording * Update wallet/how-to/use-sdk/3rd-party-libraries/wagmi.md --------- Co-authored-by: Joan E <[email protected]> Co-authored-by: Alexandra Tran Carrillo <[email protected]>
Eazyroyal · May 21, 2024 · 559f007 · 559f007
1 parent 96061bb
commit 559f007
Showing 1 changed file with 4 additions and 7 deletions.
diff --git a/wallet/how-to/use-sdk/3rd-party-libraries/wagmi.md b/wallet/how-to/use-sdk/3rd-party-libraries/wagmi.md
@@ -110,18 +110,15 @@ write();
 
 ## Benefits of using the Infura API with Wagmi
 
-Wagmi is not optimized for mobile environments.
-This limitation becomes evident when making read-only requests, which are queries that fetch data
-from the blockchain without making a transaction.
-Since mobile dapps might not maintain a continuous connection to MetaMask, these read-only requests
-can fail, leading to a suboptimal user experience.
+Read-only requests are blockchain requests that do not require user wallet interaction.
+Mobile dapps can lose their continuous connection with MetaMask, causing read-only requests to fail.
 
 These are some errors that might occur in mobile environments:
 
 ![Wagmi errors](../../../assets/wagmi-errors.png)
 
-To overcome this limitation in mobile dapps that rely on Wagmi, use the Infura API to make read-only
-requests.
+To overcome this limitation in mobile dapps that rely on a continuous connection with MetaMask,
+use the Infura API to make read-only requests.
 You can do this by [configuring the SDK with an Infura API key](#2-configure-the-sdk).
 This approach offloads the read operations to Infura's nodes, reducing the load on your own
 infrastructure and ensuring high availability and reliability, independent of the user's wallet connection.