docs: fix USDT0 naming and FAQ formatting

Author: probablyangg

STYLEGUIDE.md

@@ -48,9 +48,11 @@ Before returning any page, read it back and answer these four questions. Fix any
 | STABLE | Referring to the token (all caps) | Stable (when meaning the token), stable |
 | StableChain | Referring to the underlying settlement layer / protocol (capital S and C) | Stablechain, Stable chain, stablechain |
 | Stablechain | Only in the introductory definition ("Stable is the first Stablechain") | |
-| USDT | Referring to the asset | Tether (unless referring to the company) |
+| USDT | Referring to native USDT on a source chain, or to the broader asset where the distinction from USDT0 does not matter | Usdt, Tether (unless referring to the company) |
+| USDT0 | Referring to the omnichain asset, including Stable's native gas and settlement asset | Usdt0, USDT when referring specifically to the asset on Stable |
 
 - Use the product or protocol name exactly as branded (e.g., "LayerZero", "RedStone", "USDT0").
+- Never title-case an acronym or branded identifier. Write `USDT0`, `FAQ`, and `API`, not `Usdt0`, `Faq`, or `Api`.
 
 ### UI and keyboard actions
 
@@ -65,6 +67,11 @@ Before returning any page, read it back and answer these four questions. Fix any
 - Do not use title case (e.g., ~~"Gas Pricing And Fees"~~).
 - Vocs builds the right-side outline from your headings, so keep them short and scannable.
 
+### FAQ sections
+
+- In an FAQ section within a larger page, write each question as a `###` heading. This gives every question a visible hierarchy and a stable anchor.
+- On the dedicated `reference/faq.mdx` page, write each question as a bold paragraph ending in `?`. The structured-data parser uses that format to generate `FAQPage` question-and-answer entries.
+
 ## Frontmatter
 
 Every page must include these three fields, in this order:
