chore(deps): add textlint for one-sentence-per-line enforcement

Author: AmadiaFlare

.textlintrc

@@ -0,0 +1,5 @@
+ {
+    "rules": {
+      "one-sentence-per-line": true
+    }
+  }

CONTRIBUTING.md

@@ -23,7 +23,8 @@ We welcome:
     - automation and docgen scripts (`automations/`, `docgen/`)
 
 3.  **Follow Style Guides:**
-    - **Code/Docs:** Run [Pre-PR checks](#pre-pr-checks). Match existing code style.
+    - **Code/Docs:** Run [Pre-PR checks](#pre-pr-checks).
+Match existing code style.
     - **Diagrams:** Adhere to the [Diagram Style Guide](#diagrams-style-guide) for consistency.
 
 4.  **Commit Your Changes:** We require [Conventional Commits](https://www.conventionalcommits.org/) format for clear history and automated changelogs.

docs/fdc/reference/IFdcHub.md

@@ -14,7 +14,8 @@ Sourced from `IFdcHub.sol` on [GitHub](https://github.com/flare-foundation/flare
 
 ## Overview
 
-The IFdcHub interface serves as the main entry point for applications requesting attestations from the Flare Data Connector. It provides functionality to request attestations, access configuration contracts, and handle related events.
+The IFdcHub interface serves as the main entry point for applications requesting attestations from the Flare Data Connector.
+It provides functionality to request attestations, access configuration contracts, and handle related events.
 
 ## Functions
 

docs/fdc/reference/IFdcInflationConfigurations.md

@@ -14,7 +14,8 @@ Sourced from `IFdcInflationConfigurations.sol` on [GitHub](https://github.com/fl
 
 ## Overview
 
-The IFdcInflationConfigurations interface allows access to the inflation distribution settings for different attestation types and sources within the Flare Data Connector system. These configurations determine how inflation rewards are allocated to validators based on the attestation requests they process.
+The IFdcInflationConfigurations interface allows access to the inflation distribution settings for different attestation types and sources within the Flare Data Connector system.
+These configurations determine how inflation rewards are allocated to validators based on the attestation requests they process.
 
 ## Functions
 

docs/fdc/reference/IFdcRequestFeeConfigurations.md

@@ -14,13 +14,15 @@ Sourced from `IFdcRequestFeeConfigurations.sol` on [GitHub](https://github.com/f
 
 ## Overview
 
-The IFdcRequestFeeConfigurations interface provides functionality for managing and retrieving fees associated with attestation requests in the Flare Data Connector (FDC) system. It allows for querying the base fee required for specific attestation requests.
+The IFdcRequestFeeConfigurations interface provides functionality for managing and retrieving fees associated with attestation requests in the Flare Data Connector (FDC) system.
+It allows for querying the base fee required for specific attestation requests.
 
 ## Functions
 
 ### getRequestFee
 
-Method to get the base fee for an attestation request. It reverts if the request is not supported.
+Method to get the base fee for an attestation request.
+It reverts if the request is not supported.
 
 ```solidity
 function getRequestFee(

docs/fdc/reference/IFdcVerification.md

@@ -14,7 +14,8 @@ Sourced from `IFdcVerification.sol` on [GitHub](https://github.com/flare-foundat
 
 ## Overview
 
-The IFdcVerification interface provides methods to verify different types of attestations from the Flare Data Connector. Smart contracts can use these verification functions to validate proofs provided by the State Connector system, ensuring the authenticity and integrity of the external data being used.
+The IFdcVerification interface provides methods to verify different types of attestations from the Flare Data Connector.
+Smart contracts can use these verification functions to validate proofs provided by the State Connector system, ensuring the authenticity and integrity of the external data being used.
 
 ## Verification Functions
 

docs/ftso/solidity-reference/FtsoV2Interface.md

@@ -12,7 +12,8 @@ import FTSOV2FeedsById from "!!raw-loader!/examples/developer-hub-solidity/FTSOV
 import FTSOV2FeedsByIdWei from "!!raw-loader!/examples/developer-hub-solidity/FTSOV2FeedsByIdWei.sol";
 import FTSOV2AnchorConsumer from "!!raw-loader!/examples/developer-hub-solidity/FTSOV2AnchorConsumer.sol";
 
-Primary interface for interacting with FTSOv2. This is a long-term support (LTS) interface, designed to ensure continuity even as underlying contracts evolve or protocols migrate to new versions.
+Primary interface for interacting with FTSOv2.
+This is a long-term support (LTS) interface, designed to ensure continuity even as underlying contracts evolve or protocols migrate to new versions.
 
 Sourced from `FtsoV2Interface.sol` on [GitHub](https://github.com/flare-foundation/flare-smart-contracts-v2/blob/main/contracts/userInterfaces/LTS/FtsoV2Interface.sol).
 

docs/ftso/solidity-reference/IFastUpdateIncentiveManager.md

@@ -87,9 +87,11 @@ function getScale(
 
 ### offerIncentive
 
-The entry point for third parties to make incentive offers. It accepts a payment and, using the contents of
+The entry point for third parties to make incentive offers.
+It accepts a payment and, using the contents of
 `_offer`, computes how much the expected sample size will be increased to apply the requested (but capped) range
-increase. If the ultimate value of the range exceeds the cap, funds are returned to the sender in proportion to
+increase.
+If the ultimate value of the range exceeds the cap, funds are returned to the sender in proportion to
 the amount by which the increase is adjusted to reach the cap.
 
 ```solidity

docs/ftso/solidity-reference/IFastUpdater.md

@@ -28,7 +28,8 @@ function blockScoreCutoff(
 
 #### Returns
 
-- `_cutoff`: The upper endpoint of the acceptable range of "scores" that providers generate for sortition. A score below the cutoff indicates eligibility to submit updates in the present sortition round.
+- `_cutoff`: The upper endpoint of the acceptable range of "scores" that providers generate for sortition.
+A score below the cutoff indicates eligibility to submit updates in the present sortition round.
 
 ### currentRewardEpochId
 
@@ -54,7 +55,8 @@ function currentScoreCutoff(
 
 #### Returns
 
-- `_cutoff`: The upper endpoint of the acceptable range of "scores" that providers generate for sortition. A score below the cutoff indicates eligibility to submit updates in the present sortition round.
+- `_cutoff`: The upper endpoint of the acceptable range of "scores" that providers generate for sortition.
+A score below the cutoff indicates eligibility to submit updates in the present sortition round.
 
 ### currentSortitionWeight
 
@@ -70,11 +72,13 @@ function currentSortitionWeight(
 
 #### Parameters
 
-- `_signingPolicyAddress`: The signing policy address of the specified provider. This is different from the sender of an update transaction, due to the signature included in the `FastUpdates` type.
+- `_signingPolicyAddress`: The signing policy address of the specified provider.
+This is different from the sender of an update transaction, due to the signature included in the `FastUpdates` type.
 
 #### Returns
 
-- `_weight`: The specified provider's weight for sortition purposes. This is derived from the provider's delegation weight for the FTSO, but rescaled against a fixed number of "virtual providers", indicating how many potential updates a single provider may make in a sortition round.
+- `_weight`: The specified provider's weight for sortition purposes.
+This is derived from the provider's delegation weight for the FTSO, but rescaled against a fixed number of "virtual providers", indicating how many potential updates a single provider may make in a sortition round.
 
 ### fetchAllCurrentFeeds
 
@@ -140,7 +144,8 @@ function numberOfUpdates(
 
 #### Returns
 
-- `_noOfUpdates`: The number of updates submitted in each block for the last `_historySize` blocks. The array is ordered from the current block to the oldest block.
+- `_noOfUpdates`: The number of updates submitted in each block for the last `_historySize` blocks.
+The array is ordered from the current block to the oldest block.
 
 ### numberOfUpdatesInBlock
 
@@ -165,7 +170,8 @@ function numberOfUpdatesInBlock(
 ### submissionWindow
 
 The submission window is a number of blocks forming a "grace period" after a round of sortition starts,
-during which providers may submit updates for that round. In other words, each block starts a new round of
+during which providers may submit updates for that round.
+In other words, each block starts a new round of
 sortition and that round lasts `submissionWindow` blocks.
 
 ```solidity

docs/ftso/solidity-reference/IFastUpdatesConfiguration.md

@@ -23,7 +23,8 @@ function getFeedConfigurations(
 
 ### getFeedId
 
-Returns the feed id at a given index. Removed (unused) feed index will return bytes21(0).
+Returns the feed id at a given index.
+Removed (unused) feed index will return bytes21(0).
 
 ```solidity
 function getFeedId(
@@ -43,7 +44,8 @@ function getFeedId(
 
 ### getFeedIds
 
-Returns all feed ids. For removed (unused) feed indices, the feed id will be bytes21(0).
+Returns all feed ids.
+For removed (unused) feed indices, the feed id will be bytes21(0).
 
 ```solidity
 function getFeedIds(