Fix typos

nop33 · nop33 · commit 65a1ad83381d · 2024-06-28T19:47:26.000+02:00
diff --git a/docs/dapps/concepts/dust-amounts.md b/docs/dapps/concepts/dust-amounts.md
@@ -8,7 +8,7 @@ Alephium's unique
 [sUTXO](https://medium.com/@alephium/an-introduction-to-the-stateful-utxo-model-8de3b0f76749)
 model combines security of the UTXO model and the expressiveness of
 the account model. All assets in Alephium, including the native ALPH
-and other [tokes](/dapps/concepts/tokens), are managed by UTXOs. Even though
+and other [tokens](/dapps/concepts/tokens), are managed by UTXOs. Even though
 UTXO model brings many of the security benefits on to the table
 (e.g. see [Asset Permission
 System](http://localhost:3000/ralph/asset-permission-system)), it also
diff --git a/docs/full-node/full-node-more.md b/docs/full-node/full-node-more.md
@@ -49,7 +49,7 @@ Specify the `X-API-KEY` header, e.g.
 curl -H "X-API-KEY: ${your-api-key}" ${your-full-node-host}/infos/version
 ```
 
-## How to make the full node API publicly accessible ?
+## How to make the full node API publicly accessible?
 
 1. Set up your API key properly following the guide above.
 
@@ -59,7 +59,7 @@ curl -H "X-API-KEY: ${your-api-key}" ${your-full-node-host}/infos/version
 alephium.api.network-interface = "0.0.0.0"
 ```
 
-## How to access the Swagger UI of my full node on another computer in the same subnet ?
+## How to access the Swagger UI of my full node on another computer in the same subnet?
 
 1. Add the following to your `user.conf` and restart your full node.
 
diff --git a/docs/full-node/run-on-flux.md b/docs/full-node/run-on-flux.md
@@ -29,7 +29,7 @@ By default, the Full Node App only has the P2P port (`39973` on Flux nodes) expo
 
 <img src={require("/img/flux2.png").default} alt="Update specifications"/>
 
-3. Configure the connectivity to expose the container port `12973`. In the screenshot below the port `42973` has been arbitrariliy choosen and will be exposing the API. Any other valid port would work. Compute the signing message and follow the signing process to broadcast the specifications update across the network.
+3. Configure the connectivity to expose the container port `12973`. In the screenshot below the port `42973` has been arbitrarily choosen and will be exposing the API. Any other valid port would work. Compute the signing message and follow the signing process to broadcast the specifications update across the network.
 
 <img src={require("/img/flux3.png").default} alt="Configure connectivity"/>
 
diff --git a/docs/integration/integration-more.md b/docs/integration/integration-more.md
@@ -139,7 +139,7 @@ Alephium is a UTXO-based blockchain, recharging can be avoided by ensuring the s
 
 You can get the current height using this [endpoint](https://wallet.mainnet.alephium.org/docs/#/Blockflow/getBlockflowChain-info)`, you need to replace the `fromGroup` and `toGroup` params as needed, which can be any value of [0, 1, 2, 3].
 
-### What mechanism is in place to protect Alephium against 51% attack or to avoid chain forking ?
+### What mechanism is in place to protect Alephium against 51% attack or to avoid chain forking?
 
 It’s recommended to wait for 110 block confirmations (about 2 hours currently) for each deposit as it’s a PoW chain.
 Alephium implemented the same 51% attack protection as [Ravencoin](https://tronblack.medium.com/ravencoin-building-the-immune-system-23d077b65f71) and other PoW coins when the number of reorg is larger than 100.
diff --git a/docs/mining/miner-troubleshooting.md b/docs/mining/miner-troubleshooting.md
@@ -4,11 +4,11 @@ title: Troubleshooting
 ---
 
 
-### Why I can only restore 1 of my 4 miner addresses ?
+### Why I can only restore 1 of my 4 miner addresses?
 
 You have to specify `isMiner = true` when restoring your miner address. Please checkout the example here: [Restore-Miner-Wallet](solo-mining-guide.md#restore-your-miner-wallet)
 
-### How to connect my miner to my full node on another computer in the same subnet ?
+### How to connect my miner to my full node on another computer in the same subnet?
 
 1. Add the following to your `user.conf` and restart your full node.
 
@@ -18,15 +18,15 @@ alephium.mining.api-interface = "0.0.0.0"
 
 2. Run your miner with `-a IP`, where the IP is your full node's IP in the subnet.
 
-### How to use the Swagger UI of my VPS hosted full node ?
+### How to use the Swagger UI of my VPS hosted full node?
 
 SSH port forwarding is recommended:
 
 ```
 ssh user@server  -L 12973:127.0.0.1:12973
 ```
 
-### How to access the Swagger UI of my full node on another computer in the same subnet ?
+### How to access the Swagger UI of my full node on another computer in the same subnet?
 
 1. Add the following to your `user.conf` and restart your full node.
 
diff --git a/docs/misc/FAQ.md b/docs/misc/FAQ.md
@@ -319,7 +319,7 @@ In theory, yes. Predicting the future of technologies beyond 10, let alone 80 ye
 
 ### How is the maximum supply cap implemented?
 
-The maximum supply cap of 1 billion ALPH is an estimate. The protocol implements a cap on emissions based on a timestamp of approximately 80 years. This is because computing the sum of emissions for a shared chain within the protocol is computationally expensive. The emission rate is determined by the time and varies depending on the hash rate.  
+The maximum supply cap of 1 billion ALPH is an estimate. The protocol implements a cap on emissions based on a timestamp of approximately 80 years. This is because computing the sum of emissions for a sharded chain within the protocol is computationally expensive. The emission rate is determined by the time and varies depending on the hash rate.  
 It's worth noting that the 1 billion cap was estimated before the implementation of the improved [DAA](https://github.com/alephium/alephium/blob/master/docs/proposals/lemanDAA.md). With the current code, the actual cap on emission and maximum supply of ALPH is expected to be less than 1 billion in 80 years, even without taking into account the POLW mechanism's fee burning.
 
 ## Wallet
diff --git a/docs/misc/glossary.md b/docs/misc/glossary.md
@@ -45,7 +45,7 @@ Block Time is the time needed to compute the transactions inside a block and sen
 
 Transactions are gathered inside a block and checked by the miners (or validators on PoS blockchains). Usually, the Block Time is impacted by the mining difficulty, as it is adjusted to reflect the network's computational capacity (hashrate) over a given time.
 
-Alephium network has a difficulty adjustment on every block and has an expected block time of **64 seconds**.
+Alephium network has a difficulty adjustment on every block and has an expected block time of **16 seconds**.
 
 Additional resources: [Block Time and Block Size Article](https://medium.com/@alephium/block-time-and-block-size-16e37292444f)
 
diff --git a/docs/wallet/Multisig GUI.md b/docs/wallet/Multisig GUI.md
@@ -132,7 +132,7 @@ At this stage, the wallet has been created, a transaction has been built and dis
 
 And that’s it!
 
-You have successfully created and created and used a Multisig wallet to send a transaction on Alephium. For those who value both security and flexibility and need a way to share the funds ownership with others, a Multisig wallet is a powerful tool to have in your crypto arsenal. Remember, the future of finance is not just about owning digital assets but [securing them smartly](https://medium.com/@alephium/ttxoo-2-the-road-to-self-custody-cfea4ae89444).
+You have successfully created and used a Multisig wallet to send a transaction on Alephium. For those who value both security and flexibility and need a way to share the funds ownership with others, a Multisig wallet is a powerful tool to have in your crypto arsenal. Remember, the future of finance is not just about owning digital assets but [securing them smartly](https://medium.com/@alephium/ttxoo-2-the-road-to-self-custody-cfea4ae89444).
 
 *Let us know what you think, follow the evolution of the code on [Github](https://github.com/alephium), follow the news on [Twitter](https://twitter.com/alephium) & [Medium](https://medium.com/@alephium) or come interact onboard on [Discord](https://discord.com/invite/GEbcpajCJG) & [Telegram](https://t.me/alephiumgroup)!*
 
diff --git a/docs/wallet/ledger.md b/docs/wallet/ledger.md
@@ -122,7 +122,7 @@ All the steps here are the usual ones we have seen before using the extension wa
 
 ** 8 — Use the Ledger Device to interact with dApps in Alephium** 
 
-Now that you have a already sign a transaction with yout Ledger Device, it is time to connect it to a dApp. This process is also straightforward.
+Now that you have a already sign a transaction with your Ledger Device, it is time to connect it to a dApp. This process is also straightforward.
 
 Access the [Alephium DEX on Testnet](https://alephium.github.io/alephium-dex). Click in the “Connect Alephium” button on the top right. Select the extension wallet in the prompt and the Ledger account.
 
