fix(docs): apply suggested changes

nikerzetic-aflabs · nikerzetic-aflabs · commit f99604d8b75a · 2026-05-18T08:52:47.000+02:00
diff --git a/docs/fassets/developer-guides/13-fassets-agent-details.mdx b/docs/fassets/developer-guides/13-fassets-agent-details.mdx
@@ -99,7 +99,7 @@ function getAgentDetails(address _managementAddress) external view
 In this guide, you learned how to read FAssets agent details using the [AgentOwnerRegistry](/fassets/reference/IAgentOwnerRegistry) smart contract.
 This functionality is crucial for building user interfaces that display agent information and for validating agent credentials in your applications.
 
-The complete implementation examples are available in the [Flare Hardhat Starter Kit](/network/guides/hardhat-foundry-starter-kit) — see [`scripts/fassets/agentInfo.ts`](https://github.com/flare-foundation/flare-hardhat-starter/blob/master/scripts/fassets/agentInfo.ts) and the on-chain helper at [`contracts/fassets/FassetsAgentInfo.sol`](https://github.com/flare-foundation/flare-hardhat-starter/blob/master/contracts/fassets/FassetsAgentInfo.sol).
+The complete implementation examples are available in the [Flare Hardhat Starter Kit](/network/guides/hardhat-foundry-starter-kit).
 
 :::tip Next Steps
 To continue your FAssets development journey, you can:
diff --git a/docs/fassets/developer-guides/14-fassets-redemption-default.mdx b/docs/fassets/developer-guides/14-fassets-redemption-default.mdx
@@ -11,11 +11,6 @@ import YouTubeEmbed from "@site/src/components/YouTubeEmbed";
 
 ## Overview
 
-:::note Runnable example
-This guide describes the on-chain flow only.
-A runnable script that calls `redemptionPaymentDefault` end-to-end is not yet shipped in the starter kits — it will land in a follow-up PR to `flare-hardhat-starter` and `flare-foundry-starter`.
-:::
-
 In the FAssets system, once a **redeemer submits a redemption request**, the assigned **agent must send the underlying asset** (e.g., XRP) to the redeemer within a specific time defined in the [operational parameters](/fassets/operational-parameters).
 
 This guide explains:
diff --git a/docs/fassets/developer-guides/7-fassets-mint.mdx b/docs/fassets/developer-guides/7-fassets-mint.mdx
@@ -99,7 +99,6 @@ After understanding the underlying payment timeframes, you can use the provided
 2. Specify the correct constants from the reserve collateral script:
    - `AGENT_ADDRESS` - Agent's XRP Ledger address.
    - `AMOUNT_XRP` - XRP amount to send.
-     **Refresh this between runs** — it must equal `(valueUBA + feeUBA) / 10**assetDecimals` from the `CollateralReserved` event you just emitted.
    - `PAYMENT_REFERENCE` - Payment reference from the reserve collateral script.
 3. Create a client to connect to the XRP Ledger Testnet.
 4. Load the sender wallet.
diff --git a/docs/fassets/developer-guides/_mainnet-note.mdx b/docs/fassets/developer-guides/_mainnet-note.mdx
@@ -1,7 +1,7 @@
 :::note Network coverage
 
 Examples in this guide target the **Coston2** testnet for safety.
-For Songbird or Flare mainnet, swap the `coston2/` segment of every `@flarenetwork/flare-periphery-contracts/coston2/...` import for `songbird/` or `flare/` respectively, and resolve the AssetManager via the corresponding network's `IFlareContractRegistry` (e.g. `getAssetManagerFXRP()`, `getAssetManagerFBTC()`, `getAssetManagerFDOGE()`).
+For Songbird or Flare mainnet, swap the `coston2/` segment of every `@flarenetwork/flare-periphery-contracts/coston2/...` import for `songbird/` or `flare/` respectively, and resolve the AssetManager via the corresponding network's `IFlareContractRegistry`.
 RPC endpoints, faucet links, and the FAssets agents available on each network are listed on the [FAssets overview](/fassets/overview).
 
 :::
diff --git a/docs/fassets/reference/IAgentPing.mdx b/docs/fassets/reference/IAgentPing.mdx
@@ -4,10 +4,6 @@ sidebar_position: 9
 description: On-chain liveness ping/response between users and FAssets agent bots.
 ---
 
-:::caution Preview
-This page is a hand-written stub extracted directly from the periphery release (`@flarenetwork/flare-periphery-contracts` v0.1.41) while the auto-generated reference catches up.
-:::
-
 `IAgentPing` exposes a simple ping/response protocol for verifying that an FAssets agent's off-chain bot is alive.
 Users (or anyone) call `agentPing(agentVault, query)` to emit a `AgentPing` event; the bot listens for these events and replies with `agentPingResponse(agentVault, query, response)`, which emits an `AgentPingResponse` event identifying the owner address.
 
diff --git a/docs/fassets/reference/ICoreVaultClient.mdx b/docs/fassets/reference/ICoreVaultClient.mdx
@@ -4,11 +4,6 @@ sidebar_position: 8
 description: Agent-facing interface for transferring backing assets into and out of the FAssets core vault.
 ---
 
-:::caution Preview
-This page is a hand-written stub extracted directly from the periphery release (`@flarenetwork/flare-periphery-contracts` v0.1.41) while the auto-generated reference catches up.
-Function signatures and events may change between periphery releases — cross-check against the source before pinning your contract code.
-:::
-
 `ICoreVaultClient` is the agent-facing surface of the FAssets **core vault** subsystem.
 Agents transfer backing into the core vault to free up capital, and request returns when they need to redeem.
 Direct minting (FAssets minted without an XRPL payment from the user) and direct redemptions also flow through this client.
diff --git a/docs/fassets/reference/IFAsset.mdx b/docs/fassets/reference/IFAsset.mdx
@@ -4,10 +4,6 @@ sidebar_position: 7
 description: ERC-20 plus FAsset-specific metadata for FXRP / FBTC / FDOGE / FLTC tokens.
 ---
 
-:::caution Preview
-This page is a hand-written stub extracted directly from the periphery release (`@flarenetwork/flare-periphery-contracts` v0.1.41) while the auto-generated reference catches up.
-:::
-
 `IFAsset` is the ERC-20 surface of an FAsset token (FXRP, FBTC, FDOGE, FLTC, ...) with three extra accessors that expose the underlying asset's identity and the `IAssetManager` bound to this FAsset.
 It extends OpenZeppelin's [`IERC20`](https://docs.openzeppelin.com/contracts/5.x/api/token/erc20#IERC20) and [`IERC20Metadata`](https://docs.openzeppelin.com/contracts/5.x/api/token/erc20#IERC20Metadata).
 
diff --git a/docs/fdc/reference/IWeb2Json.mdx b/docs/fdc/reference/IWeb2Json.mdx
@@ -4,11 +4,6 @@ sidebar_position: 9
 description: Attestation type that fetches JSON over HTTP, applies a jq filter, and returns ABI-encoded data.
 ---
 
-:::caution Preview
-This page is a hand-written stub extracted directly from the periphery release (`@flarenetwork/flare-periphery-contracts` v0.1.41) while the auto-generated reference catches up.
-Cross-check against the source before pinning your contract code.
-:::
-
 The `Web2Json` attestation type fetches data from a URL, post-processes the returned JSON with a `jq` filter, and returns the result as ABI-encoded bytes.
 The interface only declares the request/response/proof structs — verification is exposed via [`IFdcVerification.verifyWeb2Json`](/fdc/reference/IFdcVerification#verifyweb2json).
 
diff --git a/docs/fdc/reference/IWeb2JsonVerification.mdx b/docs/fdc/reference/IWeb2JsonVerification.mdx
@@ -4,10 +4,6 @@ sidebar_position: 10
 description: Verifier interface for Web2Json proofs.
 ---
 
-:::caution Preview
-This page is a hand-written stub extracted directly from the periphery release (`@flarenetwork/flare-periphery-contracts` v0.1.41) while the auto-generated reference catches up.
-:::
-
 `IWeb2JsonVerification` is the verifier surface for the [`Web2Json`](/fdc/reference/IWeb2Json) attestation type.
 It is one of the parent interfaces inherited by [`IFdcVerification`](/fdc/reference/IFdcVerification) — in practice most consumers call `verifyWeb2Json` through `ContractRegistry.getFdcVerification()` rather than holding a separate `IWeb2JsonVerification` reference.
 
diff --git a/docs/fxrp/token-interactions/02-usdt0-fxrp-swap.mdx b/docs/fxrp/token-interactions/02-usdt0-fxrp-swap.mdx
@@ -12,11 +12,6 @@ import UniswapV3Wrapper from "!!raw-loader!/examples/developer-hub-solidity/Unis
 import UniswapV3WrapperScript from "!!raw-loader!/examples/developer-hub-javascript/uniswapV3Wrapper.ts";
 import RemixEmbed from "@site/src/components/RemixEmbed";
 
-:::warning Draft
-The runnable script `scripts/fassets/uniswapV3Wrapper.ts` referenced from this guide does not yet exist in the Flare Hardhat Starter.
-The guide is hidden (`unlisted: true`) until the script lands in the starter.
-:::
-
 ## Overview
 
 In this guide, you will learn how to swap USDT0 to FXRP using the Uniswap V3 router (SparkDEX).
diff --git a/docs/fxrp/token-interactions/04-gasless-fxrp-payments.mdx b/docs/fxrp/token-interactions/04-gasless-fxrp-payments.mdx
@@ -160,11 +160,6 @@ Save as `relayer/index.ts` to start the relayer service.
 
 ### Deploy Script
 
-:::note
-The deploy script below is provided in this guide only — it is not yet shipped in the Flare Hardhat Starter.
-To use it, copy the snippet into a new `scripts/gaslessForwarder/deploy.ts` file in your local clone of the starter (it will land in the starter on the next release).
-:::
-
 Save the snippet to `scripts/gaslessForwarder/deploy.ts` to deploy the [`GaslessPaymentForwarder`](/fxrp/token-interactions/gasless-fxrp-payments#gasless-payment-forwarder-contract) contract.
 
 <details>
diff --git a/docs/fxrp/upshift/_upshift.mdx b/docs/fxrp/upshift/_upshift.mdx
@@ -6,8 +6,8 @@ It provides [ERC-4626](https://eips.ethereum.org/EIPS/eip-4626) style vaults tha
 Upshift vaults support both instant and requested redemptions, depending on available liquidity.
 Users receive vault shares that represent their proportional ownership of the vault's assets, with yield accruing as share value increases over time.
 
-The [Upshift vault](https://app.upshift.finance/pools/14/0x373D7d201C8134D4a2f7b5c63560da217e3dEA28) (mainnet pool address `0x373D…dEA28`) is part of the XRP finance stack on Flare Network.
-The example scripts in the guides below interact with the Coston2 testnet vault `0x24c1a47cD5e8473b64EAB2a94515a196E10C7C81`.
+The [Upshift vault](https://app.upshift.finance/pools/14/0x373D7d201C8134D4a2f7b5c63560da217e3dEA28) is part of the XRP finance stack on Flare Network.
+The example scripts in the guides below interact with the Coston2 testnet [vault](https://coston2-explorer.flare.network/address/0x24c1a47cD5e8473b64EAB2a94515a196E10C7C81).
 It inherits the transparency model of the [FAssets](/fassets/overview) system: minting and redemption are proof-backed, and vault interactions are recorded on-chain.
 
 - **Funds are on-chain:** User deposits, vault balances, withdrawal requests, and claims are executed as smart contract state changes on Flare.
diff --git a/docs/smart-accounts/guides/cli/02-fassets-cycle.mdx b/docs/smart-accounts/guides/cli/02-fassets-cycle.mdx
@@ -105,7 +105,8 @@ sent bridge instruction transaction: 404EE0470152513277B10E5ADB6388175010634CDAF
 
 ## Request redeem
 
-We withdraw the same number of FXRP tokens that we have just deposited from the Upshift vault (`10`).
+We withdraw the same number of FXRP tokens that we have just deposited from the vault (`10`).
+The same flow applies to both Upshift-type and Firelight-type vaults.
 The process involves two steps.
 Before we can withdraw the tokens, we need to request their withdrawal.
 In a production build, the tokens stay locked for a specified time.
diff --git a/docs/smart-accounts/reference/IMasterAccountController.mdx b/docs/smart-accounts/reference/IMasterAccountController.mdx
@@ -53,10 +53,6 @@ Parameters:
 - `_proof`: Proof of the XRPL payment transaction that comes from the [Flare Data Connector](/fdc/overview).
 - `_xrplAddress`: The XRPL address that sent the payment.
 
-:::caution preview
-`reserveCollateral` and `executeDepositAfterMinting` belong to the executor-facing facets of the diamond and are documented here for completeness; cross-check the facet ABI shipped in the periphery release before consuming them — facet splits can shift between versions.
-:::
-
 ### `reserveCollateral`
 
 Reserves collateral for a minting operation.
diff --git a/examples/developer-hub-javascript/PriceVerification.ts b/examples/developer-hub-javascript/PriceVerification.ts
@@ -8,7 +8,7 @@ import {
   postRequestToDALayer,
   sleep,
 } from "../utils/fdc";
-import { getFdcHub, getRelay, getFdcVerification } from "../utils/getters";
+import { getFdcHub, getRelay } from "../utils/getters";
 import {
   getFdcRequestFee,
   calculateRoundId,
