renamed tabs and files

Author: saminacodes

apps/portal/src/app/Header.tsx

@@ -33,15 +33,15 @@ import { ThirdwebIcon } from "../icons/thirdweb";
 const links = [
   {
     href: "/connect",
-    name: "Connect",
+    name: "Wallets",
   },
   {
     href: "/pay",
-    name: "Bridge",
+    name: "Payments",
   },
   {
     href: "/engine",
-    name: "Engine",
+    name: "Transactions",
   },
   {
     href: "/contracts",
@@ -181,7 +181,7 @@ const sdkLinks = [
 const supportLinks = [
   {
     href: "/knowledge-base",
-    name: "Get thirdweb support",
+    name: "Articles",
   },
   {
     href: "/account",
@@ -216,6 +216,21 @@ export function Header() {
         </div>
 
         <div className="flex items-center gap-3">
+          
+          <div className="hidden xl:block">
+            <Link
+              className="text-foreground"
+              href="https://github.com/thirdweb-dev"
+              target="_blank"
+            >
+              <GithubIcon className="mx-3 size-6" />
+            </Link>
+          </div>
+                    
+          <div className="hidden xl:block">
+            <ThemeSwitcher className="border-none bg-transparent" />
+          </div>
+
           <div className="hidden xl:block">
             <DocSearch variant="search" />
           </div>
@@ -231,20 +246,6 @@ export function Header() {
             </Button>
           </div>
 
-          <div className="hidden xl:block">
-            <ThemeSwitcher className="border-none bg-transparent" />
-          </div>
-
-          <div className="hidden xl:block">
-            <Link
-              className="text-foreground"
-              href="https://github.com/thirdweb-dev"
-              target="_blank"
-            >
-              <GithubIcon className="mx-3 size-6" />
-            </Link>
-          </div>
-
           <div className="flex items-center gap-1 xl:hidden">
             <ThemeSwitcher className="border-none bg-transparent" />
             <DocSearch variant="icon" />

apps/portal/src/app/connect/page.mdx

@@ -34,9 +34,9 @@ export const metadata = createMetadata({
 	},
 });
 
-# What is Connect?
+# Wallets
 
-Connect is the complete toolkit for connecting every user to your application. It features customizable onboarding flows, self-custodial in-app wallets, account abstraction, onramps, and a performant API to interact with the blockchain.
+Wallets is the complete toolkit for connecting every user to your application. It features customizable onboarding flows, self-custodial in-app wallets, account abstraction, onramps, and a performant API to interact with the blockchain.
 
 ## Live Playground
 
@@ -55,7 +55,7 @@ You can interact with the React SDK in the [Live Playground](https://playground.
 
 ## Quick starts
 
-Get started with Connect in your preferred language.
+Get started with Wallets in your preferred language.
 
 <Grid>
 	<SDKCard
@@ -78,7 +78,7 @@ Get started with Connect in your preferred language.
 	/>
 </Grid>
 
-## With Connect, you can
+## With Wallets, you can
 
 - **Connect to 500+ different wallet providers** with support for every EVM network
 - **Log in and authenticate your users** with customizable and secure [email, phone, passkeys and social login](https://portal.thirdweb.com/connect/in-app-wallet/overview) flows.
@@ -90,7 +90,7 @@ Get started with Connect in your preferred language.
 <Callout variant="info" title="Have you generated a client ID?">
 	<div className="flex flex-col gap-4 items-start">
 	<p>
-		You'll need a client ID to access Connect's free blockchain APIs, storage, and more.
+		You'll need a client ID to access the Wallet APIs, storage, and more.
 	</p>
 
 	<Button asChild variant='outline'>
@@ -102,7 +102,7 @@ Get started with Connect in your preferred language.
 
 ## Supported Chains
 
-Connect is supported on every EVM compatible chain. To view the full list, visit [thirdweb chainlist](https://thirdweb.com/chainlist).
+Wallets are supported on every EVM compatible chain. To view the full list, visit [thirdweb chainlist](https://thirdweb.com/chainlist).
 
 <DocImage src={SupportedChains} />
 

apps/portal/src/app/engine/v2/sidebar.tsx

@@ -163,5 +163,5 @@ export const sidebar: SideBar = {
       name: "FAQ",
     },
   ],
-  name: "Engine",
+  name: "Transactions",
 };

apps/portal/src/app/engine/v3/configure-wallets/smart-server-wallet/server-wallets/page.mdx renamed to apps/portal/src/app/engine/v3/configure-wallets/server-wallets/page.mdx

@@ -4,13 +4,13 @@ Smart server wallets are smart accounts designed to perform blockchain operation
 
 ## Benefits
 
-Smart server wallets are the recommended way to perform blockchain operations with Engine.
+Smart server wallets are the recommended way to perform blockchain operations with thirdweb Transactions.
 
 - **Managed Gas Fees**: Smart server wallets manage gas fees for you by automatically paying the fees using the payment method associated with your thirdweb account. You do not have to worry about topping up 
 gas funds on your server wallets. 
 - **Secure Key Management**: Smart server wallets are secured by Vault. Read more about Vault in the Security section below.
 - **Minimal Setup:** Smart server wallets can be created with just a few clicks directly in the thirdweb dashboard. No need to manage private keys or seed phrases or secure with external key management systems.
-- **Higher Throughput:** Smart server wallets can handle higher throughput by using multi-dimensional nonces. While Engine handles concurrent transactions through a queue system, smart wallets use parallelization to process multiple transactions at the same time, more efficiently than EOAs.
+- **Higher Throughput:** Smart server wallets can handle higher throughput by using multi-dimensional nonces. While thirdweb Transactions handles concurrent transactions through a queue system, smart wallets use parallelization to process multiple transactions at the same time, more efficiently than EOAs.
 
 ## Security
 
@@ -22,4 +22,3 @@ Keys used to manage server wallets including the admin key and access keys can b
 
 Smart server wallets cost a gas premium fee for each transaction completed on any mainnet as part of account abstraction fees. There are no gas charges for testnets. 
 [See pricing page for details](https://thirdweb.com/pricing).
-

apps/portal/src/app/engine/v3/configure-wallets/smart-server-wallet/page.mdx

@@ -1,20 +1,28 @@
 import { Callout, Details } from "@doc";
 
-# Engine FAQs
+# Transactions FAQs
 
-<Details summary="How is pricing calculated for Engine Cloud?">
-Pricing is calculated through the number of write requests (ex: /v1/write/contract) and sign requests (ex: /v1/sign/transaction) made through the Engine API. For requests costs, [see the thirdweb pricing page](https://thirdweb.com/pricing). Read requests made through Engine API are free, within the RPC limits/plan. 
+<Details summary="How is pricing calculated?">
+Pricing is calculated through the number of write requests (ex: /v1/write/contract) and sign requests (ex: /v1/sign/transaction) made through the Transactions API. For requests costs, [see the thirdweb pricing page](https://thirdweb.com/pricing). Read requests made through Transactions API are free, within the RPC limits/plan. 
 
-For transactions through server wallets paid through the user's thirdweb account, users will pay a 5% premium on the gas fee of each transaction completed on any mainnet as part of account abstraction fees. There are no gas charges for testnets.
+For requests through server wallets paid through the user's thirdweb account, users will pay a 5% premium on the gas fee of each request completed on any mainnet as part of account abstraction fees. There are no gas charges for testnets.
 
 **Please note: Legacy pricing plans may be subject to the 10% fee specified when signed up instead of 5%. [See pricing page for updated plans and benefits](https://thirdweb.com/pricing)** 
 
 The breakdown for usage and transaction fees can be found in your usage dashboard under the team overview. 
 </Details>
 
-<Details summary="Which chains does Engine Cloud support?">
-While in beta, Engine Cloud currently supports every non ZK EVM-compatible chain which includes support for Account Abstraction. See the current list of supported chains. 
+<Details summary="Which chains does Transactions Cloud support?">
+While in beta, Transactions Cloud currently supports every non ZK EVM-compatible chain which includes support for Account Abstraction. See the current list of supported chains. 
 
 If your chain is not listed, please [contact us](https://thirdweb.com/contact-us) to prioritize enabling support. 
 </Details>
 
+<Details summary="What is the difference between Transactions Cloud and Dedicated?">
+Cloud uses shared infrastructure that allows you to get started quickly with Transactions. It is ideal for most use cases and is the recommended way to use Transactions.
+
+Dedicated is a self-hosted version of Transactions that allows you to run Transactions on your own infrastructure. 
+
+It is ideal for high throughput applications, or applications that require complete control over their infrastructure.
+</Details>
+

apps/portal/src/app/engine/v3/faq/page.mdx

@@ -4,21 +4,21 @@ import SendTransaction from '../assets/send-transaction.png';
 
 # Get started
 
-Learn how to get started with thirdweb Engine. This guide will walk you through the steps to start building with thirdweb Engine by creating a Vault, server wallets, and integrating into your application.
+Learn how to get started with thirdweb Transactions. This guide will walk you through the steps to start building with thirdweb Transactions by creating a Vault, server wallets, and integrating into your application.
 
 ## Prerequisites
 
 - Create a thirdweb project. If you don't have a project yet, [learn how to create a project](/account/api-keys/create).
 
-## Engine Setup
+## Transactions Setup
 
 <Steps>
-	<Step title="Navigate to Engine">
-		In your project dashboard, navigate to **Engine** to get started.
+	<Step title="Navigate to Transactions">
+		In your project dashboard, navigate to **Transactions** to get started.
 	</Step>
 
 	<Step title="Create Vault">
-		Create a vault to manage your Engine's server wallets. After setup, you can manage your Vault to create additional access tokens or rotate admin keys.
+		Create a vault to manage your Transactions's server wallets. After setup, you can manage your Vault to create additional access tokens or rotate admin keys.
 
 		<Callout variant="info" title="Vault">
 			Vault is thirdweb's key management service designed to store smart server wallets non-custodially. [Learn more about Vault.](/vault)
@@ -27,10 +27,10 @@ Learn how to get started with thirdweb Engine. This guide will walk you through
 	</Step>
 
 	<Step title="Create Server Wallet">
-		Create a server wallet to perform blockchain actions with Engine.
+		Create a server wallet to perform blockchain actions with Transactions.
 
 		<Callout variant="info" title="Server Wallet">
-			Server wallets are smart wallets Engine uses to perform blockchain actions. [Learn more about server wallets](/engine/v2/configure-wallets/server-wallets).
+			Server wallets are smart wallets Transactions uses to perform blockchain actions. [Learn more about server wallets](/Transactions/v2/configure-wallets/server-wallets).
 		</Callout>
 	</Step>
 
@@ -42,7 +42,7 @@ Learn how to get started with thirdweb Engine. This guide will walk you through
 	</Step>
 
 	<Step title="Integrate with your app">
-		Integrate Engine into your application using the thirdweb SDK or Engine API. [View full API reference.](https://client.scalar.com/workspace/default/request/yq_Wx56PL4Ur6jOZsAOpA)
+		Integrate Transactions into your application using the thirdweb SDK or Transactions API. [View full API reference.](https://client.scalar.com/workspace/default/request/yq_Wx56PL4Ur6jOZsAOpA)
 
 		<Tabs defaultValue="curl">
 			<TabsList>
@@ -255,7 +255,7 @@ Learn how to get started with thirdweb Engine. This guide will walk you through
 			- The full catalog of extension functions
 			- The prepareContractCall function to encode your transactions
 			- The full account interface, predefined chains, and more
-			The SDK handles encoding your transactions, signing them to Engine and polling for status.
+			The SDK handles encoding your transactions, signing them to Transactions and polling for status.
 		</Callout>
 	</Step>
 </Steps>

apps/portal/src/app/engine/v3/get-started/page.mdx

@@ -22,6 +22,6 @@ export default async function Layout(props: { children: React.ReactNode }) {
 
 export const metadata = createMetadata({
   description:
-    "Engine is a backend HTTP server that calls smart contracts using your managed backend wallets.",
-  title: "Engine V3",
+    "thirdweb Transactions is a backend HTTP server that calls smart contracts using your managed backend wallets.",
+  title: "Transactions",
 });

apps/portal/src/app/engine/v3/layout.tsx

@@ -1,8 +1,8 @@
 import { Callout } from "@doc";
 
-# Migrating from Engine v2 to v3
+# Migrating from Transactions v2 to v3
 
-Learn how to migrate your applications from Engine v2 to Engine v3. We'll cover common operations and highlight the differences in API requests and authentication.
+Learn how to migrate your applications from v2 to v3. We'll cover common operations and highlight the differences in API requests and authentication.
 
 <Callout variant="info" title="Migrating Wallets">
 If you'd like to migrate your wallets from v2 to v3 to also be secured by [Vault](/vault) or thirdweb's key management service, please [contact us for assistance.](https://thirdweb.com/support) 
@@ -14,7 +14,7 @@ Migrating your contract write operations from v2 to v3 involves changes to the e
 
 #### OLD (v2)
 
-The v2 approach used your dedicated engine url, with a specific endpoint for each chain and contract and backend wallet address in the header.
+The v2 approach used your dedicated Transactions url, with a specific endpoint for each chain and contract and backend wallet address in the header.
 
 ```bash
 curl -X POST "<engine_url>/contract/<chain>/<contract_address>/write" \
@@ -173,9 +173,9 @@ curl https://engine.thirdweb.com/v1/read/contract \
 
 ## Extension functions
 
-Engine v2 has a large number of endpoints to do specific contract calls, like mintTo, claimTo, etc.
+V2 has a large number of endpoints to do specific contract calls, like mintTo, claimTo, etc.
 
-Engine v3 does not have these endpoints yet, but they are coming soon. In the meantime, if your backend is written in typescript, we recommend using the [thirdweb SDK](/references/typescript/v5/functions#extensions) to do these operations:
+V3 does not have these endpoints yet, but they are coming soon. In the meantime, if your backend is written in typescript, we recommend using the [thirdweb SDK](/references/typescript/v5/functions#extensions) to do these operations:
 
 ##### OLD (v2)
 
@@ -194,7 +194,7 @@ const response = await fetch(
     metadataWithSupply: {
         metadata: {
         name: "Acme Inc. Superfan",
-        description: "Created with thirdweb Engine",
+        description: "Created with thirdweb",
         image:
             "ipfs://QmciR3WLJsf2BgzTSjbG5zCxsrEQ8PqsHK7JWGWsDSNo46/nft.png",
         },
@@ -233,17 +233,17 @@ const transaction = mintTo({
   supply: 1n, // The quantity of NFTs to mint
   nft: {
     name: "Acme Inc. Superfan",
-    description: "Created with thirdweb Engine",
+    description: "Created with thirdweb",
     image:
       "ipfs://QmciR3WLJsf2BgzTSjbG5zCxsrEQ8PqsHK7JWGWsDSNo46/nft.png",
   },
 });
 
-// Enqueue the transaction via Engine
+// Enqueue the transaction
 const { transactionId } =
   await serverWallet.enqueueTransaction({
     transaction,
   });
 ```
 
-The entire thirdweb SDK is available to use with engine v3 in this manner using the [`Engine` namespace](/references/typescript/v5/functions#engine). Check the [thirdweb SDK docs](/references/typescript/v5/functions#extensions) for all available functions.
+The entire thirdweb SDK is available to use with Transactions v3 in this manner using the [`Transactions` namespace](/references/typescript/v5/functions#engine). Check the [thirdweb SDK docs](/references/typescript/v5/functions#extensions) for all available functions.

apps/portal/src/app/engine/v3/migrate/page.mdx

@@ -5,19 +5,19 @@ import SupportedChains from "../../_images/supported-chains.png";
 
 
 export const metadata = createMetadata({
-	title: "thirdweb Engine",
+	title: "thirdweb Transactions",
 	description: "An open-source, backend server that reads, writes, and deploys contracts at production scale.",
 });
 
-# Engine
+# Transactions
 
-Engine provides a way to read and write to the blockchain at scale through simple API endpoints.
+Transactions provides a way to read and write to the blockchain at scale through simple API endpoints.
 
-<OpenSourceCard title="Engine" href="https://github.com/thirdweb-dev/engine" />
+<OpenSourceCard title="Transactions" href="https://github.com/thirdweb-dev/engine" />
 
 <Callout variant="info" title="Looking for the v2 documentation?">
-We just launched Engine Cloud in beta — we're actively adding new features, endpoints, and performance improvements.
-Engine Standard and Premium have now been rebranded as Engine Dedicated V2, with Engine Dedicated V3 on the way.
+We just launched Transactions Cloud in beta — we're actively adding new features, endpoints, and performance improvements.
+Engine Standard and Premium have now been rebranded as Transactions Dedicated V2, with Transactions Dedicated V3 on the way.
 
 Looking for the previous version? [Head back to the Engine V2 documentation.](/engine/v2)
 </Callout>
@@ -74,10 +74,9 @@ Looking for the previous version? [Head back to the Engine V2 documentation.](/e
         description="Debug transaction failures with detailed timelines, onchain errors, and gas details."
         iconUrl={<ActivityIcon />}
     />
-    />
 </div>
 
-## Engine Cloud vs. Dedicated
+## Cloud vs. Dedicated
 
 | Feature            | Cloud ☁️                                   | Dedicated (Coming Soon)              |
 |--------------------|-------------------------------------------|------------------------------------------|
@@ -90,7 +89,7 @@ Looking for the previous version? [Head back to the Engine V2 documentation.](/e
 
 ## Supported Chains
 
-Engine is supported on every EVM compatible chain and private subnets. To view the full list, visit [thirdweb chainlist](https://thirdweb.com/chainlist?service=engine).
+Transactions are supported on every EVM compatible chain and private subnets. To view the full list, visit [thirdweb chainlist](https://thirdweb.com/chainlist?service=engine).
 
 <DocImage src={SupportedChains} />