From 6cbadab491b5fbe7ddb7e0a7df9ece7f69e2af5f Mon Sep 17 00:00:00 2001
From: Dmytrol <46675332+Dimitrolito@users.noreply.github.com>
Date: Tue, 10 Dec 2024 15:29:34 +0200
Subject: [PATCH 1/9] typos hedera-rpc.md
---
docs/advanced/multichain/rpc-reference/hedera-rpc.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/advanced/multichain/rpc-reference/hedera-rpc.md b/docs/advanced/multichain/rpc-reference/hedera-rpc.md
index bd4027710..4ff2659e7 100644
--- a/docs/advanced/multichain/rpc-reference/hedera-rpc.md
+++ b/docs/advanced/multichain/rpc-reference/hedera-rpc.md
@@ -55,7 +55,7 @@ In certain conditions, the Hedera network will return a response that signifies
1. `Object` - Result of transaction submission to Hedera network
1.1. `code` : 9000 - The reserved WalletConnect error code for unknown errors or errors not related to the WalletConnect protocol
- 1.2. `message` : `String` - A human readable string describing the nature of the failure
+ 1.2. `message` : `String` - A human-readable string describing the nature of the failure
1.3. `data` : `Number` - An integer representing the ResponseCodeEnum value returned from the Hedera Node, which indicates the reason for the failure
@@ -295,4 +295,4 @@ While constructing a transaction for transmission to a controller, a dApp needs
"nodes": ["0.0.3", "0.0.4"]
}
}
-```
\ No newline at end of file
+```
From 5fec58e144319df64372775988caf2d46c67cc4b Mon Sep 17 00:00:00 2001
From: Dmytrol <46675332+Dimitrolito@users.noreply.github.com>
Date: Tue, 10 Dec 2024 15:30:14 +0200
Subject: [PATCH 2/9] typos about.mdx
---
docs/advanced/walletconnectmodal/about.mdx | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/advanced/walletconnectmodal/about.mdx b/docs/advanced/walletconnectmodal/about.mdx
index 03e07ea67..356353f32 100644
--- a/docs/advanced/walletconnectmodal/about.mdx
+++ b/docs/advanced/walletconnectmodal/about.mdx
@@ -411,7 +411,7 @@ More wallet package names can be found in [our sample AndroidManifest.xml](https
Wallet detection may produce inaccurate results on iOS Simulator. It is recommended to test on a real device.
1. Make an iOS build.
-2. In the generated Xcode project, find `Info.plist` file and open it with a external editor (i.e. not Xcode).
+2. In the generated Xcode project, find `Info.plist` file and open it with an external editor (i.e. not Xcode).
3. Locate or create `LSApplicationQueriesSchemes` section.
4. Add the desired wallet schemes as string entries within the ``. These schemes represent the wallets you want to detect.
From d1c73e3f1c6d63affe927aa0098baea5c8a150ec Mon Sep 17 00:00:00 2001
From: Dmytrol <46675332+Dimitrolito@users.noreply.github.com>
Date: Tue, 10 Dec 2024 15:31:41 +0200
Subject: [PATCH 3/9] typos pairing.mdx
---
docs/api/core/pairing.mdx | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/api/core/pairing.mdx b/docs/api/core/pairing.mdx
index 3fc82a20d..7e633a5ca 100644
--- a/docs/api/core/pairing.mdx
+++ b/docs/api/core/pairing.mdx
@@ -319,7 +319,7 @@ Now wallet and a dapp have a secure communication channel that will be used by t
#### Pairing Dapp Usage
-In order to pair dapp and a wallet, dapp needs to generate and share a uri with wallet.
+In order to pair dapp and a wallet, dapp needs to generate and share an uri with wallet.
To generate a uri call `create()` function on Pair instance as follows.
```swift
From 8fcbdc31a4779dcdd997bd99f132df43a5f3b24f Mon Sep 17 00:00:00 2001
From: Dmytrol <46675332+Dimitrolito@users.noreply.github.com>
Date: Tue, 10 Dec 2024 15:32:45 +0200
Subject: [PATCH 4/9] typos pairing.mdx
---
docs/api/core/pairing.mdx | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/docs/api/core/pairing.mdx b/docs/api/core/pairing.mdx
index 7e633a5ca..d07519b12 100644
--- a/docs/api/core/pairing.mdx
+++ b/docs/api/core/pairing.mdx
@@ -320,7 +320,7 @@ Now wallet and a dapp have a secure communication channel that will be used by t
#### Pairing Dapp Usage
In order to pair dapp and a wallet, dapp needs to generate and share an uri with wallet.
-To generate a uri call `create()` function on Pair instance as follows.
+To generate an uri call `create()` function on Pair instance as follows.
```swift
let uri = try await Pair.instance.create()
@@ -337,7 +337,7 @@ Now you can share the uri with the wallet.
val pairing: Pairing? = CoreClient.Pairing.create() { error -> }
```
-When first establishing a pairing with a Peer, call `CoreClient.Pairing.create`. This will try and generate a new pairing with a URI parameter that can be used to establish a connection with the other Peer as well as other meta data related to the pairing.
+When first establishing a pairing with a Peer, call `CoreClient.Pairing.create`. This will try and generate a new pairing with an URI parameter that can be used to establish a connection with the other Peer as well as other meta data related to the pairing.
#
@@ -436,7 +436,7 @@ Now the wallet and a dapp have a secure communication channel that will be used
#### Pairing Dapp Usage
-In order to pair dapp and a wallet, dapp needs to generate and share a uri with wallet. To generate a uri call `create()` function on Pair instance as follows.
+In order to pair dapp and a wallet, dapp needs to generate and share an uri with wallet. To generate an uri call `create()` function on Pair instance as follows.
```csharp
From e42c89f2b5b1a2394a5adbd2de3e2fcebde407e6 Mon Sep 17 00:00:00 2001
From: Dmytrol <46675332+Dimitrolito@users.noreply.github.com>
Date: Tue, 10 Dec 2024 15:41:28 +0200
Subject: [PATCH 5/9] typos cloud-setup.mdx
---
docs/appkit/javascript/notifications/cloud-setup.mdx | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/appkit/javascript/notifications/cloud-setup.mdx b/docs/appkit/javascript/notifications/cloud-setup.mdx
index 9d366cb8e..0f18c8cf5 100644
--- a/docs/appkit/javascript/notifications/cloud-setup.mdx
+++ b/docs/appkit/javascript/notifications/cloud-setup.mdx
@@ -15,7 +15,7 @@ It is important to understand what domain you are using for your project as you
You can pick 1 domain and this is configured in the Dapp URL field of the Notify API section of the [WalletConnect Cloud](https://cloud.walletconnect.com). You may change your domain at any time, as long as you properly host the new `did.json` file there. Note that only one project may use a given domain at the same time.
-During development it is optional to use your production domain for testing. Instead, you can use a staging domain, or even a entirely separate domain e.g. Vercel test site. However, once you move to production you will need to update your domain to your production domain and host a new file there.
+During development it is optional to use your production domain for testing. Instead, you can use a staging domain, or even an entirely separate domain e.g. Vercel test site. However, once you move to production you will need to update your domain to your production domain and host a new file there.
Note that the file must be hosted on a real, publicly accessible, domain in order to verify its legitimacy. The use of `localhost` or other local addresses is not allowed.
From 330e795055f15fa41e61f0bb5b62a6201813ac61 Mon Sep 17 00:00:00 2001
From: Dmytrol <46675332+Dimitrolito@users.noreply.github.com>
Date: Tue, 10 Dec 2024 15:42:05 +0200
Subject: [PATCH 6/9] typos from-anza-adapter-react.mdx
---
docs/appkit/migration/from-anza-adapter-react.mdx | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/appkit/migration/from-anza-adapter-react.mdx b/docs/appkit/migration/from-anza-adapter-react.mdx
index 771b6e5e7..bf565be8f 100644
--- a/docs/appkit/migration/from-anza-adapter-react.mdx
+++ b/docs/appkit/migration/from-anza-adapter-react.mdx
@@ -83,7 +83,7 @@ createWeb3Modal({
})
```
:::info
-Email an social logins are enabled by default.
+Email a social logins are enabled by default.
:::
From f3e8cddae2a86bcc51502ca0d226ef4595a7b0dd Mon Sep 17 00:00:00 2001
From: Dmytrol <46675332+Dimitrolito@users.noreply.github.com>
Date: Tue, 10 Dec 2024 15:43:54 +0200
Subject: [PATCH 7/9] typos cloud-setup.mdx
---
docs/appkit/react/notifications/cloud-setup.mdx | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/appkit/react/notifications/cloud-setup.mdx b/docs/appkit/react/notifications/cloud-setup.mdx
index 36507e4bb..c1d235eb9 100644
--- a/docs/appkit/react/notifications/cloud-setup.mdx
+++ b/docs/appkit/react/notifications/cloud-setup.mdx
@@ -15,7 +15,7 @@ It is important to understand what domain you are using for your project as you
You can pick 1 domain and this is configured in the Dapp URL field of the Notify API section of the [WalletConnect Cloud](https://cloud.walletconnect.com). You may change your domain at any time, as long as you properly host the new `did.json` file there. Note that only one project may use a given domain at the same time.
-During development it is optional to use your production domain for testing. Instead, you can use a staging domain, or even a entirely separate domain e.g. Vercel test site. However, once you move to production you will need to update your domain to your production domain and host a new file there.
+During development it is optional to use your production domain for testing. Instead, you can use a staging domain, or even an entirely separate domain e.g. Vercel test site. However, once you move to production you will need to update your domain to your production domain and host a new file there.
Note that the file must be hosted on a real, publicly accessible, domain in order to verify its legitimacy. The use of `localhost` or other local addresses is not allowed.
From c89e361d3afdb268a13fc1cb451decd39d788504 Mon Sep 17 00:00:00 2001
From: Dmytrol <46675332+Dimitrolito@users.noreply.github.com>
Date: Tue, 10 Dec 2024 15:44:32 +0200
Subject: [PATCH 8/9] typos options.mdx
---
docs/appkit/unity/core/options.mdx | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/appkit/unity/core/options.mdx b/docs/appkit/unity/core/options.mdx
index 351753c94..24e1951b0 100644
--- a/docs/appkit/unity/core/options.mdx
+++ b/docs/appkit/unity/core/options.mdx
@@ -70,7 +70,7 @@ To enable Web3Modal to detect wallets installed on mobile devices, you need to m
Wallet detection may produce inaccurate results on iOS Simulator. It is recommended to test on a real device.
1. Make an iOS build.
- 2. In the generated Xcode project, find `Info.plist` file and open it with a external editor (i.e. not Xcode).
+ 2. In the generated Xcode project, find `Info.plist` file and open it with an external editor (i.e. not Xcode).
3. Locate or create `LSApplicationQueriesSchemes` section.
4. Add the desired wallet schemes as string entries within the ``. These schemes represent the wallets you want to detect.
From 87ef3191b8118d39069bcefdb62f3f2841c7f7dc Mon Sep 17 00:00:00 2001
From: Dmytrol <46675332+Dimitrolito@users.noreply.github.com>
Date: Tue, 10 Dec 2024 15:45:12 +0200
Subject: [PATCH 9/9] typos cloud-setup.mdx
---
docs/appkit/vue/notifications/cloud-setup.mdx | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/appkit/vue/notifications/cloud-setup.mdx b/docs/appkit/vue/notifications/cloud-setup.mdx
index 36507e4bb..c1d235eb9 100644
--- a/docs/appkit/vue/notifications/cloud-setup.mdx
+++ b/docs/appkit/vue/notifications/cloud-setup.mdx
@@ -15,7 +15,7 @@ It is important to understand what domain you are using for your project as you
You can pick 1 domain and this is configured in the Dapp URL field of the Notify API section of the [WalletConnect Cloud](https://cloud.walletconnect.com). You may change your domain at any time, as long as you properly host the new `did.json` file there. Note that only one project may use a given domain at the same time.
-During development it is optional to use your production domain for testing. Instead, you can use a staging domain, or even a entirely separate domain e.g. Vercel test site. However, once you move to production you will need to update your domain to your production domain and host a new file there.
+During development it is optional to use your production domain for testing. Instead, you can use a staging domain, or even an entirely separate domain e.g. Vercel test site. However, once you move to production you will need to update your domain to your production domain and host a new file there.
Note that the file must be hosted on a real, publicly accessible, domain in order to verify its legitimacy. The use of `localhost` or other local addresses is not allowed.