fix(docs): network guides, flare-tx-sdk, FSP claiming rewards

Author: nikerzetic-aflabs

docs/network/flare-tx-sdk/1-getting-started.mdx

@@ -64,7 +64,8 @@ Add the SDK to your project:
 The SDK separates network logic from account management.
 This ensures the same wallet can be used across multiple networks without code changes.
 
-- **`Network`**: Represents the blockchain network you want to connect to. Available networks include:
+- **`Network`**: Represents the blockchain network you want to connect to.
+  Available networks include:
   - `Network.FLARE`
   - `Network.COSTON2`
   - `Network.SONGBIRD`
@@ -73,7 +74,9 @@ This ensures the same wallet can be used across multiple networks without code c
   The `Network` object provides methods to query balances, transfer tokens, claim rewards, and interact with contracts.
   It uses Flare's [public RPCs](/network/overview#configuration) by default.
 
-- **`Wallet`**: Represents a user account. The SDK does not store private keys. Instead, it defines a [`Wallet`](https://github.com/flare-foundation/flare-tx-sdk/blob/HEAD/src/wallet/index.ts) interface which can be implemented by:
+- **`Wallet`**: Represents a user account.
+  The SDK does not store private keys.
+  Instead, it defines a [`Wallet`](https://github.com/flare-foundation/flare-tx-sdk/blob/HEAD/src/wallet/index.ts) interface which can be implemented by:
   - MetaMask and other browser wallets - `EIP1193WalletController`
   - Ledger - `LedgerWalletController`
   - Trezor - `TrezorWalletController`
@@ -191,7 +194,7 @@ async function connectEip1193() {
 ### Ledger
 
 Use the [`LedgerWalletController`](https://github.com/flare-foundation/flare-tx-sdk/blob/HEAD/src/wallet/ledger/controller.ts).
-It supports either Zondax Flare App ([`@zondax/ledger-flare`](https://www.npmjs.com/package/@zondax/ledger-flare)) or Ledger ETH App ([`@ledgerHQ/hw-app-eth`](https://www.npmjs.com/package/@ledgerhq/hw-app-eth)).
+It supports either Zondax Flare App ([`@zondax/ledger-flare`](https://www.npmjs.com/package/@zondax/ledger-flare)) or Ledger ETH App ([`@ledgerhq/hw-app-eth`](https://www.npmjs.com/package/@ledgerhq/hw-app-eth)).
 
 :::tip[Security]
 
@@ -253,7 +256,7 @@ The SDK only communicates with the device for signing.
 
     ```javascript
     import { LedgerWalletController } from "@flarenetwork/flare-tx-sdk";
-    import { Eth } from "@ledgerHQ/hw-app-eth"
+    import { Eth } from "@ledgerhq/hw-app-eth"
 
     async function connectLedgerViaEthApp() {
         // add Ledger transports here

docs/network/fsp/5-protocol-parameters.mdx

@@ -17,7 +17,7 @@ The values provided here correspond to Flare Mainnet.
 | **Precision (step size)**             | ≈0.0122%    | [`FastUpdatesIncentiveManager.getPrecision`](/ftso/solidity-reference/IFastUpdateIncentiveManager#getprecision)                   |
 | **Range (precision \* mean updates)** | 0.0183%     | [`FastUpdatesIncentiveManager.getRange`](/ftso/solidity-reference/IFastUpdateIncentiveManager#getrange)                           |
 | **Max range**                         | 0.091% (5x) | [`FastUpdatesIncentiveManager.rangeIncreaseLimit`](/ftso/solidity-reference/IFastUpdateIncentiveManager#rangeincreaselimit)       |
-| **Incentive duration**                | 17 blocks   | [`FastUpdatesIncentiveManager.getIncentiveDuration`](/ftso/solidity-reference/IFastUpdateIncentiveManager#getincentiveduration)   |
+| **Incentive duration**                | 17 blocks   | governance-configured (see [`IFastUpdateIncentiveManager`](/ftso/solidity-reference/IFastUpdateIncentiveManager))                 |
 | **Incentive fee (2x)**                | ≈36.6 FLR   | -                                                                                                                                 |
 
 ### Anchor Feeds (Scaling)

docs/network/fsp/guides/claiming-rewards.mdx

@@ -179,7 +179,8 @@ If the JSON cannot be fetched or validated, you cannot build a valid Merkle proo
 
   </TabItem>
   <TabItem value="coston2" label="Flare Testnet Coston2">
-    Fetch `reward-distribution-data-tuples.json` from [timivesel/ftsov2-testnet-rewards](https://gitlab.com/timivesel/ftsov2-testnet-rewards) on GitLab.
+    Fetch `reward-distribution-data-tuples.json` from the community-maintained mirror [timivesel/ftsov2-testnet-rewards](https://gitlab.com/timivesel/ftsov2-testnet-rewards) on GitLab.
+(This mirror is not an official Flare Foundation resource; treat the data with appropriate care and verify each tuple against on-chain values before claiming on production systems.)
 
     ```bash
     EPOCH_ID=123
@@ -215,7 +216,8 @@ If the JSON cannot be fetched or validated, you cannot build a valid Merkle proo
 
   </TabItem>
   <TabItem value="coston" label="Songbird Testnet Coston">
-    Fetch `reward-distribution-data-tuples.json` from [timivesel/ftsov2-testnet-rewards](https://gitlab.com/timivesel/ftsov2-testnet-rewards) on GitLab.
+    Fetch `reward-distribution-data-tuples.json` from the community-maintained mirror [timivesel/ftsov2-testnet-rewards](https://gitlab.com/timivesel/ftsov2-testnet-rewards) on GitLab.
+(This mirror is not an official Flare Foundation resource; treat the data with appropriate care and verify each tuple against on-chain values before claiming on production systems.)
 
     ```bash
     EPOCH_ID=123
@@ -392,7 +394,8 @@ console.log("Confirmed:", tx.hash);
 ## Troubleshooting
 
 <details>
-<summary>T0. Authorization failure: executor not allowed or recipient not allowlisted</summary>
+T0.
+Authorization failure: executor not allowed or recipient not allowlisted
 
 - If the signer sending `RewardManager.claim(...)` is not the beneficiary, ensure it is configured as a **claim executor** via `setClaimExecutors(...)`.
 - If the transaction reverts when using a `recipient` address, ensure the recipient is allowlisted via `setAllowedClaimRecipients(...)`.
@@ -403,7 +406,8 @@ console.log("Confirmed:", tx.hash);
 </details>
 
 <details>
-<summary>T1. No matching tuple found for my address</summary>
+T1.
+No matching tuple found for my address
 
 - Double-check:
   - Beneficiary address selection (DIRECT uses signing policy address; FEE uses identity address).
@@ -412,7 +416,8 @@ console.log("Confirmed:", tx.hash);
 </details>
 
 <details>
-<summary>T2. Claim transaction reverts</summary>
+T2.
+Claim transaction reverts
 
 - Ensure the Merkle proof and tuple fields (`rewardEpochId`, `beneficiary`, `amount`, `claimType`) are copied exactly from the JSON.
 - Ensure `lastEpochIdToClaim` is `>=` the maximum `rewardEpochId` included in your `claims` array.

docs/network/guides/flare-for-go-developers.mdx

@@ -20,7 +20,8 @@ import CreateAccount from "!!raw-loader!/examples/developer-hub-go/create_accoun
 import DeployContractCoston2 from "!!raw-loader!/examples/developer-hub-go/coston2/deploy_contract.go";
 import DeployContractFlare from "!!raw-loader!/examples/developer-hub-go/flare/deploy_contract.go";
 
-This guide is for developers who want to interact with Flare using Go. In this guide, using Go, you will learn how to:
+This guide is for developers who want to interact with Flare using Go.
+In this guide, using Go, you will learn how to:
 
 - Query a contract on Flare using the Go API for [Geth](https://github.com/ethereum/go-ethereum), a client that implements the full Ethereum JSON-RPC API.
 - Compile a Solidity contract using the CLI interface of [solc](https://github.com/argotorg/solidity), the Solidity compiler.
@@ -34,7 +35,9 @@ All examples in this guide are available at [developer-hub/examples](https://git
 
 ## Getting started
 
-Install Geth by following the instructions in the [Geth documentation](https://geth.ethereum.org/docs/getting-started/installing-geth). Also install the Solidity compiler by following the instructions in the [Solidity documentation](https://docs.soliditylang.org/en/latest/installing-solidity.html#linux-packages). The main commands are provided here:
+Install Geth by following the instructions in the [Geth documentation](https://geth.ethereum.org/docs/getting-started/installing-geth).
+Also install the Solidity compiler by following the instructions in the [Solidity documentation](https://docs.soliditylang.org/en/latest/installing-solidity.html#linux-packages).
+The main commands are provided here:
 
 <Tabs>
   <TabItem value="macos" label="MacOS via Homebrew" default>
@@ -78,7 +81,8 @@ developer-hub-go/
 
 ### Usage
 
-You need to connect to testnet or mainnet via an RPC, any RPC listed on the [Network Configuration](/network/overview#configuration) page will work. For this guide, you can use the Public RPC.
+You need to connect to testnet or mainnet via an RPC, any RPC listed on the [Network Configuration](/network/overview#configuration) page will work.
+For this guide, you can use the Public RPC.
 
 <Tabs groupId="network">
   <TabItem value="coston2" label="Flare Testnet Coston2" default>
@@ -108,7 +112,11 @@ For this example, you can use the `FlareContractRegistry` contract which has the
 
 ### Fetch ABI
 
-To fetch a contract's ABI, copy the [FlareContractRegistry ABI](https://api.routescan.io/v2/network/testnet/evm/114/etherscan/api?module=contract&action=getabi&address=0xaD67FE66660Fb8dFE9d6b1b4240d8650e30F6019&format=raw), and paste it into a file named `FlareContractRegistry.abi`, located in the root of your project, i.e. same level as `go.mod`.
+To fetch a contract's ABI, copy the FlareContractRegistry ABI from the appropriate Routescan endpoint and paste it into `FlareContractRegistry.abi` next to your `go.mod`.
+The `FlareContractRegistry` itself is deployed at the same `0xaD67FE66660Fb8dFE9d6b1b4240d8650e30F6019` on every Flare-family network — pick the URL that matches the chain you'll deploy to:
+
+- **Flare Testnet Coston2 (chain id 114):** [routescan URL](https://api.routescan.io/v2/network/testnet/evm/114/etherscan/api?module=contract&action=getabi&address=0xaD67FE66660Fb8dFE9d6b1b4240d8650e30F6019&format=raw)
+- **Flare Mainnet (chain id 14):** [routescan URL](https://api.routescan.io/v2/network/mainnet/evm/14/etherscan/api?module=contract&action=getabi&address=0xaD67FE66660Fb8dFE9d6b1b4240d8650e30F6019&format=raw)
 
 To generate the ABI bindings, which will be saved to `FlareContractRegistry.go`:
 
@@ -154,7 +162,8 @@ For example, querying it for the address of the `WNat` contract:
 
 ## Compiling with solc
 
-For this example, you can use the `FtsoV2FeedConsumer` contract to query the FTSOv2 feeds. Copy the `FtsoV2FeedConsumer` sample contract code given below, and save the `.sol` file in the same folder as your `go.mod`.
+For this example, you can use the `FtsoV2FeedConsumer` contract to query the FTSOv2 feeds.
+Copy the `FtsoV2FeedConsumer` sample contract code given below, and save the `.sol` file in the same folder as your `go.mod`.
 
 <details>
 <summary>`FtsoV2FeedConsumer` sample contract</summary>
@@ -177,13 +186,15 @@ The compiled contract will be saved in the `build/` folder.
 
 ## Create account
 
-Before deploying a contract, you need an account. You can create an account using the following code:
+Before deploying a contract, you need an account.
+You can create an account using the following code:
 
 <CodeBlock language="go" title="create_account.go">
   {CreateAccount}
 </CodeBlock>
 
-This will generate a new account and save the keystore file in the current directory. The account address will be printed to the console.
+This will generate a new account and save the keystore file in the current directory.
+The account address will be printed to the console.
 
 :::danger
 
@@ -239,7 +250,8 @@ Copy the contents of the generated keystore file into the `key` constant in the
 
 </Tabs>
 
-Congratulations! You have now successfully deployed a contract on Flare using Go.
+Congratulations!
+You have now successfully deployed a contract on Flare using Go.
 
 :::tip[What's next?]
 

docs/network/guides/flare-for-rust-developers.mdx

@@ -21,7 +21,8 @@ import DeployContractCoston2 from "!!raw-loader!/examples/developer-hub-rust/src
 import DeployContractFlare from "!!raw-loader!/examples/developer-hub-rust/src/bin/deploy_contract_flare.rs";
 import Config from "@site/examples/developer-hub-rust/config.json";
 
-This guide is for developers who want to interact with Flare using Rust. In this guide, using Rust, you will learn how to:
+This guide is for developers who want to interact with Flare using Rust.
+In this guide, using Rust, you will learn how to:
 
 - Query a contract on Flare using [alloy-rs](https://github.com/alloy-rs), an async library for interacting with Ethereum-like chains.
 - Compile a Solidity contract using the CLI interface of [solc](https://github.com/argotorg/solidity), the Solidity compiler.
@@ -35,7 +36,8 @@ All examples in this guide are available at [developer-hub/examples](https://git
 
 ## Getting started
 
-Install the Solidity compiler by following the instructions in the [Solidity documentation](https://docs.soliditylang.org/en/latest/installing-solidity.html#linux-packages). The main commands are provided here:
+Install the Solidity compiler by following the instructions in the [Solidity documentation](https://docs.soliditylang.org/en/latest/installing-solidity.html#linux-packages).
+The main commands are provided here:
 
 <Tabs>
   <TabItem value="macos" label="MacOS via Homebrew" default>
@@ -65,7 +67,8 @@ cargo add alloy eyre tokio --features alloy/full,tokio/rt,tokio/rt-multi-thread,
 
 ### Usage
 
-You need to connect to testnet or mainnet via an RPC, any RPC listed on the [Network Configuration](/network/overview#configuration) page will work. For this guide, you can use the Public RPC.
+You need to connect to testnet or mainnet via an RPC, any RPC listed on the [Network Configuration](/network/overview#configuration) page will work.
+For this guide, you can use the Public RPC.
 
 <Tabs groupId="network">
   <TabItem value="coston2" label="Flare Testnet Coston2" default>
@@ -99,7 +102,11 @@ For this example, you can use the `FlareContractRegistry` contract which has the
 
 ### Fetch ABI
 
-To fetch a contract's ABI, copy the [FlareContractRegistry ABI](https://api.routescan.io/v2/network/testnet/evm/114/etherscan/api?module=contract&action=getabi&address=0xaD67FE66660Fb8dFE9d6b1b4240d8650e30F6019&format=raw), and paste it into a file named `FlareContractRegistry.json`, located in the root of your project, i.e. same level as `Cargo.toml`.
+To fetch a contract's ABI, copy the FlareContractRegistry ABI from the appropriate Routescan endpoint and paste it into `FlareContractRegistry.json` next to your `Cargo.toml`.
+Pick the URL that matches the chain you'll deploy to:
+
+- **Flare Testnet Coston2 (chain id 114):** [routescan URL](https://api.routescan.io/v2/network/testnet/evm/114/etherscan/api?module=contract&action=getabi&address=0xaD67FE66660Fb8dFE9d6b1b4240d8650e30F6019&format=raw)
+- **Flare Mainnet (chain id 14):** [routescan URL](https://api.routescan.io/v2/network/mainnet/evm/14/etherscan/api?module=contract&action=getabi&address=0xaD67FE66660Fb8dFE9d6b1b4240d8650e30F6019&format=raw)
 
 ### Make query
 
@@ -130,7 +137,8 @@ cargo run --bin make_query
 
 ## Compiling a contract
 
-For this example, you can use the `FtsoV2FeedConsumer` contract to query the FTSOv2 feeds. Copy the `FtsoV2FeedConsumer` sample contract code given below, and save the `.sol` file in the same folder as your `Cargo.toml`.
+For this example, you can use the `FtsoV2FeedConsumer` contract to query the FTSOv2 feeds.
+Copy the `FtsoV2FeedConsumer` sample contract code given below, and save the `.sol` file in the same folder as your `Cargo.toml`.
 
 <details>
 <summary>`FtsoV2FeedConsumer` sample contract</summary>
@@ -159,7 +167,8 @@ This will generate a `FtsoV2FeedConsumer.json` file with the contract's ABI and
 
 ### Modify format
 
-Things get a bit annoying here, as the alloy-rs `solc!()` macro expects a specific format for the JSON, which is not the same as the output from the Solidity compiler. To fix this, in the generated `FtsoV2FeedConsumer.json`, remove the top-level JSON fields, after you are done, the JSON should look like:
+Things get a bit annoying here, as the alloy-rs `solc!()` macro expects a specific format for the JSON, which is not the same as the output from the Solidity compiler.
+To fix this, in the generated `FtsoV2FeedConsumer.json`, remove the top-level JSON fields, after you are done, the JSON should look like:
 
 ```json title="FtsoV2FeedConsumer.json"
 {
@@ -175,7 +184,8 @@ Things get a bit annoying here, as the alloy-rs `solc!()` macro expects a specif
 
 ## Create account
 
-Before deploying a contract, you need to have an account with some testnet or mainnet gas tokens. You can create a new Flare account using `create_account.rs`:
+Before deploying a contract, you need to have an account with some testnet or mainnet gas tokens.
+You can create a new Flare account using `create_account.rs`:
 
 <CodeBlock language="rust" title="src/bin/create_account.rs">
   {CreateAccount}
@@ -208,7 +218,8 @@ You can also import the raw hex private key to MetaMask and any other wallet - t
 
 ## Deploying with alloy-rs
 
-With the account ready, you can now deploy the contract. In a `deploy_contract.rs` file, you can define the following code to deploy the contract:
+With the account ready, you can now deploy the contract.
+In a `deploy_contract.rs` file, you can define the following code to deploy the contract:
 
 <Tabs groupId="network">
   <TabItem value="coston2" label="Flare Testnet Coston2" default>
@@ -227,13 +238,16 @@ With the account ready, you can now deploy the contract. In a `deploy_contract.r
   </TabItem>
 </Tabs>
 
-You can now run the `deploy_contract.rs` script to deploy the contract. The contract address will be printed once the deployment is successful. You can check the contract address on a Flare Blockchain explorer, linked on the [Network Configuration](/network/overview#configuration) page.
+You can now run the `deploy_contract.rs` script to deploy the contract.
+The contract address will be printed once the deployment is successful.
+You can check the contract address on a Flare Blockchain explorer, linked on the [Network Configuration](/network/overview#configuration) page.
 
 ```bash
 cargo run --bin deploy_contract
 ```
 
-Congratulations! You have now successfully deployed a contract on Flare using 🦀.
+Congratulations!
+You have now successfully deployed a contract on Flare using 🦀.
 
 :::tip[What's next?]