fix vale issues

yashovardhan · yashovardhan · commit e2f9a4863863 · 2026-05-12T17:40:54.000+05:30
diff --git a/embedded-wallets/sdk/flutter/advanced/custom-authentication.mdx b/embedded-wallets/sdk/flutter/advanced/custom-authentication.mdx
@@ -653,7 +653,7 @@ final Web3AuthResponse response = await Web3AuthFlutter.login(
 
 ### Aggregate verifier example
 
-You can use aggregate verifier to combine multiple login methods to get the same address for the users regardless of their login providers. For example, combining a Google and email passwordless login, or Google and GitHub via Auth0 to access the same address for your user.
+You can use aggregate verifier to combine multiple sign-in methods to get the same address for the users regardless of their sign-in providers. For example, combining a Google and email passwordless sign-in, or Google and GitHub via Auth0 to access the same address for your user.
 
 ```dart
 // focus-start
diff --git a/embedded-wallets/sdk/flutter/usage/request.mdx b/embedded-wallets/sdk/flutter/usage/request.mdx
@@ -4,7 +4,7 @@ sidebar_label: Send requests
 description: 'Web3Auth Flutter SDK - request Function | Embedded Wallets'
 ---
 
-The `request` method facilitates the use of templated transaction screens for signing transactions. The method will return [SignResponse](#signresponse). It can be used to sign transactions for any EVM chain and screens can be whitelabeled to your branding.
+The `request` method facilitates the use of prebuilt transaction screens for signing transactions. The method will return [SignResponse](#signresponse). It can be used to sign transactions for any EVM chain and screens can be customized to match your branding.
 
 Please check the list of [JSON RPC methods](https://docs.metamask.io/wallet/reference/json-rpc-api/), noting that the request method currently supports only the signing methods.
 
diff --git a/embedded-wallets/sdk/ios/README.mdx b/embedded-wallets/sdk/ios/README.mdx
@@ -42,13 +42,13 @@ Install the Web3Auth iOS SDK using one of the following methods:
    https://github.com/Web3Auth/web3auth-swift-sdk
    ```
 
-   From the **Dependency Rule** dropdown, select E**xact Version** and enter **11.1.0** as the version.
+   From the **Dependency Rule** dropdown, select **Exact Version** and enter **11.1.0** as the version.
 
 3. When finished, Xcode will automatically begin resolving and downloading your dependencies in the background.
 
-### Cocoapods
+### CocoaPods
 
-To install the Embedded Wallets SDK using Cocoapods, follow the steps:
+To install the Embedded Wallets SDK using CocoaPods, follow the steps:
 
 1. Open the Podfile, and add the Embedded Wallets pod:
 
diff --git a/embedded-wallets/sdk/ios/advanced/README.mdx b/embedded-wallets/sdk/ios/advanced/README.mdx
@@ -88,7 +88,7 @@ Control how long users stay authenticated and how sessions persist. The session
 
 **Key Configuration Options:**
 
-- `sessionTime` - Session duration in seconds. Controls how long users remain authenticated before needing to log in again.
+- `sessionTime` - Session duration in seconds. Controls how long users remain authenticated before needing to sign in again.
   - Minimum: 1 second (`1`).
   - Maximum: 30 days (`86400 * 30`).
   - Default: 7 days (`86400 * 7`).
@@ -104,11 +104,11 @@ web3Auth = Web3Auth(W3AInitParams(
 
 ## Custom authentication methods
 
-Control the login options presented to your users. For detailed configuration options and implementation examples, see the [custom authentication](./custom-authentication.mdx) section.
+Control the sign-in options presented to your users. For detailed configuration options and implementation examples, see the [custom authentication](./custom-authentication.mdx) section.
 
 ## UI customization
 
-Create a seamless brand experience by customizing the Web3Auth Login Screens to match your application's design. For complete customization options, refer to the [Whitelabeling and UI Customization](./whitelabel.mdx) section.
+Create a seamless brand experience by customizing the Web3Auth Sign-in Screens to match your application's design. For complete customization options, refer to the [Whitelabeling and UI Customization](./whitelabel.mdx) section.
 
 ## Multi-Factor Authentication
 
diff --git a/embedded-wallets/sdk/ios/advanced/custom-authentication.mdx b/embedded-wallets/sdk/ios/advanced/custom-authentication.mdx
@@ -40,7 +40,7 @@ Consequentially, you will see the terms **"Verifier ID"** and **"Aggregate Verif
 
 :::
 
-To use custom authentication (using supported Social providers or Login providers like Auth0, AWS Cognito, Firebase, or your own custom JWT login), you can add the configuration using the `loginConfig` parameter during the initialization.
+To use custom authentication (using supported Social providers or Sign-in providers like Auth0, AWS Cognito, Firebase, or your own custom JWT sign-in), you can add the configuration using the `loginConfig` parameter during the initialization.
 
 The `loginConfig` parameter is a key value map. The key should be one of the `Web3AuthProvider` in its string form, and the value should be a `W3ALoginConfig` struct.
 
@@ -120,15 +120,15 @@ public enum TypeOfLogin: String, Codable {
 ### Usage
 
 <Tabs
-  defaultValue="google"
+  defaultValue="Google"
   values={[
-    { label: "Google", value: "google" },
-    { label: "Facebook", value: "facebook" },
+    { label: "Google", value: "Google" },
+    { label: "Facebook", value: "Facebook" },
     { label: "JWT", value: "jwt" },
   ]}
 >
 
-<TabItem value="google">
+<TabItem value="Google">
 
 ```swift
 import Web3Auth
@@ -152,7 +152,7 @@ let web3Auth = try await Web3Auth(
 
 </TabItem>
 
-<TabItem value="facebook">
+<TabItem value="Facebook">
 
 ```swift
 import Web3Auth
@@ -203,9 +203,9 @@ let web3Auth = try await Web3Auth(
 
 </Tabs>
 
-## Configure extra login options
+## Configure extra sign-in options
 
-Additional to the login config during initialization, you can pass extra options to the `login` function to configure the login flow for cases requiring additional info for enabling login. The `ExtraLoginOptions` accepts the following parameters.
+Additional to the sign-in config during initialization, you can pass extra options to the `login` function to configure the sign-in flow for cases requiring additional info for enabling sign-in. The `ExtraLoginOptions` accepts the following parameters.
 
 ### Parameters
 
@@ -279,16 +279,16 @@ public struct ExtraLoginOptions: Codable {
 <Tabs defaultValue="auth0"
   values={[
     { label: "Auth0", value: "auth0" },
-    { label: "Custom JWT", value: "byoj" },
+    { label: "Custom JWT", value: "custom-jwt" },
     { label: "Email Passwordless", value: "email-passwordless" },
     { label: "SMS Passwordless", value: "sms-passwordless" },
   ]}
 >
 
 <TabItem value="auth0">
-Auth0 has a special login flow, called the SPA flow. This flow requires a `client_id` and `domain`
+Auth0 has a special sign-in flow, called the SPA flow. This flow requires a `client_id` and `domain`
 to be passed, and Web3Auth will get the JWT `id_token` from Auth0 directly. You can pass these
-configurations in the `ExtraLoginOptions` object in the login function.
+configurations in the `ExtraLoginOptions` object in the sign-in function.
 
 ```swift
 import
@@ -327,7 +327,7 @@ let result = try await web3Auth.login(
 
 </TabItem>
 
-<TabItem value="byoj">
+<TabItem value="custom-jwt">
 If you're using any other provider like Firebase, AWS Cognito or deploying your own Custom JWT
 server, you need to put the JWT token into the `id_token` field of the `extraLoginOptions`,
 additionally, you need to pass over the `domain` field as well, which is mandatory. If you don't
@@ -366,8 +366,8 @@ let result = await web3Auth.login(
 </TabItem>
 
 <TabItem value="email-passwordless">
-To use the email passwordless login, you need to put the email into the `login_hint` parameter of
-the `ExtraLoginOptions`. By default, the login flow will be `code` flow, if you want to use the
+To use the email passwordless sign-in, you need to put the email into the `login_hint` parameter of
+the `ExtraLoginOptions`. By default, the sign-in flow will be `code` flow, if you want to use the
 `link` flow, you need to put `flow_type` into the `additionalParams` parameter of the
 `ExtraLoginOptions`.
 
@@ -393,7 +393,7 @@ let result = try await web3Auth.login(
 
 <TabItem value="sms-passwordless">
 
-To use the SMS Passwordless login, send the phone number as the `login_hint` parameter of the `ExtraLoginOptions`. Please ensure the phone number takes the format:
+To use the SMS Passwordless sign-in, send the phone number as the `login_hint` parameter of the `ExtraLoginOptions`. Please ensure the phone number takes the format:
 +\{country_code}-\{phone_number}, that is, (+91-09xx901xx1).
 
 ```swift
@@ -419,7 +419,7 @@ let result = try await web3Auth.login(W3ALoginParams(
 
 ### Aggregate verifier example
 
-You can use aggregate verifier to combine multiple login methods to get the same address for the users regardless of their login providers. For example, combining a Google and email passwordless login, or Google and GitHub via Auth0 to access the same address for your user.
+You can use aggregate verifier to combine multiple sign-in methods to get the same address for the users regardless of their sign-in providers. For example, combining a Google and email passwordless sign-in, or Google and GitHub via Auth0 to access the same address for your user.
 
 ```swift
 import Web3Auth
diff --git a/embedded-wallets/sdk/ios/usage/launch-wallet-services.mdx b/embedded-wallets/sdk/ios/usage/launch-wallet-services.mdx
@@ -7,11 +7,11 @@ description: 'Web3Auth iOS SDK - launchWalletServices | Embedded Wallets'
 import TabItem from '@theme/TabItem'
 import Tabs from '@theme/Tabs'
 
-The `launchWalletServices` method launches a WebView which allows you to use the templated wallet UI services. The method takes `ChainConfig` as the required input. Wallet Services is currently only available for EVM chains.
+The `launchWalletServices` method launches a WebView which allows you to use the prebuilt wallet UI services. The method takes `ChainConfig` as the required input. Wallet Services is currently only available for EVM chains.
 
 :::note
 
-Access to Wallet Services is gated. You can use this feature in `sapphire_devnet` for free. The minimum [pricing plan](https://web3auth.io/pricing.html) to use this feature in a production environment is the **Scale Plan**.
+Access to Wallet Services is gated. You can use this feature in `sapphire_devnet` at no cost. The minimum [pricing plan](https://web3auth.io/pricing.html) to use this feature in a production environment is the **Scale Plan**.
 
 :::
 
diff --git a/embedded-wallets/sdk/ios/usage/request.mdx b/embedded-wallets/sdk/ios/usage/request.mdx
@@ -4,7 +4,7 @@ sidebar_label: Send requests
 description: 'Web3Auth iOS SDK - request | Embedded Wallets'
 ---
 
-The `request` method facilitates the use of templated transaction screens for signing transactions. The method will return [SignResponse](#signresponse). It can be used to sign transactions for any EVM chain and screens can be whitelabeled to your branding.
+The `request` method facilitates the use of prebuilt transaction screens for signing transactions. The method will return [SignResponse](#signresponse). It can be used to sign transactions for any EVM chain and screens can be customized to match your branding.
 
 Please check the list of [JSON RPC methods](https://docs.metamask.io/wallet/reference/json-rpc-api/), noting that the request method currently supports only the signing methods.
 
diff --git a/embedded-wallets/sdk/js/advanced/README.mdx b/embedded-wallets/sdk/js/advanced/README.mdx
@@ -56,13 +56,13 @@ Control how long users stay authenticated and how sessions persist.
 **Key Configuration Options:**
 
 - `sessionTime` - Session duration in seconds. Controls how long users remain authenticated before
-  needing to log in again.
+  needing to sign in again.
   - Minimum: 1 second (`1`).
   - Maximum: 30 days (`86400 * 30`).
   - Default: 7 days (`86400 * 7`).
 - `storageType` - Storage location for authentication state. Options:
-  - `"local"`: Persists across browser tabs and browser restarts (localStorage)
-  - `"session"`: Persists only in current tab, cleared when tab closes (sessionStorage)
+  - `"local"`: Persists across browser tabs and browser restarts (`localStorage`)
+  - `"session"`: Persists only in current tab, cleared when tab closes (`sessionStorage`)
 
 ```tsx
 const web3AuthOptions = {
@@ -88,7 +88,7 @@ section.
 
 ## Custom authentication methods
 
-Control the login options presented to your users and how they're displayed in the modal. For
+Control the sign-in options presented to your users and how they're displayed in the modal. For
 detailed configuration options and implementation examples, see the
 [custom authentication](./custom-authentication.mdx) section.
 
diff --git a/embedded-wallets/sdk/js/advanced/custom-authentication.mdx b/embedded-wallets/sdk/js/advanced/custom-authentication.mdx
@@ -36,7 +36,7 @@ The basic custom authentication is available directly in the modal. You can conf
 
 :::note
 
-You can only configure implicit login via modal, for JWT-based logins, you need to create your own UI and use the `connectTo` function.
+You can only configure implicit sign-in via modal, for JWT-based logins, you need to create your own UI and use the `connectTo` function.
 
 :::
 
@@ -153,12 +153,12 @@ await web3auth.init()
 
 ## Advanced custom authentication
 
-The more advanced custom authentication is available via the `connectTo` function. This allows you to any service you want and tie it to your Web3Auth Integration. **This method allows you to make Web3Auth totally invisible to your end users and have a fully whitelabeled experience all across.**
+The more advanced custom authentication is available via the `connectTo` function. This allows you to any service you want and tie it to your Web3Auth Integration. **This method allows you to make Web3Auth totally invisible to your end users and have a fully customized experience all across.**
 
 You can utilise this function to enable multiple types of connections like:
 
-- Implicit Login connections
-- JWT login connections
+- Implicit Sign-in connections
+- JWT sign-in connections
 - Grouped auth connections
 
 <details>
