fix(docs): ensure sentences start on newline

nikerzetic-aflabs · nikerzetic-aflabs · commit c9c87a213cfc · 2026-04-10T10:08:19.000+02:00
diff --git a/docs/fassets/01-overview.mdx b/docs/fassets/01-overview.mdx
@@ -37,7 +37,9 @@ Agents and a community-provided collateral pool ensure trustlessness through ove
   }}
 />
 
-Anyone on the Flare blockchain can mint FAssets, which are wrapped versions of original tokens from other blockchains, known as underlying networks. The original tokens from these chains, such as Ripple (XRPL), Dogecoin (DOGE), Bitcoin (BTC), and Litecoin (LTC), are referred to as underlying assets. For example, the FAsset version of Bitcoin is known as FBTC.
+Anyone on the Flare blockchain can mint FAssets, which are wrapped versions of original tokens from other blockchains, known as underlying networks.
+The original tokens from these chains, such as Ripple (XRPL), Dogecoin (DOGE), Bitcoin (BTC), and Litecoin (LTC), are referred to as underlying assets.
+For example, the FAsset version of Bitcoin is known as FBTC.
 
 ### Minting
 
@@ -99,7 +101,8 @@ Eligibility:
 
 ### Challengers
 
-Challengers monitor agents for illegal transactions that reduce collateral below the backing factor. They:
+Challengers monitor agents for illegal transactions that reduce collateral below the backing factor.
+They:
 
 - Submit proof of illegal actions to the system.
 - Earn rewards from the agent's vault upon successful challenges.
diff --git a/docs/fassets/02-minting.mdx b/docs/fassets/02-minting.mdx
@@ -120,11 +120,13 @@ The minting fee is further divided in two shares:
 
 #### Agent share
 
-This share remains in the agent's underlying account but is not marked as being in use. The agent can use this balance freely.
+This share remains in the agent's underlying account but is not marked as being in use.
+The agent can use this balance freely.
 
 #### Pool share
 
