fix some spelling

cspell.json

@@ -43,6 +43,7 @@
     "DIMM",
     "DYOR",
     "Datagram",
+    "Dedust",
     "Decompilation",
     "Descr",
     "ECDH",
@@ -52,6 +53,7 @@
     "Excno",
     "Extracurrency",
     "Fift",
+    "Fullnode",
     "Gbit",
     "Gbps",
     "Gravi",
@@ -69,6 +71,7 @@
     "Mbit",
     "Merkle",
     "Metaverse",
+    "Mintless",
     "Multiplatform",
     "Mytonctrl",
     "NVME",
@@ -137,6 +140,8 @@
     "cryptosystems",
     "datagram",
     "datagrams",
+    "defi",
+    "DeFi",
     "decompilation",
     "decompiles",
     "decompiling",
@@ -150,6 +155,7 @@
     "fiftlib",
     "float",
     "frontends",
+    "fullnode",
     "gamification",
     "gennaio",
     "getgems",
@@ -161,6 +167,8 @@
     "highlevel",
     "highload",
     "hmac",
+    "howto",
+    "HOWTO",
     "inclusivity",
     "inplace",
     "int",
@@ -181,6 +189,7 @@
     "long",
     "masterchain",
     "mathrm",
+    "mintless",
     "micropayment",
     "micropayments",
     "mintable",
@@ -231,6 +240,7 @@
     "subnetwork",
     "subnetworks",
     "subresolver",
+    "subresolvers",
     "sunt",
     "superserver",
     "tick-tock",
@@ -244,6 +254,8 @@
     "underload",
     "underloaded",
     "unixtime",
+    "visio",
+    "Visio",
     "workchain",
     "workchains",
     "xguard",

docs/develop/smart-contracts/environment/testnet.md

