update docs based on feedbacks

buidler-labs · Sep 24, 2024 · ff928ac · ff928ac
1 parent 35df2ba
commit ff928ac
Show file tree

Hide file tree

Showing 6 changed files with 8 additions and 15 deletions.
diff --git a/docs/configuration.md b/docs/configuration.md
@@ -148,7 +148,7 @@ export default {
 - **Type**: `boolean`
 - **Required**: `false`
 - **Default**: `false`
-- **Description**: Allows your dApp to connect multiple wallets at the same time.
+- **Description**: Allows your dApp to connect multiple wallets at the same time `in a one wallet per connector manner`.
 
 ::: tip
 If this is enabled, you have to specify the desired `connector` whenever you use a hook.

diff --git a/docs/guides/connect-wallet.md b/docs/guides/connect-wallet.md
@@ -2,7 +2,9 @@
 
 By using `useWallet` hook, you can simply call `connect` method, and your wallet should pop up with a connection request.
 
-Also, it provides different wallet states like `isExtensionRequired`, `extensionReady`, `isConnected` in order to develop a great user experience.
+Furthermore, it allows you to craft great user experiences by giving you access different wallet states such as `isExtensionRequired`, `extensionReady` or `isConnected`.
+
+Following is a snippet of how one might go about doing just that:
 
 ```tsx
 import { KabilaConnector } from '@buidlerlabs/hashgraph-react-wallets/connectors'

diff --git a/docs/guides/execute-transactions.md b/docs/guides/execute-transactions.md
@@ -2,7 +2,7 @@
 
 Our collection of [`React Hooks`](/hooks/) aims to cover all developer's needs for interacting with the Hedera network, though there are a few exceptions that can be easily handled.
 
-In the following examples, we demonstrate two ways to execute one of the most popular transactions on the network: the `TokenAssociateTransaction`.
+The following examples illustrate, for comparison reasons of verbosity, 2 ways of doing a token associate transaction.
 
 ### Using `useAssociateTokens` hook:
 

diff --git a/docs/strategies/built-in/hwc-connection-strategy.md b/docs/strategies/built-in/hwc-connection-strategy.md
@@ -6,9 +6,4 @@ The implementation is straightforward, as its main responsibility is to initiali
 
 ::: info
 It requires a `projectId` that needs to be configured on `<HWBridgeProvider>`. Read more about the [`configuration`](/configuration.html#%F0%9F%8E%AB-projectid)
-:::
-
-### Not Enough?
-
-You can create your own connection strategy according to your preferences. [Read more](/strategies/create-connection-strategy)
-
+:::
diff --git a/docs/strategies/built-in/index.md b/docs/strategies/built-in/index.md
@@ -9,4 +9,4 @@ The library provides the following internally built and ready-to-use connection
 
 ### Not Enough?
 
-You can create your own connection strategy according to your preferences. [Read more](/strategies/create-connection-strategy)
+You can [create your own](/strategies/create-connection-strategy).
diff --git a/docs/strategies/built-in/wagmi-connection-strategy.md b/docs/strategies/built-in/wagmi-connection-strategy.md
@@ -2,8 +2,4 @@
 
 Similar to the [`HWCConnectionStrategy`](/strategies/hwc-connection-strategy), this connection strategy enables interaction with the chain via [`wagmi`](https://wagmi.sh/) through `JSON-RPC`.
 
-The core responsibility of this strategy is to initialize a `wagmi` configuration, derived from the primary config of `<HWBridgeProvider>` ([`chains`](/configuration.html#🔗-chains)/[`connectors`](/configuration.html#🔌-connectors)), which will subsequently be used for executing actions on the chain.
-
-### Not Enough?
-
-You can create your own connection strategy according to your preferences. [Read more](/strategies/create-connection-strategy)
+The core responsibility of this strategy is to initialize a `wagmi` configuration, derived from the primary config of `<HWBridgeProvider>` ([`chains`](/configuration.html#🔗-chains)/[`connectors`](/configuration.html#🔌-connectors)), which will subsequently be used for executing actions on the chain.