diff --git a/doc/ConfigParam-HOWTO b/doc/ConfigParam-HOWTO
index 8432657a..c91bf335 100644
--- a/doc/ConfigParam-HOWTO
+++ b/doc/ConfigParam-HOWTO
@@ -26,7 +26,7 @@ Therefore, the structure of such parameters is determined in source file `crypto
     capabilities#c4 version:uint32 capabilities:uint64 = GlobalVersion;
     _ GlobalVersion = ConfigParam 8;  // all zero if absent
 
-We see that configuration parameter #8 contains a Cell with no references and exactly 104 data bits. The first four bits must be 11000100, then 32 bits with the currently enabled "global version" are stored, and 64-bit integer with flags corresponding to currently enabled capabilities follow. A more detailed description of all configuration parameters will be provided in an appendix to the TON Blockchain documentation; for now, one can inspect the TL-B scheme in `crypto/block/block.tlb` and check how different parameters are used in the validator sources.
+We see that configuration parameter #8 contains a Cell with no references and exactly 104 data bits. The first eight bits must be 11000100, then 32 bits with the currently enabled "global version" are stored, and 64-bit integer with flags corresponding to currently enabled capabilities follow. A more detailed description of all configuration parameters will be provided in an appendix to the TON Blockchain documentation; for now, one can inspect the TL-B scheme in `crypto/block/block.tlb` and check how different parameters are used in the validator sources.
 
 In contrast with configuration parameters with non-negative indices, configuration parameters with negative indices can contain arbitrary values. At least, no restrictions on their values are enforced by the validators. Therefore, they can be used to store important information (such as the Unixtime when certain smart contracts must start operating) that is not crucial for the block generation, but is used by some of the fundamental smart contracts.