@@ -20,7 +20,7 @@ For convenience, almost the entire infrastructure of the mainnet (wallets, API,
 * Testnet TON Center API: https://testnet.toncenter.com
 * Testnet HTTP API: https://testnet.tonapi.io/
 * Testnet bridge: https://bridge.ton.org/?testnet=true
-* Testent dTON GraphQL: https://testnet.dton.io/
+* Testnet dTON GraphQL: https://testnet.dton.io/
 
 ## Some third parties
 

docs/develop/smart-contracts/governance.md

@@ -44,7 +44,7 @@ Each validator, from time to time, is randomly assigned to create a new block (i
 The same way as with checking whether it is time to conduct new elections, the Elector in each block checks whether it is time to release funds from `frozen` for stored `past_elections`. At the corresponding block, the Elector distributes accumulated earnings from corresponding validation rounds (gas fees and block creation rewards) to validators of that round proportional to validator weights. After that, stakes with rewards are added to the `credits` table, and the election gets removed from `past_elections` table.
 
 ### Current state of Elector
-You can check current state in the [dapp](https://1ixi1.github.io/elector/), which allows to see elections participans, locked stakes, ready to withdraw funds, complaints and so on.
+You can check current state in the [dapp](https://1ixi1.github.io/elector/), which allows to see elections participants, locked stakes, ready to withdraw funds, complaints and so on.
 ## Config
 Config smart contract controls TON configuration parameters. Its logic determines who and under what conditions has permission to change some of those parameters. It also implements a proposal/voting mechanism and validator set rolling updates.
 

docs/learn/academy/academy-overview.md

@@ -37,7 +37,7 @@ RU
 </Button>
 
 
-#### TON & Telegram Blockchain Сourse
+#### TON & Telegram Blockchain Course
 
 We're proud to present the __TON Blockchain Course__, which is a comprehensive guide to the TON Blockchain. The course is designed for developers who want to learn how to create smart contracts and decentralized applications on the TON Blockchain in engaging and interactive ways.
 

docs/participate/network-maintenance/custom-overlays.md

@@ -9,7 +9,7 @@ Currently these overlays can be used for two purposes:
 
 Participation in custom overlays allow to avoid uncertainty of public overlays and improve delivery reliability and delays.
 
-Each custom overlay has stricty determined list of participants with predefined permissions, in particular permission to send external messages and blocks. Config of the overlay should be the same on all participating nodes.
+Each custom overlay has strictly determined list of participants with predefined permissions, in particular permission to send external messages and blocks. Config of the overlay should be the same on all participating nodes.
 
 If you have multiple node under your control it is expedient to unite them into custom overlay, where all validators will be able to send block candidates and all LS will be able to send external messages. That way LS will synchronize faster while simultaneously external message delivery rate will be higher (and delivery more robust in general). Note, that additional overlay causes additional network traffic.
 

docs/participate/nodes/node-types.md

@@ -3,11 +3,11 @@ import Button from '@site/src/components/button'
 # TON Node Types
 
 **Blockchain node** is a device, usually a computer, that runs the TON blockchain's software - and therefore, participates in the blockchain operation.
-In general, nodes ensure decentralisation of the TON network.
+In general, nodes ensure decentralization of the TON network.
 
 Nodes perform different functions within the TON protocol:
 
-- **Full** and **archive nodes** maintain the blockchain block and transaction history, enable users and client applications to look for blocks and transactions, as well as to send new transations into the blockchain;
+- **Full** and **archive nodes** maintain the blockchain block and transaction history, enable users and client applications to look for blocks and transactions, as well as to send new transactions into the blockchain;
 - **Validator nodes** verify transactions ensuring the blockchain security.
 
 Below, you will find more detailed information about each of these node types, as well as about interaction of full and archive nodes with client applications.
@@ -34,8 +34,8 @@ Running a Full Node
 ## Archive Node
 
 **Archive node** is a full node that keeps the entire block history of the TON blockchain.
-Such nodes act as the decentralised point of truth in terms of ensuring consistency of the whole blockchain history.
-They serve as a backend for blockchain explorers and other applicaitons relying on deep transaction history.
+Such nodes act as the decentralized point of truth in terms of ensuring consistency of the whole blockchain history.
+They serve as a backend for blockchain explorers and other applications relying on deep transaction history.
 
 Archive nodes do not prune the blockchain state which elevates their system requirements, especially in terms of storage.
 According to the latest estimations, while full nodes and validator nodes require about 1 TB disk space, archive nodes would require about 8 TB to store the complete block history.
@@ -66,7 +66,7 @@ Running a Validator Node
 TON nodes are equipped with a _Liteserver_ functionality allowing external applications (in other words, _lite clients_) to interact with the TON blockchain via them.
 As a rule, the liteserver mode is used with full and archive nodes while validator nodes do not enable it to increase validation performance.
 
-The liteserver mode allows lite clients to send transactoins via TON nodes, as well as to retrieve information about blocks and transactions with them - for instance, to fetch and update wallet balances.
+The liteserver mode allows lite clients to send transactions via TON nodes, as well as to retrieve information about blocks and transactions with them - for instance, to fetch and update wallet balances.
 
 You have two options to allow your lite client application to interact with the TON blockchain:
 

docs/participate/run-nodes/become-validator.md

@@ -128,21 +128,21 @@ In case of low efficiency - take action to fix the problem. Contact technical su
 Please set up dashboards to monitor your validators using these APIs.
 :::
 
-#### Penalised Validators Tracker
+#### Penalized Validators Tracker
 
-You can track penalised validators on each round with [@tonstatus_notifications](https://t.me/tonstatus_notifications).
+You can track penalized validators on each round with [@tonstatus_notifications](https://t.me/tonstatus_notifications).
 
 #### Validation API
 https://elections.toncenter.com/docs - use this API to get information about current and past validation rounds (cycles) - time of rounds, which validators participated in them, their stakes, etc.
 
 Information on current and past elections (for the validation round) is also available.
 
-#### Effieciency API
+#### Efficiency API
 
 https://toncenter.com/api/qos/index.html#/ - use this API to get information on the efficiency of validators over time.
 
 This API analyses the information from the catchain and builds an estimate of the validator's efficiency. This API does not use the checkloadall utility, but is its alternative.
-Unlike `checkloadall` which works only on validation rounds, in this API you can set any time interval to analyse the validator's efficiency.
+Unlike `checkloadall` which works only on validation rounds, in this API you can set any time interval to analyze the validator's efficiency.
 
 Workflow:
 

docs/participate/run-nodes/mytonctrl.mdx

@@ -753,7 +753,7 @@ Example:
 
 ### clcf
 
-Create local config file (by dafault at `/usr/bin/ton/local.config.json`)
+Create local config file (by default at `/usr/bin/ton/local.config.json`)
 
 ### print_ls_proxy_config
 

docs/participate/wallets/contracts.md

@@ -194,7 +194,7 @@ Also op-code, op::code and operational code
 | Elector         | 0x4e73744b      | New Stake                  |
 | Elector         | 0xf374484c      | New Stake Confirmation     |
 | Elector         | 0x47657424      | Recover Stake Request      |
-| Elector         | 0x47657424      | Recover Stake Responce     |
+| Elector         | 0x47657424      | Recover Stake Response     |
 | Wallet          | 0x0f8a7ea5      | Jetton Transfer            |
 | Wallet          | 0x235caf52      | [Jetton Call To](https://testnet.tonviewer.com/transaction/1567b14ad43be6416e37de56af198ced5b1201bb652f02bc302911174e826ef7) |
 | Jetton          | 0x178d4519      | Jetton Internal Transfer   |

sidebars/develop.js

@@ -32,7 +32,7 @@ module.exports = [
       'develop/smart-contracts/guidelines/message-modes-cookbook',
       'develop/smart-contracts/guidelines/internal-messages',
       'develop/smart-contracts/guidelines/external-messages',
-      'develop/smart-contracts/guidelines/non-bouncable-messages',
+      'develop/smart-contracts/guidelines/non-bounceable-messages',
     ],
   },
   {

sidebars/participate.js

@@ -44,8 +44,7 @@ module.exports = [
       'participate/run-nodes/local-ton',
       'participate/run-nodes/mytonctrl-status',
       'participate/run-nodes/faq',
-      'participate/run-nodes/node-comands',
-
+      'participate/run-nodes/node-commands',
     ],
   },
   {

src/grammar/names-dictionary.txt

@@ -20,3 +20,9 @@ Ristretto
 Eruda
 Ratelance
 Onda
+Avacoin
+Serokell
+townsquarelabs
+Codespaces
+Codespace
+codespace