thirdweb-dev · jnsdls · May 7, 2025 · May 7, 2025
@@ -345,7 +345,7 @@ export const CreateListingsForm: React.FC<CreateListingsFormProps> = ({
             const promise = sendAndConfirmTx.mutateAsync(approveTx);
             toast.promise(promise, {
               loading: "Approving NFT for listing",
-              success: "NFT approved succesfully",
+              success: "NFT approved successfully",
               error: "Failed to approve NFT",
             });
             await promise;

@@ -38,7 +38,7 @@ When a user signs into an application using their email or social logins for the
 
 ### General Usage
 
-- When users interact with their wallet via the the enclave, all communications are encrypted and only the legitimate user can access their wallet.
+- When users interact with their wallet via the enclave, all communications are encrypted and only the legitimate user can access their wallet.
 - All traffic is encrypted with TLS and HSTS. Services are run in private VPCs on AWS and accessible only from a single entry point via our Cloudflare DNS.
 - Applications can [link multiple authentication methods](/connect/in-app-wallet/guides/link-multiple-profiles) to the same wallet. Any of these methods can be used to authenticate into the users wallet.
 

@@ -38,7 +38,7 @@ App developers can issue `Account` smart accounts programmatically by deploying
 
 <br />
 
-<Callout title="Issue accounts programatically" variant="info" >
+<Callout title="Issue accounts programmatically" variant="info" >
 
 If you intend to issue accounts programmatically using a custom factory contract, you must do the following:
 

@@ -32,7 +32,7 @@ An upgrade to the features of `ManagedAccount` applies to **all** `ManagedAccoun
 
 <br />
 
-<Callout title="Issue accounts programatically" variant="info">
+<Callout title="Issue accounts programmatically" variant="info">
 
 If you intend to issue accounts programmatically using a custom factory contract, you must do the following:
 

@@ -20,7 +20,7 @@ Ecosystem Wallets support a variety of login methods:
 - Custom Auth (Generic Auth Endpoint)
 - Guest (Onboard easily, link other accounts later)
 - Backend (Server Wallets)
-- Siwe (Login with a seperate wallet supported by the SDK)
+- Siwe (Login with a separate wallet supported by the SDK)
 - SiweExternal (Login with an external wallet that only supports web using a browser loading a static thirdweb React page temporarily)
 
 ## Usage
@@ -104,7 +104,7 @@ An instance of `ThirdwebClient`.
 
 ### ecosystemId (required)
 
-The ID of the ecosyste wallet you created on the dashboard.
+The ID of the ecosystem wallet you created on the dashboard.
 
 ### ecosystemPartnerId (optional)
 

@@ -20,7 +20,7 @@ In-App Wallets support a variety of login methods:
 - Custom Auth (Generic Auth Endpoint)
 - Guest (Onboard easily, link other accounts later)
 - Backend (Server Wallets)
-- Siwe (Login with a seperate wallet supported by the SDK)
+- Siwe (Login with a separate wallet supported by the SDK)
 - SiweExternal (Login with an external wallet that only supports web using a browser loading a static thirdweb React page temporarily)
 
 ## Usage

@@ -12,7 +12,7 @@ You can quickly create a new project with the thirdweb CLI
 npx thirdweb create app
 ```
 
-or clone the the Next.js or Vite starter repo:
+or clone the Next.js or Vite starter repo:
 
 <Stack>
 <GithubTemplateCard

@@ -60,7 +60,7 @@ You can quickly create a new project with the thirdweb CLI
 npx thirdweb create app
 ```
 
-or clone the the Next.js or Vite starter repo:
+or clone the Next.js or Vite starter repo:
 
 <Stack>
 <GithubTemplateCard

@@ -111,7 +111,7 @@ Learn how to migrate to thirdweb's ConnectButton component from [RainbowKit](htt
 
 <hr/>
 
-### Initalization
+### Initialization
 
 #### RainbowKit
 

@@ -19,4 +19,4 @@ const contract = getContract({
 });
 ```
 
-Contracts defined this way are lightweight and can be exported as consts accross your application to read or write to it.
+Contracts defined this way are lightweight and can be exported as consts across your application to read or write to it.
@@ -25,7 +25,7 @@ Ecosystem Wallets support a variety of login methods:
 - Custom Auth (Generic Auth Endpoint)
 - Guest (Onboard easily, link other accounts later)
 - Backend (Server Wallets)
-- Siwe (Login with a seperate wallet supported by the SDK)
+- Siwe (Login with a separate wallet supported by the SDK)
 - SiweExternal (Login with an external wallet that only supports web using a browser loading a static thirdweb React page temporarily)
 
 ### Login with Email

@@ -23,7 +23,7 @@ In-App Wallets support a variety of login methods:
 - Custom Auth (Generic Auth Endpoint)
 - Guest (Onboard easily, link other accounts later)
 - Backend (Server Wallets)
-- Siwe (Login with a seperate wallet supported by the SDK)
+- Siwe (Login with a separate wallet supported by the SDK)
 - SiweExternal (Login with an external wallet that only supports web using a browser loading a static thirdweb React page temporarily)
 
 ### Login with Email

@@ -86,7 +86,7 @@ export async function fetchConstructorParams(
       ),
     ];
 
-    // regex finds the LAST occurence of solc metadata bytes, result always in same position
+    // regex finds the LAST occurrence of solc metadata bytes, result always in same position
     // TODO: we currently don't handle error string embedded in the bytecode, need to strip ascii (upgradeableProxy) in patterns[2]
     // https://etherscan.io/address/0xee6a57ec80ea46401049e92587e52f5ec1c24785#code
     if (matches?.[0]?.[2]) {

@@ -178,7 +178,7 @@ async function getTransactionsForMaketplaceV3(options: {
   client: ThirdwebClient;
 }): Promise<DeployTransactionResult[]> {
   const { chain, client } = options;
-  const WETHAdress = await computePublishedContractAddress({
+  const WETHAddress = await computePublishedContractAddress({
     chain,
     client,
     contractId: "WETH9",
@@ -195,7 +195,7 @@ async function getTransactionsForMaketplaceV3(options: {
       chain,
       client,
       contractId: "DirectListingsLogic",
-      constructorParams: { _nativeTokenWrapper: WETHAdress },
+      constructorParams: { _nativeTokenWrapper: WETHAddress },
     }).then((c) =>
       c
         ? null
@@ -205,7 +205,7 @@ async function getTransactionsForMaketplaceV3(options: {
       chain,
       client,
       contractId: "EnglishAuctionsLogic",
-      constructorParams: { _nativeTokenWrapper: WETHAdress },
+      constructorParams: { _nativeTokenWrapper: WETHAddress },
     }).then((c) =>
       c
         ? null
@@ -233,7 +233,7 @@ async function getTransactionsForDynamicContract(options: {
   deployMetadata: FetchDeployMetadataResult;
 }): Promise<DeployTransactionResult[]> {
   const { chain, client } = options;
-  const WETHAdress = await computePublishedContractAddress({
+  const WETHAddress = await computePublishedContractAddress({
     chain,
     client,
     contractId: "WETH9",
@@ -255,7 +255,7 @@ async function getTransactionsForDynamicContract(options: {
             contractId: e.extensionName,
             publisher: e.publisherAddress,
             version: e.extensionVersion || "latest",
-            constructorParams: { _nativeTokenWrapper: WETHAdress },
+            constructorParams: { _nativeTokenWrapper: WETHAddress },
           }).then((c) =>
             c
               ? null

@@ -55,7 +55,7 @@ export interface AccountBalanceProps extends Omit<TextProps, "children"> {
    * If not passed, the component will return `null`.
    *
    * You can/should pass a descriptive text/component to this prop, indicating that the
-   * balance was not fetched succesfully
+   * balance was not fetched successfully
    * @example
    * ```tsx
    * <AccountBalance

@@ -25,7 +25,7 @@ export interface WalletNameProps extends Omit<TextProps, "children"> {
    * If not passed, the component will return `null`.
    *
    * You can/should pass a descriptive text/component to this prop, indicating that the
-   * name was not fetched succesfully
+   * name was not fetched successfully
    * @example
    * ```tsx
    * <WalletName fallbackComponent={<span>Failed to load</span>}

@@ -57,7 +57,7 @@ export interface AccountBalanceProps
    * If not passed, the component will return `null`.
    *
    * You can/should pass a descriptive text/component to this prop, indicating that the
-   * balance was not fetched succesfully
+   * balance was not fetched successfully
    * @example
    * ```tsx
    * <AccountBalance

@@ -45,7 +45,7 @@ export interface ChainNameProps
    * If not passed, the component will return `null`.
    *
    * You can/should pass a descriptive text/component to this prop, indicating that the
-   * name was not fetched succesfully
+   * name was not fetched successfully
    * @example
    * ```tsx
    * <ChainName fallbackComponent={<span>Failed to load</span>}

@@ -50,7 +50,7 @@ export interface TokenNameProps
    * If not passed, the component will return `null`.
    *
    * You can/should pass a descriptive text/component to this prop, indicating that the
-   * name was not fetched succesfully
+   * name was not fetched successfully
    * @example
    * ```tsx
    * <TokenName fallbackComponent={"Failed to load"}

@@ -50,7 +50,7 @@ export interface TokenSymbolProps
    * If not passed, the component will return `null`.
    *
    * You can/should pass a descriptive text/component to this prop, indicating that the
-   * symbol was not fetched succesfully
+   * symbol was not fetched successfully
    * @example
    * ```tsx
    * <TokenSymbol fallbackComponent={"Failed to load"}

@@ -27,7 +27,7 @@ export interface WalletNameProps
    * If not passed, the component will return `null`.
    *
    * You can/should pass a descriptive text/component to this prop, indicating that the
-   * name was not fetched succesfully
+   * name was not fetched successfully
    * @example
    * ```tsx
    * <WalletName fallbackComponent={<span>Failed to load</span>}

@@ -51,7 +51,7 @@ function InAppWalletConnectUI(props: {
     return <LoadingScreen />;
   }
 
-  // if the the modal starts out with the wallet's connect ui instead of wallet selector - going back to main screen requires staying on the same component and clearing the selection data
+  // if the modal starts out with the wallet's connect ui instead of wallet selector - going back to main screen requires staying on the same component and clearing the selection data
   // otherwise, we go back to the wallet selector by calling props.goBack
   const goBackToMain = () => {
     if (initialScreen === props.wallet) {

@@ -104,7 +104,7 @@ export async function uploadBatchMobile(
           );
         }
 
-        return reject(new Error("Unknown upload error occured"));
+        return reject(new Error("Unknown upload error occurred"));
       });
 
       xhr.open("POST", `https://${getThirdwebDomains().storage}/ipfs/upload`);
-Original file line number
+Diff line change
@@ Expand Up @@
     <br />
-    <Callout title="Issue accounts programatically" variant="info" >
+    <Callout title="Issue accounts programmatically" variant="info" >
     If you intend to issue accounts programmatically using a custom factory contract, you must do the following:
@@ Expand Down @@