-This share is minted as FAssets and sent to the [collateral pool](/fassets/collateral#pool-collateral). The percentage of this share is defined by the agent and can be changed by the agent after a delay that provides time for minters to notice the change.
+This share is minted as FAssets and sent to the [collateral pool](/fassets/collateral#pool-collateral).
+The percentage of this share is defined by the agent and can be changed by the agent after a delay that provides time for minters to notice the change.
 
 ### Executor Fee
 
@@ -140,13 +142,21 @@ This design ensures timely and reliable minting finalization without relying on
 
 ### Minting
 
-The FAssets agent verifies the minter after the user completes the collateral reservation and pays the collateral reservation fee. The agent is responsible for confirming or rejecting the minter's status. If the agent does not respond within a certain timeframe, the minter has the option to cancel the reservation and receive a full refund of the collateral reservation fee.
+The FAssets agent verifies the minter after the user completes the collateral reservation and pays the collateral reservation fee.
+The agent is responsible for confirming or rejecting the minter's status.
+If the agent does not respond within a certain timeframe, the minter has the option to cancel the reservation and receive a full refund of the collateral reservation fee.
 
-To enable the agent to verify the minter, the collateral reservation must include the address (or multiple addresses, in the case of UTXO chains) from which the payment will be made. If multiple addresses are provided, all of them must be used for the payment.
+To enable the agent to verify the minter, the collateral reservation must include the address (or multiple addresses, in the case of UTXO chains) from which the payment will be made.
+If multiple addresses are provided, all of them must be used for the payment.
 
-Users must wait up to 60 seconds before they can cancel their request. If the agent accepts within this time, the user can proceed to mint by depositing the underlying assets. Therefore, it is important for the agent to respond quickly. If the agent does not respond in time, it will depend on whether the user is willing to wait; otherwise, the agent will simply miss the opportunity to mint, but there will be no loss of tokens.
+Users must wait up to 60 seconds before they can cancel their request.
+If the agent accepts within this time, the user can proceed to mint by depositing the underlying assets.
+Therefore, it is important for the agent to respond quickly.
+If the agent does not respond in time, it will depend on whether the user is willing to wait; otherwise, the agent will simply miss the opportunity to mint, but there will be no loss of tokens.
 
-When the agent rejects the minter's request or the minter decides to cancel, the minter will receive a refund of the collateral reservation fee, minus a small percentage (e.g., 5%) that is burned. This burned amount is designed to prevent abuse of the agent by stopping someone from repeatedly reserving collateral from a sanctioned address. If the burned percentage were zero, an attacker could exploit the system without any cost.
+When the agent rejects the minter's request or the minter decides to cancel, the minter will receive a refund of the collateral reservation fee, minus a small percentage (e.g., 5%) that is burned.
+This burned amount is designed to prevent abuse of the agent by stopping someone from repeatedly reserving collateral from a sanctioned address.
+If the burned percentage were zero, an attacker could exploit the system without any cost.
 
 ## Payment Failure
 
@@ -200,7 +210,8 @@ FAssets are still transferred to the minter's account, and the agent's collatera
 ### Expired proof
 
 Proofs provided by the [Flare Data Connector](/fdc/overview) can be created for 14 days and remain valid indefinitely once created.
-Suppose neither the minter nor the agent presents the proof of payment or nonpayment within the 14-day window. In that case, the regular minting process cannot continue, and the agent's collateral could be locked indefinitely.
+Suppose neither the minter nor the agent presents the proof of payment or nonpayment within the 14-day window.
+In that case, the regular minting process cannot continue, and the agent's collateral could be locked indefinitely.
 
 In this case, the agent can still recover the collateral by buying it back with native tokens.
 The recovery is accomplished with the following procedure:
diff --git a/docs/fassets/05-collateral.mdx b/docs/fassets/05-collateral.mdx
@@ -10,7 +10,9 @@ import useBaseUrl from "@docusaurus/useBaseUrl";
 FAssets collateral is locked in contracts that ensure the minted FAssets can always be redeemed for the underlying assets they represent or compensated by collateral.
 Along with Flare's native token, FLR, any governance approved ERC-20 token on the Flare blockchain can be used as collateral.
 
-FAssets collateral ensures the security and redemption of minted FAssets by locking collateral in smart contracts. This guarantees that FAssets can either be redeemed for their underlying assets or compensated by collateral. Collateral can include Flare's native token (FLR) and any governance-approved ERC-20 tokens on the Flare blockchain.
+FAssets collateral ensures the security and redemption of minted FAssets by locking collateral in smart contracts.
+This guarantees that FAssets can either be redeemed for their underlying assets or compensated by collateral.
+Collateral can include Flare's native token (FLR) and any governance-approved ERC-20 tokens on the Flare blockchain.
 
 ## Collateral Types
 
@@ -123,7 +125,8 @@ The following thresholds are set by the FAssets system's governance and are the
 
 #### Minimal CR
 
-The lowest collateral ratio the agent vault and the collateral pool must maintain so that enough collateral exists to insure the minted FAssets and to compensate for redemption payments that fail. The minimal CR can be different for each type of collateral.
+The lowest collateral ratio the agent vault and the collateral pool must maintain so that enough collateral exists to insure the minted FAssets and to compensate for redemption payments that fail.
+The minimal CR can be different for each type of collateral.
 
 If an agent's CR remains below the minimal CR for longer than a governance-set amount of time, [liquidations](/fassets/liquidation) can start.
 
@@ -180,12 +183,14 @@ To reduce the threat of liquidation, agents should set the minting CR well above
 
 #### Exit CR
 
-After a user redeems CPTs, the pool CR must be more than the exit CR. If the pool CR is already below the exit CR, redemption cannot occur.
+After a user redeems CPTs, the pool CR must be more than the exit CR.
+If the pool CR is already below the exit CR, redemption cannot occur.
 The exit CR is for the collateral pool only.
 
 #### Top-up CR
 
-To incentivize healthy collateral pools, if the pool CR falls below the top-up CR, anyone can add collateral to the pool and receive [CPTs](#pool-collateral) at a reduced price. This [top-up mechanism](#top-up) decreases the likelihood of liquidations because of a low amount of pool collateral.
+To incentivize healthy collateral pools, if the pool CR falls below the top-up CR, anyone can add collateral to the pool and receive [CPTs](#pool-collateral) at a reduced price.
+This [top-up mechanism](#top-up) decreases the likelihood of liquidations because of a low amount of pool collateral.
 
 ## Minting Fees and Debt
 
@@ -282,7 +287,8 @@ The following example shows fee entitlement.
 After step **4**, Bob is not entitled to any of the fees in the pool:
 
 - Bob is assigned an initial fee debt of 10 FAssets, according to the $fee\_debt_p$ formula in the box above.
-- As a result, the total virtual fees are increased to 20 FAssets. 10 of them are in fees, and 10 of them are in debt.
+- As a result, the total virtual fees are increased to 20 FAssets.
+  10 of them are in fees, and 10 of them are in debt.
 - Each user now holds half the total CPTs, therefore they are allowed to withdraw half the virtual fees, this is, 10 FAssets each.
 - Alice has no debt, so she can withdraw 10 FAssets, which is all the fees in the pool, because she was the only CPT holder when these fees were accrued.
 - Conversely, Bob has 10 FAssets of debt, so he can't withdraw any of the fees.
@@ -379,7 +385,8 @@ After step **2**, all of Alice's CPTs are transferable because she has no debt.
 After step **3**, all of Alice's CPTs continue to be transferable, and she is entitled to 100% of the fees in the pool.
 If she transferred or traded his CPTs, the recipient of those CPTs would be entitled to the fees.
 
-After step **4**, only half of Alice's CPTs are transferable (50 CPTs). The other half is debt-locked.
+After step **4**, only half of Alice's CPTs are transferable (50 CPTs).
+The other half is debt-locked.
 
 After step **5**, only 25% of Alice's CPTs remain locked (25 CPTs), which correspond to her 5 FAssets of debt.
 
@@ -445,7 +452,9 @@ These actions can cause the agent's CPTs to be burned:
 
 ## Top-up
 
-To reduce the likelihood of liquidations because the pool collateral is too low, the pool can be topped up at a reduced price when the **CR** is above the **top-up CR**. A top-up mechanism for vault collateral is not available. To prevent liquidation, agents can add vault collateral any time.
+To reduce the likelihood of liquidations because the pool collateral is too low, the pool can be topped up at a reduced price when the **CR** is above the **top-up CR**.
+A top-up mechanism for vault collateral is not available.
+To prevent liquidation, agents can add vault collateral any time.
 
 :::tip[What's next]
 
diff --git a/docs/fassets/06-core-vault.mdx b/docs/fassets/06-core-vault.mdx
@@ -119,7 +119,9 @@ The CV effectively acts as an **insurance-backed reserve** that boosts efficienc
 
 :::info
 
-Transfer requests do not expire. Agents must either complete the transfer or cancel and re-queue it. Inaction leaves collateral locked indefinitely.
+Transfer requests do not expire.
+Agents must either complete the transfer or cancel and re-queue it.
+Inaction leaves collateral locked indefinitely.
 
 :::
 
@@ -176,9 +178,12 @@ Three escrows are created if `remaining_funds = M + 3L`, and M stays in the wall
 
 ### Security Model
 
-The XRP Core Vault features enhanced security measures for managing daily liquidity, including escrow time-locking and a minimum reserve in multisig setups. It has an emergency pause function and "Red Alert Mode" for urgent threats.
+The XRP Core Vault features enhanced security measures for managing daily liquidity, including escrow time-locking and a minimum reserve in multisig setups.
+It has an emergency pause function and "Red Alert Mode" for urgent threats.
 
-In case of a security issue, all signing is halted pending governance review. Escrow accounts may be unlocked to prevent asset loss, with governance overseeing the restoration of operations. Only one escrow can be unlocked per day, minimizing potential damage.
+In case of a security issue, all signing is halted pending governance review.
+Escrow accounts may be unlocked to prevent asset loss, with governance overseeing the restoration of operations.
+Only one escrow can be unlocked per day, minimizing potential damage.
 
 ## Summary
 
diff --git a/docs/fassets/07-liquidation.mdx b/docs/fassets/07-liquidation.mdx
@@ -4,7 +4,8 @@ description: Understand how liquidations work in FAssets.
 keywords: [fassets, xrp, bitcoin, dogecoin, flare-network]
 ---
 
-Liquidation is the process of selling assets to bring the FAssets system back to health after an [agent](/fassets/overview#agents) becomes undercollateralized. The following types of liquidation can occur:
+Liquidation is the process of selling assets to bring the FAssets system back to health after an [agent](/fassets/overview#agents) becomes undercollateralized.
+The following types of liquidation can occur:
 
 - **Unhealthy position liquidation**: Occurs when the [collateral ratio (CR)](/fassets/collateral#collateral-ratio) of either the agent's vault or collateral pool falls below its respective [minimal CR](/fassets/collateral#system-wide-thresholds).
   In this case, the agent's position is liquidated until the collateral ratio reaches the [safety CR](/fassets/collateral#system-wide-thresholds) or all of the backed FAssets are liquidated.
diff --git a/docs/fassets/09-operational-parameters.mdx b/docs/fassets/09-operational-parameters.mdx
@@ -10,11 +10,13 @@ import TabItem from "@theme/TabItem";
 
 import OperationalParameters from "@site/src/features/FAssets/OperationalParameters";
 
-This page lists the current values for the most important parameters of the FAssets system on **Songbird Canary-Network** and **Songbird Testnet Coston**. These values are subject to change as the system is further developed and tested.
+This page lists the current values for the most important parameters of the FAssets system on **Songbird Canary-Network** and **Songbird Testnet Coston**.
+These values are subject to change as the system is further developed and tested.
 
 ## Asset Manager Operational Parameters
 
-To get the default agent settings, you need to call the `getSettings` function on the `IAssetManager` interface. Read more about the `IAssetManager` interface [here](/fassets/reference/IAssetManager).
+To get the default agent settings, you need to call the `getSettings` function on the `IAssetManager` interface.
+Read more about the `IAssetManager` interface [here](/fassets/reference/IAssetManager).
 
 ### Minting and Redeeming
 
@@ -48,13 +50,15 @@ To get the default agent settings, you need to call the `getSettings` function o
 
 ### Core Vault Manager
 
-To get the Core Vault manager operational parameters you need to use the [`ICoreVaultManager`](/fassets/reference/ICoreVaultManager) interface. Specific functions added to each parameter.
+To get the Core Vault manager operational parameters you need to use the [`ICoreVaultManager`](/fassets/reference/ICoreVaultManager) interface.
+Specific functions added to each parameter.
 
 <OperationalParameters sectionTitle="Core Vault Manager" hideBtc hideDoge />
 
 ### Core Vault Settings
 
-To get the Core Vault settings you need to use the [`IAssetManager`](/fassets/reference/IAssetManager) interface. Specific functions added to each parameter.
+To get the Core Vault settings you need to use the [`IAssetManager`](/fassets/reference/IAssetManager) interface.
+Specific functions added to each parameter.
 
 <OperationalParameters sectionTitle="Core Vault Settings" hideBtc hideDoge />
 
diff --git a/docs/fassets/11-songbird.mdx b/docs/fassets/11-songbird.mdx
@@ -6,7 +6,8 @@ keywords: [fassets, xrp, bitcoin, dogecoin, flare-network]
 
 import JiraIssueCollector from "/src/components/JiraIssueCollector";
 
-The launch of FAssets on Songbird Canary-Network demonstrates system behavior while paving the way for its next deployment on Flare Mainnet. The primary goals of this test are to ensure the system operates as intended, identify edge cases, refine usability and automation, and incentivize whitehat security researchers to uncover potential code errors.
+The launch of FAssets on Songbird Canary-Network demonstrates system behavior while paving the way for its next deployment on Flare Mainnet.
+The primary goals of this test are to ensure the system operates as intended, identify edge cases, refine usability and automation, and incentivize whitehat security researchers to uncover potential code errors.
 
 The test on Songbird Canary-Network will have the following characteristics:
 
