feat: added walletkit updates

content/applications/appkit/howto/staking.mdx

@@ -7,7 +7,7 @@ Quote a stake or unstake, build the transaction, and send it through the connect
 
 ## How it works
 
-The `StakingManager` routes each quote and build call to a single registered staking provider — by default the first one you registered, or the one you pass as `providerId`. `setDefaultProvider` on the manager overrides the default; an unknown `providerId` throws. A quote describes the intent (`direction: 'stake' | 'unstake'`, `amount`, optional `unstakeMode`), and `useBuildStakeTransaction` turns an accepted quote into a `TransactionRequest`.
+The `StakingManager` routes each quote call and each build call to a single registered staking provider — by default the first one you registered, or the one you pass as `providerId`. `setDefaultProvider` on the manager overrides the default; an unknown `providerId` throws. A quote describes the intent (`direction: 'stake' | 'unstake'`, `amount`, optional `unstakeMode`), and `useBuildStakeTransaction` turns an accepted quote into a `TransactionRequest`.
 
 The protocol shape — derivative jetton, unstake modes, settlement timing, pool model — is provider-specific. Tonstakers, the bundled provider, issues `tsTON` and supports `INSTANT`, `WHEN_AVAILABLE`, and `ROUND_END` unstake modes. Read the user's staked-token balance with `useStakedBalance`, or query the jetton balance directly. `apy` and `instantUnstakeAvailable` from `useStakingProviderInfo` are provider-supplied display data, not guarantees of future yield or withdrawal timing.
 

content/applications/walletkit/android/events.mdx

@@ -39,7 +39,7 @@ walletKit.removeEventsHandler(eventsHandler)
 
 ### Establishing connection with dApp
 
-To establish a connection with a dApp, one needs a connection request URL from any source: copy/paste, QR code, deep link, etc. Send it to the WalletKit to initiate a connection request.
+To establish a connection with a dApp, one needs a connection request URL from any source: copy/paste, QR code, deep link, etc. Send it to WalletKit to initiate a connection request.
 
 ```kotlin
 wallet.connect(/* connection url */)

content/applications/walletkit/android/wallets.mdx

@@ -4,7 +4,7 @@ sidebarTitle: "Manage wallets"
 ---
 
 <Callout type="tip">
-  Initialize the WalletKit before managing wallets. See the [initialization guide](/applications/walletkit/android/init) for details.
+  Initialize WalletKit before managing wallets. See the [initialization guide](/applications/walletkit/android/init) for details.
 </Callout>
 
 The SDK provides a comprehensive API for creating, retrieving, and managing wallets. All wallet operations follow a three-step pattern.

content/applications/walletkit/android/webview.mdx

@@ -4,7 +4,7 @@ sidebarTitle: "Inject WebView"
 ---
 
 <Callout type="tip">
-  Initialize the WalletKit before injecting it into WebView. See the [initialization guide](/applications/walletkit/android/init) for details.
+  Initialize WalletKit before injecting it into WebView. See the [initialization guide](/applications/walletkit/android/init) for details.
 </Callout>
 
 Injecting WalletKit into WebView allows integrating the wallet service with a dApp running in a native WebView and handling its events.

content/applications/walletkit/ios/events.mdx

@@ -37,7 +37,7 @@ try await walletKit.remove(eventsHandler: eventsHandler)
 
 ### Establishing connection with dApp
 
-To establish a connection with a dApp, one needs a connection request URL from any source: copy/paste, QR code, deep link, etc. Send it to the WalletKit to initiate a connection request.
+To establish a connection with a dApp, one needs a connection request URL from any source: copy/paste, QR code, deep link, etc. Send it to WalletKit to initiate a connection request.
 
 ```swift
 try await walletKit.connect(url: /* connection url */)

content/applications/walletkit/ios/init.mdx

@@ -56,7 +56,7 @@ Once you have a configuration, create an instance of the kit:
 ```swift
 import TONWalletKit
 
-// Instructs how to store intermediate events and other data from the WalletKit.
+// Instructs how to store intermediate events and other data from WalletKit.
 let storage: TONWalletKitStorageType = .memory // .keychain or .custom(/* custom storage */)
 
 // Instance

content/applications/walletkit/ios/wallets.mdx

@@ -4,7 +4,7 @@ sidebarTitle: "Manage wallets"
 ---
 
 <Callout type="tip">
-  Initialize the WalletKit before managing wallets. See the [initialization guide](/applications/walletkit/ios/init) for details.
+  Initialize WalletKit before managing wallets. See the [initialization guide](/applications/walletkit/ios/init) for details.
 </Callout>
 
 The SDK provides a comprehensive API for creating, retrieving, and managing wallets. All wallet operations follow a three-step pattern.

content/applications/walletkit/ios/webview.mdx

@@ -4,7 +4,7 @@ sidebarTitle: "Inject into WebView"
 ---
 
 <Callout type="tip">
-  Initialize the WalletKit before injecting it into WebView. See the [initialization guide](/applications/walletkit/ios/init) for details.
+  Initialize WalletKit before injecting it into WebView. See the [initialization guide](/applications/walletkit/ios/init) for details.
 </Callout>
 
 Injecting WalletKit into WebView allows integrating the wallet service with a dApp running in a native WebView and handling its events.

content/applications/walletkit/overview.mdx

@@ -54,7 +54,7 @@ Explore the complete demo wallets on GitHub:
 
 You can integrate your custodial wallet with TON or partially build a basic wallet from scratch.
 
-To get started, select your framework or environment and install WalletKit:
+To get started, select your framework and follow usage recipes in the respective sections:
 
 <Columns cols={3}>
   <Card
@@ -73,8 +73,6 @@ To get started, select your framework or environment and install WalletKit:
   />
 </Columns>
 
-Then, follow usage recipes in the respective sections.
-
 ## See also
 
 To implement custom wallet logic, you may need to explore in-depth topics: