[Docs] Improvements to acct, ec, and vault docs (#7246)

CORE-0000

<!-- start pr-codex -->

---

## PR-Codex overview
This PR focuses on updating various documentation and component links within the `thirdweb` portal, as well as enhancing the content of FAQs and guides to provide clearer information on account management, migration to the TypeScript SDK v5, and Engine Cloud features.

### Detailed summary
- Added `Account` link to `supportLinks` in `Header.tsx`.
- Included warning about deprecation of TypeScript SDK v4 in `page.mdx`.
- Added troubleshooting details for transactions in `Engine Troubleshoot Guide`.
- Updated FAQ on customized plans in `faq/page.mdx`.
- Introduced ownership transfer steps in `manage-team/page.mdx`.
- Removed outdated Nebula access details in `faqs/page.mdx`.
- Added details about server wallet keys and admin key usage in `vault/faqs/page.mdx`.
- Updated pricing explanation and added a new chains support detail in `Engine Cloud` FAQ.
- Introduced a new section on `Smart Server Wallets`, detailing benefits and security in `server-wallets/page.mdx`.

> ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}`

<!-- end pr-codex -->

<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
## Summary by CodeRabbit

- **New Features**
  - Introduced a new documentation page for Smart Server Wallets, outlining features, security, and pricing.
  - Added new FAQ entries to the Vault documentation regarding key requirements for server wallets and admin key handling.
  - Added a new FAQ entry detailing supported chains for Engine Cloud.

- **Improvements**
  - Updated navigation links in the header, moving "Account" to support links and adding a "Status" link.
  - Enhanced troubleshooting guidance for Engine Cloud transactions.
  - Updated Engine Cloud pricing FAQ to reference the pricing page.
  - Added a warning callout about TypeScript SDK v4 deprecation to the migration guide.
  - Expanded billing documentation with a new section on transferring team ownership.
  - Clarified the FAQ about signing up for customized or enterprise plans.

- **Removals**
  - Removed outdated Nebula FAQ entries related to access approval and pricing.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

Author: saminacodes

apps/portal/src/app/Header.tsx

@@ -74,10 +74,6 @@ const toolLinks = [
     name: "Hex Converter",
     href: "https://thirdweb.com/tools/hex-converter",
   },
-  {
-    name: "Account",
-    href: "/account",
-  },
   {
     name: "API Keys",
     href: "/account/api-keys",
@@ -188,8 +184,12 @@ const supportLinks = [
     href: "/knowledge-base",
   },
   {
-    name: "Contact Sales",
-    href: "https://thirdweb.com/contact-us",
+    name: "Account",
+    href: "/account",
+  },
+  {
+    name: "Status",
+    href: "https://status.thirdweb.com",
   },
 ];
 

apps/portal/src/app/account/billing/manage-team/page.mdx

@@ -30,4 +30,20 @@ Invite your team members using email addresses and assign a member or owner role
 
 </Step>
 
+</Steps>
+
+## Transfer Ownership
+
+Owners may transfer ownership of a team to another member by adding a new owner and deleting the current owner. This is useful if you want to change the primary contact for billing or project management.
+
+<Steps>
+<Step title="Navigate to Settings > Members">
+While logged in, navigate to settings on your dashboard.
+</Step>
+<Step title="Transfer Ownership">
+Invite the member you want to transfer ownership to and select the "Owner" role for them. Ensure that the member has accepted the invitation and is listed as a team member.
+</Step>
+<Step title="Delete Prior Owner">
+Using the three dots next to the member's name, select "Remove Member" to remove the owner from the team. 
+</Step>
 </Steps>

apps/portal/src/app/account/faq/page.mdx

@@ -65,8 +65,8 @@ If you are developing a Unity native or mobile application, you will need to obt
 
 ## Billing
 
-<Details summary="How do I sign up for a thirdweb Pro plan?">
-To subscribe to the thirdweb Pro plan, please [contact Sales](https://thirdweb.com/contact-us) for more details about its features and to receive a quote for the monthly subscription fee.
+<Details summary="How do I sign up for a customized or enterprise thirdweb plan?">
+To subscribe to a customized plan, please [contact Sales](https://thirdweb.com/contact-us) for more details. 
 </Details>
 
 <Details summary="How do I update my payment method?">

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

@@ -0,0 +1,25 @@
+# Smart Server Wallets
+
+Smart server wallets are smart accounts designed to perform blockchain operations for backend applications.
+
+## Benefits
+
+Smart server wallets are the recommended way to perform blockchain operations with Engine.
+
+- **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.
+
+## Security
+
+Smart server wallets are secured by Vault, thirdweb's secure key management system. This setup ensures that your private keys are never exposed to the server or client, and all transactions are signed securely.
+Keys used to manage server wallets including the admin key and access keys can be rotated or re-rolled at any time, should you need to rotate keys for security purposes. Read more about [Vault](/vault).
+
+
+## Pricing
+
+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/faq/page.mdx

@@ -3,11 +3,18 @@ import { Callout, Details } from "@doc";
 # Engine 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. Write and sign requests cost $1 per 1,000 requests. Read requests made through Engine API are free, within the RPC limits/plan. 
+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. 
 
 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.
 
 **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. 
+
+If your chain is not listed, please [contact us](https://thirdweb.com/contact-us) to prioritize enabling support. 
+</Details>
+

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

@@ -1,3 +1,10 @@
+import { Details } from "@doc";
+
 # Engine Troubleshoot Guide
 
-More information coming soon.
+<Details summary="Transactions stuck in a pending state using Engine Cloud.">
+
+Ensure that Account Abstraction is enabled for your project by navigating to Project Settings > Enabled Services > Account Abstraction.
+
+If disabled, toggle on Account Abstraction and try the transaction again.
+</Details>

apps/portal/src/app/nebula/faqs/page.mdx

@@ -2,10 +2,6 @@ import { Details } from "@doc";
 
 # Nebula FAQs
 
-<Details summary="I am still waiting on access to Nebula. How can I be approved?"> 
-We are rolling out Nebula approval in batches daily - stay tuned! 
-</Details>
-
 <Details summary="What underlying model does Nebula use?"> 
 During Alpha, we are primarily testing the t0 model while conducting limited trials of the upcoming t1 model. 
 The t0 model utilizes a mixture-of-agents architecture. We are targeting an early Q2 launch for t1, and will 
@@ -67,7 +63,3 @@ Nebula is not currently open source. We are exploring open sourcing Nebula in th
 <Details summary="Can Nebula be used in a stateless manner?"> 
 Depending on the use case, Nebula can be used in a stateless manner by not reusing the same session. Nebula learns from each session, so having more contextual requests will be beneficial and are recommended.
 </Details>
-
-<Details summary="When will pricing be available for Nebula?"> 
-Pricing options will be available in beta. Nebula is still being tested in alpha.
-</Details>

apps/portal/src/app/typescript/v5/migrate/page.mdx

@@ -1,12 +1,17 @@
 import {
   ArticleIconCard,
+  Callout
 } from "@doc";
 import {
   ReactIcon,
 } from "@/icons";
 
 # Migration from TypeScript SDK v4
 
+<Callout type="warning">
+  The TypeScript SDK v4 will be deprecated on June 23, 2025. We highly recommend you to migrate to the latest version of the SDK v5 as soon as possible.
+</Callout>
+
 <ArticleIconCard
 	title="Looking to migrate to React SDK v5?"
 	icon={ReactIcon}

apps/portal/src/app/vault/faqs/page.mdx

@@ -22,4 +22,25 @@ a “rotation-code” only allows the “service account rotate” operation, wh
 There is no way for thirdweb to “silently” access your vault without your knowledge with only the recovery code.
 
 Rotating your engine’s vault account through a thirdweb-stored rotation code requires a signature from your wallet. You will also be able to see rotation history, the thirdweb account which initiated this rotation, and their wallet signature.
-</Details>
+</Details>
+
+<Details summary="Which key would I use to create additional server wallets?">
+You need either:
+- The admin key (which can perform any action, including creating Vault EOAs, aka server wallets).
+- Or an access token that has explicit permissions to create Vault EOAs.
+
+For Engine Cloud by default, we generate an access token for you during onboarding. This token can create Vault EOAs.
+
+However, if you want to restrict access to creating Vault EOAs, you can create a custom access token with the required scopes.
+</Details>
+
+<Details summary="How is my admin key used in the dashboard?">
+The admin key is temporarily stored in dashboard when performing actions that require it, such as creating or managing server wallets:
+
+- It is only stored locally in memory for the duration of your session.
+- It is only sent over the network when end-to-end encrypted communication with Vault is happening.
+- It is not persisted or stored after your session ends.
+
+Please note, you should never share your admin key with third parties.
+</Details>
+