address PR review feedback

- Capitalize descriptions in terminology table
- Expand "DA" to "Data Availability (DA)" for clarity
- Add note explaining gas vs mana terminology in code
- Remove outdated "Aztec token" note (now consistently "Fee Juice")
- Replace L1/L2 with Ethereum/Aztec for clarity
- Clarify Fee Juice bridging uses enshrined FeeJuicePortal
- Reword fee payer section to mention FPC/paymaster context
- Clarify account deployment payment flow
- Add link to FPC documentation

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Author: critesjosh

docs/docs-developers/docs/foundational-topics/fees.md

@@ -23,33 +23,33 @@ Familiar terms from Ethereum mainnet as referred to on the Aztec network:
 
 | Ethereum Mainnet | Aztec              | Description                                                    |
 | ---------------- | ------------------ | -------------------------------------------------------------- |
-| gas              | mana               | unit measuring computational effort for transaction operations |
-| fee per gas      | Fee Juice per mana | price per unit of mana                                         |
-| fee (wei)        | Fee Juice          | total fee paid for a transaction                               |
+| gas              | mana               | Unit measuring computational effort for transaction operations |
+| fee per gas      | Fee Juice per mana | Price per unit of mana                                         |
+| fee (wei)        | Fee Juice          | Total fee paid for a transaction                               |
 
 ## What is mana?
 
 Mana is Aztec's unit of computational effort, equivalent to gas on Ethereum. Every transaction consumes mana based on the operations it performs.
 
 Mana has two dimensions:
 
-- **DA (Data Availability) mana**: Cost of publishing transaction data to the data availability layer
-- **L2 mana**: Cost of executing the transaction on the Aztec network
+- **Data Availability (DA) mana**: Cost of publishing transaction data to the data availability layer
+- **L2 mana**: Cost of executing the transaction on Aztec
 
 The total transaction fee is calculated as:
 
 ```
 fee = (daGas × feePerDaGas) + (l2Gas × feePerL2Gas)
 ```
 
-## What is Fee Juice?
-
-Fee Juice is the native fee token on Aztec, used to pay for transaction fees. It is bridged Aztec tokens from L1 and is **non-transferable** on L2 - it can only be used to pay fees, not sent between accounts.
-
 :::note
-Fee Juice is sometimes referred to as "Aztec token" in protocol documentation. They are the same thing.
+The SDK and protocol code use "gas" in variable names (e.g., `daGas`, `l2Gas`) for historical reasons, but conceptually these represent mana.
 :::
 
+## What is Fee Juice?
+
+Fee Juice is the native fee token on Aztec, used to pay for transaction fees. It is bridged Aztec tokens from Ethereum and is **non-transferable** on Aztec - it can only be used to pay fees, not sent between accounts.
+
 Aztec borrows ideas from EIP-1559, including congestion multipliers and the ability to specify base and priority fees per mana.
 
 ## Factors affecting fees
@@ -75,15 +75,15 @@ import { Gas_Settings_Components, Gas_Settings, Tx_Teardown_Phase } from '@site/
 
 ## Fee payment
 
-A fee payer will have Fee Juice from bridging Aztec tokens from Ethereum (L1). On Aztec this fee asset is non-transferable, and only deducted by the protocol to pay for fees. A user can claim bridged Fee Juice and use it to pay for transaction fees in the same transaction.
+A fee payer obtains Fee Juice by bridging Aztec tokens from Ethereum. The fee payer can be the account itself or a fee-paying contract (FPC), which functions similarly to a paymaster on Ethereum. On Aztec, Fee Juice is non-transferable and only deducted by the protocol to pay for fees. A user can claim bridged Fee Juice and use it to pay for transaction fees in the same transaction.
 
-The mechanism for bridging is the same as any other token. For more on this concept see the [Token Bridge Tutorial](../tutorials/js_tutorials/token_bridge.md) which describes portal contracts and [cross-chain messaging](../aztec-nr/framework-description/how_to_communicate_cross_chain.md).
+Fee Juice uses an enshrined `FeeJuicePortal` contract on Ethereum for bridging, unlike user-deployed token portals. The underlying cross-chain messaging mechanism is similar to other tokens - for more on this concept see the [Token Bridge Tutorial](../tutorials/js_tutorials/token_bridge.md) which describes portal contracts and [cross-chain messaging](../aztec-nr/framework-description/how_to_communicate_cross_chain.md).
 
 ### Payment methods
 
-An account with Fee Juice can pay for its transactions directly, including deployment of a new account, if Fee Juice has been bridged to the address where the account will be deployed.
+An account with Fee Juice can pay for its transactions directly. A new account can even pay for its own deployment transaction, provided Fee Juice was bridged to its address before deployment.
 
-Alternatively, accounts can use fee-paying contracts (FPCs) to pay for transactions. FPCs accept tokens and pay fees in Fee Juice on behalf of users. Common patterns include:
+Alternatively, accounts can use [fee-paying contracts (FPCs)](../aztec-js/how_to_pay_fees.md#fee-payment-contracts-fpc) to pay for transactions. FPCs accept tokens and pay fees in Fee Juice on behalf of users. Common patterns include:
 
 - **Sponsored FPCs**: Pay fees unconditionally, enabling free transactions for users
 - **Token-accepting FPCs**: Accept a specific token in exchange for paying fees