Added links leading to new articles

Author: xssnick

docs/learn/networking/low-level-adnl.md

@@ -73,6 +73,10 @@ The receiving peer must fetch the first 4 bytes, decrypt it into the `length` fi
 
 The first datagram in the session always goes from the server to the client after a handshake packet was successfully accepted by the server and it's actual buffer is empty. The client should decrypt it and disconnect from the server in case of failure, because it means that the server has not followed the protocol properly and the actual session keys differs on the server and client side.
 
+### Communication details
+
+If you want to dive into communication details, you could check article [ADNL TCP - Liteserver](/docs/develop/network/adnl-tcp) to see some examples.
+
 ### Security considerations
 #### Handshake padding
 It is unknown why the initial TON team decided to include this field into the handshake. `aes_params` integrity is protected by a SHA-256 hash and confidentiality is protected by the key derived from the `secret` parameter. Probably, it was intended to migrate from AES-CTR at some point. To do this, specification may be extended to include a special magic value in `aes_params`, which will signal that the peer is ready to use the updated primitives. The response to such a handshake may be decrypted twice, with new and old schemes, to clarify which scheme the other peer is actually using.
@@ -85,7 +89,8 @@ If an encryption key is derived only from the `secret` parameter, it will be sta
 It is not obvious why the `nonce` field in the datagram is present because, even without it, any two ciphertexts will differ because of the session-bounded keys for AES and encryption in CTR mode. However, the following attack can be performed in the case of an absent or predictable nonce. CTR encryption mode turns block ciphers, such as AES, into stream ciphers to make it possible to perform a bit-flipping attack. If the attacker knows the plaintext which belongs to encrypted datagram, they can obtain a pure keystream, XOR it with their own plaintext and efficiently replace the message which was sent by peer. The buffer integrity is protected by a SHA-256 hash, but an attacker can replace it too because having knowledge of a full plaintext means having knowledge of its hash. The nonce field is present to prevent such an attack, so no attacker can replace the SHA-256 without having knowledge of the nonce.
 
 ## P2P protocol (ADNL over UDP)
-TBD
+
+Detailed description can be found in article [ADNL UDP - Internode](/docs/develop/network/adnl-udp).
 
 ## References
 - [The Open Network, p. 80](https://ton.org/ton.pdf)

docs/learn/networking/overlay-subnetworks.md

@@ -28,6 +28,6 @@ Overlay subnetworks can be public or private.
 Overlay subnetworks work according to a special [gossip](https://en.wikipedia.org/wiki/Gossip_protocol) protocol.
 
 :::info
-Read more about ADNL overlay subnetworks in Chapter 3.3 of the [TON Whitepaper](https://ton.org/docs/ton.pdf).
+Read more about overlays in [Overlay subnetworks](/docs/develop/network/overlay) article, or in Chapter 3.3 of the [TON Whitepaper](https://ton.org/docs/ton.pdf).
 :::
 

docs/learn/networking/rldp.md

@@ -11,3 +11,7 @@ A reliable arbitrary-size datagram protocol built upon the ADNL, called RLDP,
 is used instead of a TCP-like protocol. This reliable datagram protocol can
 be employed, for instance, to send RPC queries to remote hosts and receive
 answers from them.
+
+:::info
+Detailed description with examples can be found in [RLDP](/docs/develop/network/rldp) article of `develop` section.
+:::

docs/learn/networking/ton-dht.md

@@ -64,5 +64,5 @@ new sequence number is larger (to prevent replay attacks).
 TON DHT is not only used to store the IP Addresses of ADNL Nodes, but is also used for other purposes - it can store a list of addresses of the nodes which are storing a specific torrent of TON Storage, a list of addresses of nodes included in an overlay subnetwork, ADNL Addresses of TON services or ADNL Addresses of accounts of the TON Blockchain and so on.
 
 :::info
-Read more about TON DHT in Chapter 3.2. of the [TON Whitepaper](https://ton.org/docs/ton.pdf).
+Read more about TON DHT in [DHT](/docs/develop/network/dht) article, or in Chapter 3.2. of the [TON Whitepaper](https://ton.org/docs/ton.pdf).
 :::

docs/learn/overviews/TL-B.md

@@ -140,6 +140,12 @@ The **Backus–Naur form** can be found at [TlbParser.bnf](https://github.com/an
 TL-B is also supported by [intellij-ton plugin](https://github.com/andreypfau/intellij-ton).
 
 Docs on TL-B can be found in the [TVM Whitepaper](https://ton.org/tvm.pdf) and in a concise (they have been collected in one place) format [here](https://github.com/tonstack/TL-B-docs).
+
 ## Generator of serializators and deserializators
 An example of a generator used by a TON node can be found in the [Ton node sources](https://github.com/ton-blockchain/ton/blob/master/crypto/tl/tlbc.cpp).
 
+## More about TL-B
+
+If you want to know more about TL-B serialization and see some examples of complex structures parsing, 
+you can continue by reading [TL-B](/docs/develop/data-formats/tl-b) article at `develop` section of documentation.
+

docs/learn/overviews/cells.md

@@ -43,6 +43,8 @@ Any object in TON (message, message queue, block, whole blockchain state, contra
 The process of serialization is described by a TL-B scheme: 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 to know more details about cell (de)serialization, you could read [Cell & Bag of Cells](/docs/develop/data-formats/cell-boc) article.
+
 :::tip TL-B
 Navigate to the [TL-B](/learn/overviews/TL-B) section for more information.
 :::