applying prettier to entire repo (#5786)

Co-authored-by: Polkadot-Kusama Bot <[email protected]>

docs/learn/learn-agile-coretime.md

@@ -472,7 +472,9 @@ A ready-to-use automated and decentralized method for ordering on-demand coretim
 currently [being implemented](https://github.com/paritytech/polkadot-sdk/issues/1487). Some teams
 already implemented a simplified [variant](https://github.com/Magport/Magnet/issues/4). What works
 in any case is ordering on-demand coretime "by hand", by sending the `placeOrderKeepAlive` extrinsic
-of the `onDemandAssignmentProvider`, via polkadot js for example. You can find an easy step-by-step guide [here](https://forum.polkadot.network/t/parachain-consensus-updates-coretime-asynchronous-backing-scalability/4396/8?u=kianenigma).
+of the `onDemandAssignmentProvider`, via polkadot js for example. You can find an easy step-by-step
+guide
+[here](https://forum.polkadot.network/t/parachain-consensus-updates-coretime-asynchronous-backing-scalability/4396/8?u=kianenigma).
 
 #### How many cores will be configured for on-demand coretime?
 

docs/learn/learn-assets.md

@@ -36,18 +36,19 @@ logic.
 
 ## Sufficient Assets
 
-
-A sufficient asset on Asset Hub can allow for an account to exist on-chain even though it does not have any account balance in {{ polkadot: DOT :polkadot }}{{ kusama: KSM :kusama }}. Any registered asset on the Asset Hub can be made _sufficient_ through governance on the Relay Chain. A balance of a non-sufficient asset can only exist on accounts that are on-chain
-(i.e., accounts having the
+A sufficient asset on Asset Hub can allow for an account to exist on-chain even though it does not
+have any account balance in {{ polkadot: DOT :polkadot }}{{ kusama: KSM :kusama }}. Any registered
+asset on the Asset Hub can be made _sufficient_ through governance on the Relay Chain. A balance of
+a non-sufficient asset can only exist on accounts that are on-chain (i.e., accounts having the
 [existential deposit](./learn-accounts.md#existential-deposit-and-reaping) of a sufficient asset).
-That is, a user could not keep an account on-chain by transferring an non-sufficient asset to it; the
-account must already be on-chain by having more than the existential deposit in
+That is, a user could not keep an account on-chain by transferring an non-sufficient asset to it;
+the account must already be on-chain by having more than the existential deposit in
 {{ polkadot: DOT :polkadot }}{{ kusama: KSM :kusama }} (or a sufficient asset).
 
-Assets deemed _sufficient_ can instantiate accounts on the Asset Hub and pay for transaction fees without the need for
-{{ polkadot: DOT. :polkadot }}{{ kusama: KSM. :kusama }} An example would be USDT on the Polkadot
-Asset Hub. If an account holds 0.7 USDT, it would exist on the Polkadot Asset Hub system parachain
-without the need to hold DOT.
+Assets deemed _sufficient_ can instantiate accounts on the Asset Hub and pay for transaction fees
+without the need for {{ polkadot: DOT. :polkadot }}{{ kusama: KSM. :kusama }} An example would be
+USDT on the Polkadot Asset Hub. If an account holds 0.7 USDT, it would exist on the Polkadot Asset
+Hub system parachain without the need to hold DOT.
 
 :::warning Transfers of Non-sufficient assets
 

docs/learn/learn-nomination-pools.md

@@ -26,7 +26,7 @@ There are currently
 members in
 {{ polkadot: <RPC network="polkadot" path="query.nominationPools.lastPoolId" defaultValue={80} /> :polkadot }}
 {{ kusama: <RPC network="kusama" path="query.nominationPools.lastPoolId" defaultValue={115} /> :kusama }}
-pools. There is no limit to the number of pools or pool members per pool. 
+pools. There is no limit to the number of pools or pool members per pool.
 
 :::