fix(docs): minor typos (#704)

Author: dineshpinto

automations/solidity_reference.json

@@ -513,6 +513,10 @@
         {
             "name": "PollingManagementGroup",
             "address": "0x142a8DbC8410deFd989dA27177986ac66aE9fCA8"
+        },
+        {
+            "name": "FtsoV2PriceStore",
+            "address": "0x8707442a5f40a17cee2Ae0555620a3ab6fEf60A4"
         }
     ],
     "SongbirdCanaryNetwork": [
@@ -893,6 +897,14 @@
         {
             "name": "PollingManagementGroup",
             "address": "0x4CBEE91ed327e41d1AfcDF7AA99d2696c8D56849"
+        },
+        {
+            "name": "AssetManagerController",
+            "address": "0x572DeF121DC83332887E25e34aD51C2f5f40BC97"
+        },
+        {
+            "name": "FtsoV2PriceStore",
+            "address": "0x14150aEeced5c1b318b0a78b0bBd8ca73ac891e4"
         }
     ]
 }

docs/network/guides/flare-contracts-registry.mdx

@@ -23,7 +23,7 @@ export const contracts = ["FlareContractRegistry"];
 
 Flare provides a registry of enshrined protocol contracts such as `FtsoV2`, `FdcHub`, and `RandomNumberV2`.  
 To ensure reliability, these contract addresses should **always be retrieved dynamically** via the **Flare Contract Registry** rather than hardcoding them.
-Using the registry ensures your contracts, and dApps are resistant to future upgrades and cannot be misled by off-chain or unverified sources.
+Using the registry ensures your contracts, and dApps are resistant to future upgrades and cannot be misled by offchain or unverified sources.
 
 ## Flare Contract Registry Address
 

docs/network/guides/gasless-usdt0-transfers.mdx

@@ -15,7 +15,7 @@ import USD0 from "!!raw-loader!/examples/developer-hub-javascript/USD0.json";
 Flare's USD₮0 integration enables native, gasless USDT transfers (also known as meta-transactions) on the Flare network, allowing your end-users to avoid paying gas fees directly.
 In this guide, you will build a system for gasless USD₮0 transfers:
 
-1. A **frontend application** where users authorize token transfers by signing a message, without needing to submit an on-chain transaction themselves.
+1. A **frontend application** where users authorize token transfers by signing a message, without needing to submit an onchain transaction themselves.
 2. A **backend relayer service** that takes this signed authorization and submits the actual transaction to the Flare network, covering the gas fees on the user's behalf.
 
 This powerful pattern significantly enhances user experience by abstracting away the complexities and costs of network gas fees.
@@ -40,8 +40,8 @@ This ensures transparent offchain signing.
 ### EIP-3009: Transfer with Authorization
 
 [EIP-3009](https://eips.ethereum.org/EIPS/eip-3009) extends the ERC-20 token standard to include support for meta-transactions.
-It allows a token holder to sign an authorization message offchain, which can then be relayed by another account (the relayer) to execute the transfer on-chain.
-The relayer pays the gas fees for this on-chain execution.
+It allows a token holder to sign an authorization message offchain, which can then be relayed by another account (the relayer) to execute the transfer onchain.
+The relayer pays the gas fees for this onchain execution.
 
 EIP-3009 introduces two key functions, including:
 

docs/support/whitepapers.mdx

@@ -31,19 +31,19 @@ Explore Flare's whitepapers, research, and analytics to gain deeper insights int
   <CustomCard
     title="The Flare Data Connector"
     href="/pdf/whitepapers/20240224-FlareDataConnector.pdf"
-    description="A protocol using network consensus to securely and reliably import offchain event data onto Flare, publishing confirmed attestations on-chain every 90 seconds."
+    description="The Flare Data Connector (FDC) enables users to register external events on Flare by submitting attestation requests, which are then validated by Flare's data providers and published on-chain every 90 seconds for use by dApps."
     date="Jan 14, 2025"
   />
   <CustomCard
     title="FTSOv2: more data feeds and faster updates to the FTSO"
     href="/pdf/whitepapers/20240223-FlareTimeSeriesOracleV2.pdf"
-    description="An upgraded Flare Time Series Oracle delivering faster updates via block-latency feeds alongside 90-second anchor feeds, while efficiently handling over 1,000 feeds."
+    description="An upgraded Flare Time Series Oracle (FTSO) delivering faster updates via block-latency feeds alongside 90-second anchor feeds, while efficiently handling over 1,000 feeds."
     date="Sep 9, 2024"
   />
   <CustomCard
     title="Consensus learning: A novel decentralised ensemble learning paradigm"
     href="/pdf/whitepapers/20240225-ConsensusLearning.pdf"
-    description="A distributed ML paradigm integrating ensemble methods with P2P consensus for data privacy and Byzantine fault tolerance."
+    description="A distributed Machine Learning paradigm integrating ensemble methods with P2P consensus for data privacy and Byzantine fault tolerance."
     date="Feb 25, 2024"
   />
 </div>

examples/developer-hub-javascript/GaslessApp.tsx

@@ -87,7 +87,7 @@ export default function App() {
       throw new Error(errorData.error || "Relayer request failed.");
     }
     const { txHash } = await response.json();
-    alert("✅ Sent! On-chain tx hash:\n" + txHash);
+    alert("✅ Sent! Onchain tx hash:\n" + txHash);
   }
 
   return (