diff --git a/docs/general/polkadot-direction.md b/docs/general/polkadot-direction.md
index d2a874a0eb34..5f30f08659e8 100644
--- a/docs/general/polkadot-direction.md
+++ b/docs/general/polkadot-direction.md
@@ -57,8 +57,8 @@ A paradigm shift from:
 
 Previously, securing a parachain slot was a competitive process through an
 [auction mechanism](../learn/learn-auction.md). With coretime rental, there is no need for slot
-auctions anymore. Teams can purchase on-demand coretime or reserve bulk coretime as required.
-This greatly decreases the barrier-to-entry for software tinkerers and parachain teams.
+auctions anymore. Teams can purchase on-demand coretime or reserve bulk coretime as required. This
+greatly decreases the barrier-to-entry for software tinkerers and parachain teams.
 
 On top of those main changes, [agile core usage](#agile-core-usage) and
 [coretime allocation](#agile-coretime-allocation) will allow any application to access Polkadot's
@@ -85,11 +85,11 @@ essentially **coretime becomes a commodity that can be tokenized, sold, and trad
 maximizes the agility of Polkadot and lets the market figure out the best solution needed for
 applications to be successful.
 
-Applications can reserve **bulk coretime** and **on-demand coretime** depending on their needs.
-Bulk coretime rental will be a standard rental of coretime through a broker system parachain at a
-fixed price for a fixed period of time. On-demand coretime rental will be available through
-ongoing sale of coretime for immediate use at a spot price. This system lowers the barrier to entry
-for prospective builders.
+Applications can reserve **bulk coretime** and **on-demand coretime** depending on their needs. Bulk
+coretime rental will be a standard rental of coretime through a broker system parachain at a fixed
+price for a fixed period of time. On-demand coretime rental will be available through ongoing sale
+of coretime for immediate use at a spot price. This system lowers the barrier to entry for
+prospective builders.
 
 For example, revenues from coretime sales can be burnt, used to fund the Treasury, or used for a mix
 of those options. The topic is currently under discussion. For more information, see
diff --git a/docs/learn/learn-polkadot-technical-fellowship.md b/docs/learn/learn-polkadot-technical-fellowship.md
index 7bbc5340767e..904c1b49c299 100644
--- a/docs/learn/learn-polkadot-technical-fellowship.md
+++ b/docs/learn/learn-polkadot-technical-fellowship.md
@@ -120,11 +120,10 @@ This initiative is funded by Polkadot treasury through
 :::info Induction to Fellowship as a Candidate (Rank 0)
 
 The fellowship manifesto states that any account may register to become a candidate for a basic
-deposit, but that feature has not been added to the collectives runtime yet.  A fellowship referendum 
-is no longer needed for candidate induction.  To be added as a
-candidate of the Polkadot Technical Fellowship, a pre-existing member with rank greater than or
-equal to 1 can sign and submit an `induct` call. The fellowship membership management is administered through
-the
+deposit, but that feature has not been added to the collectives runtime yet. A fellowship referendum
+is no longer needed for candidate induction. To be added as a candidate of the Polkadot Technical
+Fellowship, a pre-existing member with rank greater than or equal to 1 can sign and submit an
+`induct` call. The fellowship membership management is administered through the
 [core fellowship](https://github.com/paritytech/polkadot-sdk/blob/master/substrate/frame/core-fellowship/src/lib.rs)
 pallet.
 
diff --git a/docs/maintain/maintain-guides-async-backing.md b/docs/maintain/maintain-guides-async-backing.md
index bc93fb758255..b23e9f9a9194 100644
--- a/docs/maintain/maintain-guides-async-backing.md
+++ b/docs/maintain/maintain-guides-async-backing.md
@@ -80,8 +80,9 @@ collator side of Async Backing and establish a basic understanding of the change
 
 ## Prerequisite
 
-The relay chain needs to have async backing enabled so double-check that the relay-chain configuration
-contains the following three parameters (especially when testing locally e.g. with zombienet):
+The relay chain needs to have async backing enabled so double-check that the relay-chain
+configuration contains the following three parameters (especially when testing locally e.g. with
+zombienet):
 
 ```json
 "async_backing_params": {