@@ -120,6 +127,12 @@ Every page has exactly one home in the sidebar. Edit only the `/en` section of `
 
 When a concept is relevant to multiple sections (e.g., a Learn concept that readers also need mid-task in Build), keep it in its canonical section and surface it from the others through **content**, not navigation. Link to it from the relevant overview page inline. Concepts live in one place; task-oriented sections point at them.
 
+### Sidebar labels
+
+- Use sentence case for English sidebar labels.
+- Preserve the exact capitalization of acronyms, standards, and branded identifiers such as `USDT0`, `FAQ`, `API`, `JSON-RPC`, and `EIP-7702`.
+- Match the destination page's title unless the surrounding navigation provides context that allows a shorter label.
+
 ## Page structure
 
 Follow this general pattern:

docs/pages/en/explanation/bank-module.mdx

@@ -39,4 +39,4 @@ The full method signatures, event payloads, and authorization flow are in the [B
 
 - [**Bank precompile reference**](/en/reference/bank-module-api): Call `transfer`, `approve`, `mint`, `burn`, and read events.
 - [**System modules overview**](/en/explanation/system-modules-overview): Return to the full list of precompile-exposed modules.
-- [**USDT as gas**](/en/explanation/usdt-as-gas-token): Understand the dual-role asset model the bank module manages.
+- [**USDT0 as gas**](/en/explanation/usdt-as-gas-token): Understand the dual-role asset model the bank module manages.

docs/pages/en/explanation/confidential-transfer.mdx

@@ -53,6 +53,6 @@ Confidential Transfer is in development. See [Roadmap](/en/explanation/technical
 
 ## Next recommended
 
-- [**USDT as gas**](/en/explanation/usdt-as-gas-token): Understand the asset model confidential transfers shield.
+- [**USDT0 as gas**](/en/explanation/usdt-as-gas-token): Understand the asset model confidential transfers shield.
 - [**Flow of funds**](/en/explanation/flow-of-funds): See where confidentiality fits in the end-to-end payment lifecycle.
 - [**Roadmap**](/en/explanation/technical-roadmap): Track when confidential transfer ships.

docs/pages/en/explanation/eip-7702.mdx

@@ -47,5 +47,5 @@ After submission, the EOA's account code is set to the delegate. Subsequent tran
 ## Next recommended
 
 - [**Account Abstraction (EIP-7702)**](/en/reference/eip-7702-api): Implement batch payments, spending limits, and session keys against a delegate contract.
-- [**USDT as gas**](/en/explanation/usdt-as-gas-token): Understand the gas model that EIP-7702 transactions run on.
+- [**USDT0 as gas**](/en/explanation/usdt-as-gas-token): Understand the gas model that EIP-7702 transactions run on.
 - [**Gas waiver**](/en/explanation/gas-waiver): Compare delegation to gas-waived flows where an application pays the user's gas instead.

docs/pages/en/explanation/erc-3009.mdx

@@ -91,6 +91,6 @@ This property is what makes ERC-3009 on Stable a strong foundation for higher-le
 
 **See also:**
 
-- [USDT as Gas](/en/explanation/usdt-as-gas-token)
+- [USDT0 as gas](/en/explanation/usdt-as-gas-token)
 - [USDT0 Behavior on Stable](/en/explanation/usdt0-behavior)
 - [x402 (HTTP-Native Payments)](/en/explanation/x402)

docs/pages/en/explanation/ethereum-comparison.mdx

@@ -46,7 +46,7 @@ On Stable, transaction fees are paid in USDT0, not a volatile native token. This
 
 - Users need USDT0 in their wallet to submit transactions.
 - The `value` field in transactions still works for sending USDT0, similar to how ETH is sent on Ethereum.
-- See [USDT as gas](/en/explanation/usdt-as-gas-token) for details.
+- See [USDT0 as gas](/en/explanation/usdt-as-gas-token) for details.
 
 ### 3. No priority tips
 
@@ -74,6 +74,6 @@ USDT0 functions as both the native gas token and an ERC-20 token. This introduce
 
 ## Next recommended
 
-- [**USDT as gas**](/en/explanation/usdt-as-gas-token): Understand the asset model that replaces ETH for gas.
+- [**USDT0 as gas**](/en/explanation/usdt-as-gas-token): Understand the asset model that replaces ETH for gas.
 - [**Gas pricing**](/en/explanation/gas-pricing): Review the single-component fee model in detail.
 - [**USDT0 behavior on Stable**](/en/explanation/usdt0-behavior): Audit contracts for dual-role asset semantics, allowance safety, and `EXTCODEHASH` behavior.

docs/pages/en/explanation/flow-of-funds.mdx

@@ -60,6 +60,6 @@ The conversion logic (e.g., BTC → USDT) may be handled by an exchange partner,
 
 ## Next recommended
 
-- [**USDT as gas**](/en/explanation/usdt-as-gas-token): Understand how USDT0 serves as both native gas and ERC-20 balance on Stable.
+- [**USDT0 as gas**](/en/explanation/usdt-as-gas-token): Understand how USDT0 serves as both native gas and ERC-20 balance on Stable.
 - [**Bridging USDT0 to Stable**](/en/explanation/usdt0-bridging): See how USDT0 moves onto Stable from other chains via OFT Mesh or Legacy Mesh.
 - [**Send your first USDT0**](/en/tutorial/send-usdt0): Submit a USDT0 transfer on testnet using standard EVM tooling.

docs/pages/en/explanation/gas-pricing.mdx

@@ -36,5 +36,5 @@ Stable accepts EIP-1559 (Type 2) transactions, but `maxPriorityFeePerGas` is alw
 ## Next recommended
 
 - [**Gas pricing reference**](/en/reference/gas-pricing-api): Construct transactions, estimate gas, and configure tooling against Stable's fee model.
-- [**USDT as gas**](/en/explanation/usdt-as-gas-token): See how USDT0 serves as both native gas and ERC-20 balance.
+- [**USDT0 as gas**](/en/explanation/usdt-as-gas-token): See how USDT0 serves as both native gas and ERC-20 balance.
 - [**Ethereum comparison**](/en/explanation/ethereum-comparison): Review every behavior difference you'll encounter porting from Ethereum.

docs/pages/en/explanation/gas-waiver.mdx

@@ -56,4 +56,4 @@ For flows where the user does hold USDT0 but wants to bundle multiple calls into
 
 - [**Enable gas-free transactions**](/en/how-to/integrate-gas-waiver): Integrate the hosted Waiver Server API with API-key submission and NDJSON responses.
 - [**Gas waiver protocol**](/en/reference/gas-waiver-api): Read the full protocol spec: marker routing, wrapper format, governance controls.
-- [**USDT as gas**](/en/explanation/usdt-as-gas-token): Understand the gas token that the waiver covers.
+- [**USDT0 as gas**](/en/explanation/usdt-as-gas-token): Understand the gas token that the waiver covers.

docs/pages/en/explanation/key-features.mdx

@@ -19,7 +19,7 @@ Stable is a delegated Proof-of-Stake Layer 1 with single-slot finality, full EVM
 
 ## USDT-specific features
 
-- [**USDT as gas**](/en/explanation/usdt-as-gas-token): USDT0 serves as both the native gas token and an ERC-20 token on the same balance.
+- [**USDT0 as gas**](/en/explanation/usdt-as-gas-token): USDT0 serves as both the native gas token and an ERC-20 token on the same balance.
 - [**Gas waiver**](/en/explanation/gas-waiver): Governance-authorized waivers submit wrapper transactions that execute at zero gas price on the user's behalf.
 - [**Guaranteed blockspace**](/en/explanation/guaranteed-blockspace): Enterprise partners secure reserved capacity in every block for payment flows.
 - [**USDT transfer aggregator**](/en/explanation/usdt-transfer-aggregator): High-volume USDT0 transfers batch into parallelized, fault-tolerant settlement bundles.