1187-documentation-fixes-pt-ii (#1188)

* check

* folders

* tenses

* emojis-icons

* BoC

* headers formatting

* my_code

* comparing connection keys

* sent case

* ui elements

* ui elements guidelines sections

* concepts

* check

* check1

* guidelines

* imgs

* documentation

Author: aigerimu

docs/v3/concepts/dive-into-ton/go-from-ethereum/solidity-vs-func.md

@@ -43,7 +43,7 @@ In the case of FunC, the main data types are:
 - **Tuples** — is an ordered collection of up to 255 components, having arbitrary value types, possibly distinct.
 - **Tensors** — is an ordered collection ready for mass assigning like: `(int, int) a = (2, 4)`. A special case of tensor type is the unit type `()`. It represents that a function doesn’t return any value or has no arguments.
 
-Currently, FunC does not support defining custom types. Read more about types in [Statements](/v3/documentation/smart-contracts/func/docs/statements/) page.
+Currently, FunC does not support defining custom types. Read more about types in the [Statements](/v3/documentation/smart-contracts/func/docs/statements/) page.
 
 ### Declaring and using variables
 
@@ -64,7 +64,7 @@ FunC is a more abstract and function-oriented language. It supports dynamic typi
 var z = x + y; // Dynamic variable declaration 
 ```
 
-Read more in [Statements](/v3/documentation/smart-contracts/func/docs/statements/) page.
+Read more on the [Statements](/v3/documentation/smart-contracts/func/docs/statements/) page.
 
 ### Loops
 
@@ -93,7 +93,7 @@ repeat(10) {
 }
 ;; x = 1024
 ```
-Read more on [Statements](/v3/documentation/smart-contracts/func/docs/statements/) page.
+Read more on the [Statements](/v3/documentation/smart-contracts/func/docs/statements/) page.
 
 ### Functions
 
@@ -133,7 +133,7 @@ Most of the control structures known from curly-braces languages are available i
 #### FunC
 FunC supports classic `if-else` statements, `ifnot`, `repeat`, `while`, and `do/until` loops.  Also, since v0.4.0, `try-catch` statements are supported.
 
-Read more in [Statements](/v3/documentation/smart-contracts/func/docs/statements/) page.
+Read more on the [Statements](/v3/documentation/smart-contracts/func/docs/statements/) page.
 
 ### Dictionaries
 
@@ -233,7 +233,7 @@ send_raw_message(msg, mode);
 
 This example presented how smart contracts can communicate with each other. 
 
-Read more in [Internal Messages](/v3/documentation/smart-contracts/overview/) page.
+Read more on the [Internal messages](/v3/documentation/smart-contracts/overview/) page.
 
 ## See also 
 

docs/v3/concepts/dive-into-ton/go-from-ethereum/tvm-vs-evm.md

@@ -10,24 +10,25 @@ import Feedback from '@site/src/components/Feedback';
 ### Data presentation
 
 #### EVM
-1. Fundamental Data Units
- The EVM operates primarily on 256-bit integers, reflecting its design around Ethereum's cryptographic functions, such as Keccak-256 hashing and elliptic curve operations.
+1. Fundamental data units
+
+ - The EVM operates primarily on 256-bit integers, reflecting its design around Ethereum's cryptographic functions, such as Keccak-256 hashing and elliptic curve operations.
  - Data types are limited mainly to integers, bytes, and occasionally arrays of these types, but all must conform to 256-bit processing rules.
-2. State Storage
+2. State storage
 - The entire state of the Ethereum blockchain is a mapping of 256-bit addresses to 256-bit values. A data structure known as the **Merkle Patricia Trie (MPT)** maintains this mapping.
 - The MPT enables Ethereum to efficiently prove the consistency and integrity of the blockchain state through cryptographic verification, which is vital for a decentralized system like Ethereum.
-3. Data Structure Limitations
+3. Data structure limitations
 - The simplification to 256-bit word constraints means that the EVM is not inherently designed to handle complex or custom data structures directly.
 Developers often need to implement additional logic within smart contracts to simulate more complex data structures, which can increase gas costs and complexity.
 
 #### TVM
-1. Cell-Based Architecture
+1. Cell-based architecture
 - TVM uses a unique [bag of cells](/v3/documentation/data-formats/tlb/cell-boc/) model to represent data. Each cell can contain up to 128 data bytes and have up to 4 references to other cells.
 - This structure allows the TVM to natively support arbitrary algebraic data types and more complex constructions such as trees or directed acyclic graphs (DAGs) directly within its storage model.
-2. Flexibility and Efficiency
+2. Flexibility and efficiency
 - The cell model provides significant flexibility, enabling the TVM to handle various data structures more naturally and efficiently than the EVM.
 - For example, creating linked structures through cell references allows for dynamic and potentially infinite data structures, which is crucial for specific applications like decentralized social networks or complex decentralized finance (DeFi) protocols.
-3. Complex Data Handling
+3. Complex data handling
 - The ability to manage complex data types inherently within the VM architecture reduces the need for workaround implementations in smart contracts, potentially lowering the execution cost and increasing execution speed.
 TVM's design is particularly advantageous for applications requiring complex state management or interlinked data structures. It provides a robust foundation for developers to build sophisticated and scalable decentralized applications.
 

docs/v3/concepts/dive-into-ton/introduction.mdx

@@ -17,8 +17,8 @@ To understand the true vision for the decentralized internet and how TON contrib
 
 <Player url="https://www.youtube.com/watch?v=XgzHmV_nnpY" />
 
-* To learn more about the technical aspects of TON Blockchain, review the [Blockchain of Blockchains](/v3/concepts/dive-into-ton/ton-blockchain/blockchain-of-blockchains/)
-* Learn more about the development of all things TON by reviewing this section: [Getting Started](/v3/documentation/ton-documentation/)
+* To learn more about the technical aspects of TON Blockchain, review the [Blockchain of blockchains](/v3/concepts/dive-into-ton/ton-blockchain/blockchain-of-blockchains/)
+* Learn more about the development of all things TON by reviewing this section: [Getting started](/v3/documentation/ton-documentation/)
 
 ## Blockchain basics with TON
 
@@ -50,9 +50,9 @@ Russian
 
 ## TON Blockchain development
 
-__TON Blockchain Course__ is a comprehensive TON Blockchain guide. The course is designed for developers who want to learn how to create smart contracts and decentralized applications (dApps) on the TON Blockchain.
+__TON Blockchain course__ is a comprehensive TON Blockchain guide. The course is designed for developers who want to learn how to create smart contracts and decentralized applications (dApps) on the TON blockchain.
 
-It consists of __9 modules__ and covers the basics of the TON Blockchain, the FunC programming language, and the TON Virtual Machine (TVM).
+It consists of __9 modules__ and covers the basics of TON Blockchain, the FunC programming language, and the TON Virtual Machine (TVM).
 
 
 <Button href="https://stepik.org/course/176754/promo"

docs/v3/concepts/dive-into-ton/ton-blockchain/cells-as-data-storage.md

@@ -55,12 +55,13 @@ Any object in TON, like the message, block, or whole blockchain state, serialize
 A TL-B scheme describes the serialization process: a formal description of how this object can be serialized into _builder_ or how to parse an object of a given type from the _Slice_.
 TL-B for cells is the same as TL or ProtoBuf for byte-streams.
 
-If you want more details about cell serialization and deserialization, read the [Cell & Bag of Cells](/v3/documentation/data-formats/tlb/cell-boc) article.
+If you want more details about cell serialization and deserialization, read [Cell & bag of cells](/v3/documentation/data-formats/tlb/cell-boc) article.
+
 
 ## See also
 
 - [Blockchain of blockchains](docs/v3/concepts/dive-into-ton/ton-blockchain/blockchain-of-blockchains/)
-- [TL-B Language](/v3/documentation/data-formats/tlb/tl-b-language)
+- [TL-B language](/v3/documentation/data-formats/tlb/tl-b-language)
 
 <Feedback />
 

docs/v3/concepts/dive-into-ton/ton-blockchain/security-measures.md

@@ -4,39 +4,39 @@ import Feedback from '@site/src/components/Feedback';
 
 The security of the TON blockchain ecosystem is of utmost importance. Below is a summary of completed audits conducted by renowned auditing firms for key components of the TON blockchain.
 
-## TON blockchain
+## TON Blockchain
 
 Various security providers audited core blockchain modules to ensure their robustness and security.
 
-**Audit Firms**: Trail of Bits, SlowMist, CertiK  
-**Audit Reports**:
+**Audit firms**: Trail of Bits, SlowMist, CertiK  
+**Audit reports**:
 - [Trail of Bits: TON Blockchain Audit Report](https://docs.ton.org/audits/TON_Blockchain_ToB.pdf)
 - [SlowMist: TON Blockchain Audit Report](https://docs.ton.org/audits/TON_Blockchain_SlowMist.pdf)
 - [CertiK: TON Blockchain Audit Report](https://docs.ton.org/audits/TON_Blockchain_CertiK.pdf)
 - [CertiK: TON Masterchain Contracts Formal Verification](https://docs.ton.org/audits/TON_Blockchain_Formal_Verification_CertiK.pdf)
 
-## TON blockchain library (tonlib)
+## TON Blockchain library (tonlib)
 
 Zellic conducted a security assessment for TON from October 16th to November 17th, 2023. During this engagement, Zellic reviewed Tonlib’s code for security vulnerabilities, design issues, and general weaknesses in security posture.
 
-**Audit Firm**: Zellic  
-**Audit Report**:
+**Audit firm**: Zellic  
+**Audit report**:
 - [Zellic: Audit Report](https://docs.ton.org/audits/TON_Blockchain_tonlib_Zellic.pdf)
 
 ## TVM and Fift
 
 Audit for TON Virtual Machine and the Fift programming language.
 
-**Audit Firm**: Trail of Bits  
-**Audit Report**:
+**Audit firm**: Trail of Bits  
+**Audit report**:
 - [Trail of Bits Audit Report - TVM & Fift](https://docs.ton.org/audits/TVM_and_Fift_ToB.pdf)
 
-## TVM Upgrade 2023.07
+## TVM Upgrade Jul 2023
 
 Audit for security and potential vulnerabilities in TVM Upgrade 2023.07.
 
-**Audit Firm**: Trail of Bits  
-**Audit Report**:
+**Audit firm**: Trail of Bits  
+**Audit report**:
 - [Trail of Bits Audit Report - TVM Upgrade](https://docs.ton.org/audits/TVM_Upgrade_ToB_2023.pdf)
 
 ---

docs/v3/concepts/dive-into-ton/ton-blockchain/smart-contract-addresses.md

@@ -77,7 +77,7 @@ However, raw addresses have two main issues:
 
 Convert raw, user-friendly addresses using [ton.org/address](https://ton.org/address/).
 
-For more details, refer to the refhandling guide in [Addresses Documentation](/v3/documentation/smart-contracts/addresses/).
+For more details, refer to the refhandling guide in the [Smart contracts addresses documentation](/v3/documentation/smart-contracts/addresses/) section.
 
 ## See also
 

docs/v3/concepts/dive-into-ton/ton-blockchain/ton-networking.md

@@ -2,19 +2,19 @@ import Feedback from '@site/src/components/Feedback';
 
 # TON networking
 
-The TON Ecosystem uses its peer-to-peer network protocols.
+TON Ecosystem uses its peer-to-peer network protocols.
 
-- **TON blockchain** uses these protocols to propagate new blocks, send and collect transaction candidates, etc.
+- **TON Blockchain** uses these protocols to propagate new blocks, send and collect transaction candidates, etc.
 
   While the networking demands of single-blockchain projects, such as Bitcoin or Ethereum, can be met quite easily: one essentially needs to construct a peer-to-peer overlay network and then propagate all new blocks and transaction candidates via a [gossip](https://en.wikipedia.org/wiki/Gossip_protocol) protocol.
 
 Multi-blockchain projects, such as TON, are much more demanding. For example, one must be able to subscribe to updates for only some shardchains, not necessarily all of them.
 
 
-- **TON Ecosystem services** like TON Proxy, TON Sites, TON Storage, and DApps run on these protocols.
+- **TON Ecosystem services** like TON Proxy, TON Sites, TON Storage, and dApps run on these protocols.
 
   Once the more sophisticated network protocols are in place to support the TON blockchain. 
-  They can easily be used for purposes not necessarily related to the immediate demands of the blockchain itself, thus providing more possibilities and flexibility for creating new services in the TON Ecosystem.
+  They can easily be used for purposes not necessarily related to the immediate demands of the blockchain itself, thus providing more possibilities and flexibility for creating new services in TON Ecosystem.
 
 ## TON network protocols
 

docs/v3/concepts/dive-into-ton/ton-ecosystem/wallet-apps.mdx

@@ -40,14 +40,14 @@ Here are some non-custodial wallets for TON Blockchain.
 
 ### Tonkeeper
 
-[Tonkeeper](https://tonkeeper.com/) is a central wallet in the TON Ecosystem. The Tonkeeper team developed it and has active support from both users and developers.
+[Tonkeeper](https://tonkeeper.com/) is a central wallet in TON Ecosystem. The Tonkeeper team developed it and has active support from both users and developers.
 
 <img src="/img/docs/wallet-apps/Tonkeeper.png?raw=true" alt="Tonkeeper" width="240" height="480" style={{ display: 'block', margin: 'auto' }}/>
 
 
 #### Highlights
-- This app is most popular with users.
-- Supports all up-to-date features, including NFT and Token transfer between user wallets.
+- This app is the most widely used.
+- Supports all up-to-date features, including NFT and token transfer between user wallets.
 - It supports all major platforms, such as iOS and Android, but it also works on popular browsers like Firefox or Chrome.
 
 #### Tonkeeper test environment
@@ -118,10 +118,10 @@ You must download a separate Sandbox application to connect to the Testnet.
 TonDevWallet is a wallet designed to simplify the development process for the TON Blockchain. It provides extensive tools and features to streamline your TON development experience.
 
 #### Highlights
-TonConnect Integration: TonDevWallet seamlessly integrates with TonConnect, allowing you to connect your wallet to TON-compatible websites easily.
+TON Connect integration: TonDevWallet seamlessly integrates with TON Connect, allowing you to connect your wallet to TON-compatible websites easily.
 - Store and manage multiple private keys within TonDevWallet, giving you the flexibility to access and control various accounts.
 - Create multiple wallets to organize and manage different accounts for your TON development projects.
-- Local transaction emulation lets you preview transaction results before executing them on the TON Blockchain. This feature helps you ensure the correctness of your transactions before submitting them to the blockchain.
+- Local transaction emulation lets you preview transaction results before executing them on TON Blockchain. This feature helps you ensure the correctness of your transactions before submitting them to the blockchain.
 
 #### Links
 - [GitHub](https://github.com/TonDevWallet/TonDevWallet)
@@ -242,7 +242,7 @@ Tonkey is an advanced project that introduces multi-signature functionality to T
 
 - [Explorers in TON](/v3/concepts/dive-into-ton/ton-ecosystem/explorers-in-ton/)
 - [What is blockchain? What is a smart contract? What is gas?](https://blog.ton.org/what-is-blockchain)
-- [Types of Wallet Contracts](/v3/documentation/smart-contracts/contracts-specs/wallet-contracts/)
+- [Wallet contracts](/v3/documentation/smart-contracts/contracts-specs/wallet-contracts/)
 
 <Feedback />
 

docs/v3/concepts/educational-resources.mdx

@@ -36,7 +36,7 @@ Russian
 </Button>
 
 
-#### TON blockchain development
+#### TON Blockchain development
 
 We're proud to present the __TON Blockchain course__, 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/v3/contribute/content-standardization.mdx

@@ -22,6 +22,54 @@ Examples:
 - "color" over "colour"
 - "analyze" over "analyse"
 
+### Use present tense
+
+Use present tense to describe general behavior, current functionality, and step-by-step instructions.
+This makes documentation clear and easy to follow.
+
+**Examples:**
+- This guideline provides an overview of the contribution process.
+- The system checks the file format and shows an error if it is invalid.
+
+*Avoid future or past tense for immediate or typical actions.*
+
+**Avoid:**
+- The system will check the file format.
+- The user clicked the button.
+
+### When to use the future or past tenses
+
+Present tense is standard, but future and past tenses are allowed in specific cases.
+
+**Future tense:** for actions that happen later, after a condition or delay.
+
+**Examples:**
+- After setup, the system will send a confirmation email.
+- If payment fails, the user will get a notification.
+
+*Avoid the future tense for immediate behavior or unreleased features. Also, avoid *would*.*
+
+**Avoid:**
+
+- The system will check the file format.
+- The API would return an error.
+
+
+**Past tense:** for describing past events like changelogs or logs.
+
+**Examples:**
+- Version 2.1 fixed a validation issue.
+- The user submitted the form at 2 pm and got a 500 error.
+
+*Avoid past tense in general documentation — it can imply outdated info.*
+
+**Avoid:**
+
+- The system checked the user’s location.
+- The user clicked the button.
+
+
+
 ### Use active voice
 
 Sentences using active voice are more concise and efficient, making your writing more engaging and easier to comprehend.
@@ -61,6 +109,23 @@ Use the **"Mon D, YYYY"** format. This approach is standard for American readers
 
 Adhering to these guidelines creates a unified approach to presenting dates, fostering clarity and comprehension throughout the TON documentation.
 
+### Use of emojis and icons
+
+#### In the Documentation section:
+- Avoid using emojis and decorative icons.
+- Technical documentation should be clear, professional, and distraction-free.
+- Use only standard formatting elements like headings, lists, and code blocks.
+
+#### In the Guidelines section:
+- Emojis and icons are allowed to make content more engaging and friendly.
+- Use them purposefully and consistently, preferring functional icons such as:
+
+✅ Success, ⚠️ Warning, ❌ Error.
+- Always use icons with supporting text — don’t rely on icons alone to convey meaning.
+- Avoid overly decorative or emotional emojis that don’t add meaning.
+- When in doubt, skip the icon. Clarity, consistency, and neutrality come first.
+
+
 ## Link preferences
 
 ### Linking to internal pages
@@ -556,6 +621,26 @@ When using these words, refer to them in lowercase unless they are the first wor
 - Node
 - Liteserver
 
+### BoC, bag of cells
+
+- Use either the abbreviation **BoC** or the full term **bag of cells**.
+- **Bag of cells** is capitalized only when it starts a sentence or heading. In all other cases, write **bag of cells** in lowercase.
+- Always abbreviate **BoC**. Do not use **BOC** or **boc**.
+
+**Correct usage:**
+
+- BoC
+- Bag of cells
+- bag of cells
+
+
+**Incorrect usage:**
+
+- BOC
+- boc
+- Bag Of Cells
+- Bag of Cells
+
 ## See also
 
 - [How to contribute](/v3/contribute/)

docs/v3/contribute/typography.mdx

@@ -60,6 +60,32 @@ Despite the overall _sentence case_ rule,
 #### Header consistency:
 - Avoid repeating the exact words in consecutive headers.
 
+#### Header formatting:
+
+Use plain text for all headers.
+Avoid using any formatting styles in headings:
+
+- No code formatting `backticks` (``)
+- No bold **text**
+- No italics *text*
+- No quotation marks (“ ” or " ")
+- No ALL CAPS (unless it's an acronym)
+
+Keep headers clean and consistent. Use formatting only in body text.
+
+**Correct:**
+
+- Run the TON Center service
+- How the smart contract works
+
+**Incorrect:**
+
+- *Run the TON Center service*
+- How the `smart contract` works
+- “Run the TON Center service”
+- HOW THE SMART CONTRACT WORKS
+
+
 #### Capitalized terms in headers
 
 Sometimes, you can face specific capitalization defined as capitalized according to American English rules.