TON Docs LLM Fuzz (4th week): 179 issues (25/26) #1429
Description
- *4326. Rename .ton domains heading
The heading uses a wildcard asterisk that can misparse; rename it to ".ton domains" to avoid ambiguity.
- 4327. Remove unnecessary escapes in inline code
Inline code unnecessarily escapes quotes; change sha256("dns_next_resolver") to sha256("dns_next_resolver").
- 4328. Update link to TON DNS standard to TEP-81
The page links to a TIPs issue; replace it with https://github.com/ton-blockchain/TEPs/blob/master/text/0081-dns-standard.md.
- 4329. Clarify TonWeb initialization context
The example assumes an initialized TonWeb instance; add a brief note or one-line initialization indicating that a TonWeb instance (e.g., tonweb) is created before use.
- 4330. Broaden supported domains to .ton and .t.me
The text claims only .ton domains are recognized; update it to state that TON DNS currently supports .ton and .t.me domains.
- 4331. Add internal link for configuration parameter 4
The mention of network config #4 links externally; add an internal cross‑reference to docs/v3/documentation/network/configs/blockchain-configs.mdx#param-4 (optionally keep the external link).
- 4332. Clarify .ton contract as DNS collection, not resolver
“The .ton domain resolver acts as an NFT collection” is ambiguous; replace with “The .ton DNS collection contract acts as an NFT collection, while each .ton domain is an NFT item.”
- 4333. Replace 'community vote' with 'validator vote'
The governance phrasing is inaccurate; change it to “a validator vote to update configuration parameter 4.”
- 4334. Remove speculative phrasing about future changes
Replace “This may change in the future.” with the neutral conditional “If new top‑level domains are added, it would require deploying a new root DNS smart contract and a validator vote to update configuration parameter 4.”
- 4335. Fix addresses link target and text
Update the “TON smart contract address system” link to point directly to /v3/documentation/smart-contracts/addresses/address and change the link text to “Smart contract addresses” to match the destination heading.
- 4336. Align capitalization in identical comments
Make both identical comments use the same sentence case: ;; assuming that 'subdomain' is not empty.
- 4337. Clarify leading zero byte sentence
Replace “It is skipped if the subdomain begins with zero byte.” with “If the subdomain begins with a zero byte, the function skips that leading byte.”
- 4338. Remove stray parenthesis in example state
Fix the example to subdomain_sfx = "" (remove the extra )).
- 4339. Use self-anchor for Appendix link
Change the link subresolvers#appendix-1-code-of-resolve-contractton to a same-page anchor #appendix-1-code-of-resolve-contractton or add an explicit heading ID {#appendix-1-code-of-resolve-contractton}.
- 4340. Rephrase warning and fix lowercase wording
Reword the note to state the limitation without attributing it to case-insensitivity, change “results in the lowercase” to “results in lowercase,” and ensure “WorkChain” is capitalized if mentioned.
- 4341. Use possessive in dns_next_resolver sentence
Change to “by updating the domain’s dns_next_resolver record.”
- 4342. Fix TL‑B code block formatting
ton-docs/docs/v3/guidelines/web3/ton-dns/subresolvers.mdx
Lines 162 to 165 in ee42357
Remove the inner backticks and use a single fenced block with a language hint (e.g., text) containing the TL‑B line.
- 4343. Retitle “Creating own” section
Change the heading to “Creating your own subdomain manager.”
- 4344. Retitle “Processing records update” section
Change the heading to “Processing record updates.”
- 4345. Fix comment: “Searching for a zero byte”
Change ;; Searching zero byte. to ;; Searching for a zero byte.
- 4346. Use TIP‑81 link for TON DNS standard
Update the standard reference to use the TIPs link and naming: link text “TON DNS standard” pointing to ton-blockchain/TIPs#81.
- 4347. Remove unsupported code fence tokens
Change code fences like func showLineNumbers to func; configure line numbers via site settings if needed.
- 4348. Correct FunC multi-return assignment
In “Resolving domains,” destructure parse_sd’s two returns and use the top label for lookup, e.g., (slice top, slice subdomain_suffix) = subdomain~parse_sd(); (cell records, _) = domains.udict_get_ref?(256, string_hash(top));.
- 4349. Align t.me branch comment with pattern
Update the inline comment to reflect the checked pattern "me"\0"t"\0<subdomain>\0[...], matching the starts_with("6D65007400"s) logic.
- 4350. Standardize leading zero byte representation
Use one consistent subdomain string representation across the walkthrough (either include the leading zero byte or not) and note that a leading zero, if present, is skipped by the resolver.
- 4351. Use correct Firefox labels: 'Settings...' and 'Manual proxy configuration'
In the Firefox section, use the correct labels—Settings → General → Network Settings → Settings... and Manual proxy configuration—and remove the unnecessary article before the option name.
- 4352. Standardize UI styling; remove quotes
UI labels and fields are inconsistently quoted and styled; consistently use bold for UI elements (e.g., Settings, Manual proxy configuration, HTTP Proxy, Server, Port, OK), remove quotation marks and “without quotes,” and use plain numerals like 8080.
- 4353. Restrict Safari guidance to macOS/iOS
Safari is only on Apple platforms; change the text to direct users to macOS or iOS instructions below with in‑page links to #macos and #ios.
- 4354. Add Android 'Proxy' step before 'Manual'
Explicitly include the Proxy selection so the flow reads Modify Network → Advanced options → Proxy → Manual.
- 4355. Separate Windows address and port fields
Clarify that the entry proxy address goes in Address and the value 8080 goes in Port (do not enter the address in the Port field).
- 4356. Correct macOS path and separate port field
Use System Settings/Preferences → Network → [Interface] → Details/Advanced → Proxies → Web Proxy (HTTP), and enter the proxy in Server with 8080 in the Port field (not host:port in one field).
- 4357. Define 'entry proxy' and add cross-reference
Replace the undefined phrase “public entry proxy” with clear guidance—e.g., “Enter the address of your entry proxy (for a local proxy, use 127.0.0.1)”—and add a first‑mention cross‑reference to docs/v3/guidelines/web3/ton-proxy-sites/running-your-own-ton-proxy.mdx#running-an-entry-proxy and docs/v3/guidelines/web3/ton-proxy-sites/running-your-own-ton-proxy.mdx#accessing-ton-sites.
- 4358. Link Chrome section to OS anchors
Update the Chrome section to link directly to this page’s OS sections (Windows, macOS, Ubuntu, iOS, Android) using in‑page anchors (#windows, #macos, #ubuntu, #ios, #android).
- 4359. Fix H1 to declarative plural form
Change "How to open any TON Site?" to a statement without a question mark and use plural: "How to open TON Sites".
- 4360. Reword heading for browsing domains
Change "Browse through the ton.run or tonp.io" to the more natural "Browse via ton.run or tonp.io".
- 4361. Link both domains and use plural consistently
Link both ton.run and tonp.io and remove the definite article; use plural "TON Sites" (e.g., "... open ton.run or tonp.io and browse TON Sites.").
- 4362. Remove time-sensitive “soon” about TON Wallet
Replace "TON Wallet ... will support it soon" with a time-agnostic statement: "TON Wallet support for TON Proxy is planned; check the extension page for current status."
- 4363. Soften superlative security claims
Change "This is the most secure way of accessing TON Sites." to a neutral form such as "This is a secure way to access TON Sites," and remove similar "most secure" phrasing elsewhere.
- 4364. Replace non-descriptive “from here” link text
Change the anchor text "from here" to descriptive text: "Download the latest version from GitHub" linking to https://github.com/xssnick/Tonutils-Proxy#download-precompiled-version.
- 4365. Consolidate duplicated Tonutils-Proxy steps
Remove the redundant instruction list and its introductory sentence, and keep a single concise two-step list: 1) Download the latest release from GitHub; 2) Launch the app and click Start Gateway.
- 4366. Normalize “Start Gateway” label formatting
Format the button label consistently using backticks in all instances: Start Gateway.
- 4367. Match “See also” link text to target page
Change the link text "Run C++ implementation" to "Running your TON Proxy" while keeping the same URL.
- 4368. Clarify intro wording
Change "require additional steps to start" to "require additional steps to set up" for clearer phrasing.
- 4369. Fix H2: "Running a TON Site"
Change "Running TON Site" to "Running a TON Site" for proper grammar and consistency with related pages.
- 4370. Clarify reverse proxy terminology and capitalize product name
Rephrase to avoid conflating the client TON Proxy with the server reverse proxy and capitalize the product: "Install the Tonutils Reverse Proxy to serve your website via TON Sites."
- 4371. Simplify H3 title: "Installation on Linux"
Change "Installation on any Linux" to "Installation on Linux" for natural phrasing.
- 4372. Fix heading hierarchy under Linux section
Use H4 for "Download", "Run", and "Use"; nest "Run without domain" as an H5 under "Run" to maintain a proper hierarchy.
- 4373. Rephrase domain run instruction and update placeholder
Replace "Run with domain configuration and follow the following steps:" with "Run with your TON DNS domain:" and change the placeholder to "<your-domain.ton>".
- 4374. Add bash language tags to command blocks
Add the bash language specifier to both unlabeled code fences for consistent syntax highlighting.
- 4375. Remove trailing space in domain command
Delete the trailing space after "your-domain.ton" to prevent copy-paste errors.
- 4376. Use correct term: "ADNL address"
Replace ".adnl domain" with "ADNL address (suffix .adnl)" for terminology consistency.
- 4377. Rename "Use" to "Usage"
Change the subheading "Use" to "Usage" to follow common documentation conventions.
- 4378. Specify config.json path and creation
State where config.json is located or generated by default and how to point the binary to a custom path, so users know where to edit it.
- 4379. Confirm and document added HTTP headers
Verify the header names (e.g., X-Adnl-Ip, X-Adnl-Id) and document their meanings or link to a reference.
- 4380. Deduplicate and correct other OS instructions
Remove the duplicated sentence, capitalize "Linux," and replace "as in step 2 for Linux" with "using the same command shown for Linux"; keep a single corrected note that a Go environment is required.
- 4381. Clarify which proxy is running
Replace "the TON Proxy should be running" with "the reverse proxy should be running" to avoid ambiguity with the client entry proxy.
- 4382. Explain how to find the generated ADNL address
Specify where the generated ADNL address is shown and how to copy it (e.g., printed in the proxy output).
- 4383. Update "See also" link text to match target page
Change the link text from "Run C++ implementation" to "Running your TON Proxy" to match the target page title.
- 4384. Standardize author name and handle
Use "Andrey Burnosov" and "@AndreyBurnosov" to match the linked profiles consistently.
- 4385. Fix typo: ANDL → ADNL
Replace every occurrence of “ANDL” with the correct term “ADNL” in step titles and descriptions (e.g., “Generate a persistent ADNL address”) to match canonical usage (see docs/v3/documentation/network/protocols/adnl/overview.mdx).
- 4386. Fix fragment and wrong link in “Accessing TON Sites”
Rewrite the opening line as a complete sentence and link to the local section: “Once your RLDP-HTTP proxy is running on localhost:8080, as described in Running an entry proxy (#running-an-entry-proxy), you can verify your setup with curl.”
- 4387. Replace invalid example IPs
Replace invalid addresses like 777.777.777.777 and 333.333.333.333 with placeholders (<your_public_ip>, <YOUR_WEB_SERVER_HTTP_IP>) or reserved documentation IPs (e.g., 203.0.113.10) to avoid impossible IPv4 values.
- 4388. Make ADNL hex/file name consistent (…E2BD)
The sample ADNL ends with …E2BD but the text says the private key is saved to 45061…2DB; correct the transposed characters to 45061…E2BD everywhere this sample pair appears.
- 4389. Number the “Run rldp-http-proxy” step
After “2. Download the TON global config”, prefix “Run rldp-http-proxy” with “3.” to keep the ordered steps consistent.
- 4390. Add language tags to code fences
Add bash to shell command fences and html to the HTML snippet; use text for output-only blocks. Update at least: the first curl example under “Accessing TON Sites”; the rldp-http-proxy “Example” under “Running an entry proxy on a remote computer”; the rldp-http-proxy “Example” under “Run the proxy in reverse mode”; the -R '*'@: snippet and its example.
- 4391. Use “an HTTP” (article before acronym)
Change “a HTTP …” to “an HTTP …” wherever applicable to follow standard article usage before vowel sounds.
- 4392. Prefer “HTTP requests” over “HTTP queries”
Replace “HTTP queries” with “HTTP requests” for consistency with RLDP documentation (see docs/v3/documentation/network/protocols/rldp.mdx#rldp-http).
- 4393. Align Firefox proxy steps with canonical page
Match wording/labels to docs/v3/guidelines/web3/ton-proxy-sites/connect-with-ton-proxy.mdx#firefox: Settings → General → Network Settings → Configure; choose Manual proxy settings; set HTTP Proxy 127.0.0.1, Port 8080.
- 4394. Clarify HTTP proxy address usage
Avoid implying users should browse to http://localhost:8080 or http://<your_public_ip>:8080; clarify these are HTTP proxy endpoints to configure in clients (or use with curl -x), and cross-reference connect-with-ton-proxy.mdx for setup.
- 4395. Note executable path differences for prebuilt binaries
Add a note that when using prebuilt release binaries, paths differ from build-tree examples (e.g., run ./rldp-http-proxy from the download directory); adjust commands accordingly.
- 4396. Neutralize phrasing for “.adnl” suffix
Change “use the ADNL address directly with a fake .adnl domain” to a neutral phrasing like “use the ADNL address with the .adnl suffix.”
- 4397. Rephrase unsourced “TON Proxy 2.0 anonymity” claim
Remove the version-specific claim or rephrase to a present-tense fact without versioning (e.g., “TON Proxy currently lacks anonymity features…”), unless a source is cited.
- 4398. Document the -A flag
Add a parameter note explaining that -A <your_adnl_address> specifies the persistent ADNL address generated earlier.
- 4399. Replace “mainly when” with “especially when”
In the sentence about HTTPS/TLS not being required due to ADNL encryption, change “mainly when the entry proxy is hosted locally” to “especially when the entry proxy is hosted locally” for more natural phrasing.
- 4400. Title-case H1 and replace ampersand
Change “Site & domain management” to “Site and Domain Management” for title case consistency and to avoid “&”.
- 4401. Generalize extension naming
Replace “Install the TON Chrome extension” with “Install a TON wallet extension (e.g., TON Wallet or MyTonWallet).”
- 4402. Use “owns the domain”
Replace “holds the domain” with “owns the domain” for clarity and consistency.
- 4403. Make recovery callout title singular
Change the callout header from “Recovery phrases” to “Recovery phrase”.
- 4404. Correct recovery phrase length
Change “Your recovery phrase consists of 24 words” to “Your recovery phrase consists of 12 or 24 words.”
- 4405. Fix restoration wording
Replace “You can restore this phrase …” with “If you lose access, you can restore your wallet in any TON wallet app using this recovery phrase.”
- 4406. Remove product-specific private key path
Replace the Tonkeeper-specific “Settings → Wallet protection → Your private key” line with “Refer to your wallet’s documentation to view or back up your recovery phrase.”
- 4407. Strengthen storage and no‑sharing guidance
Replace with: “Store your recovery phrase securely. Never share it with anyone; anyone with access can control your funds.”
- 4408. Add Testnet DNS hint
Append: “(Use https://dns.ton.org/?testnet=true on Testnet.)”
- 4409. Use “Toncoin”
Replace “coins” with “Toncoin” for accurate currency naming.
- 4410. Say “hexadecimal format”
Replace “in HEX format” with “in hexadecimal format”.
- 4411. Link to DNS subresolvers reference
Append: “See TON DNS resolvers for details.” linking to docs/v3/guidelines/web3/ton-dns/subresolvers.mdx.
- 4412. Pin smart contract links to SHAs
The links to https://github.com/ton-blockchain/ton/blob/master/crypto/smartcont/dns-manual-code.fc and https://github.com/ton-blockchain/ton/blob/master/crypto/smartcont/dns-auto-code.fc should be updated to blob//… to avoid master-branch drift.
- 4413. Remove extra blank lines before Feedback
Reduce multiple consecutive blank lines before the closing “” component to a single blank line.
- 4414. Use title case in H1
Change the page title to title case: "# TON Sites for Applications".
- 4415. Add article “a” before “TON Site” in H2 and sentence
Add the missing article in both places: change the H2 to "## How to support a TON Site in your application?" and the sentence to "You can launch a TON Site in your application by directly integrating a local entry proxy into your product."
- 4416. Link “entry proxy” to setup section
Link the phrase "entry proxy" to /v3/guidelines/web3/ton-proxy-sites/running-your-own-ton-proxy#running-an-entry-proxy to guide readers to the setup instructions.
- 4417. Correct “Andriod” to “Android”
Fix the misspelling in the list item to "- Android".
- 4418. Add space in CPU frequency unit
Text reads “At least 1GHz”; insert a space between number and unit: “At least 1 GHz”.
- 4419. Normalize bandwidth unit to Mbps
Use “10 Mbps” instead of “10 Mb/s” for standard unit formatting.
- 4420. Use plural “instructions” and drop “the” before “source”
Change “from the source using this instruction” to “from source using these instructions”.
- 4421. Clarify and link overlay network wording
Change to “Each bag is distributed via its own overlay network.” and link “overlay network” to /v3/documentation/network/protocols/overlay.
- 4422. Rewrite data block sentence to avoid hyphen
Replace “Data block - starts with a torrent header ...” with “The data block starts with a torrent header ...”.
- 4423. Capitalize Merkle and hyphenate SHA-256
ton-docs/docs/v3/guidelines/web3/ton-storage/storage-daemon.mdx
Lines 38 to 44 in ee42357
Capitalize “Merkle” (tree/root/proofs) and format “SHA-256”; use “hash-based Merkle tree”.
- 4424. Standardize bagID casing in prose
Use inline code “bagID” consistently in prose (e.g., keep L46 as bagID; replace backticked “BagID” at L175 with “bagID”), and keep “” as the placeholder in command syntax.
- 4425. Standardize “bag metafile” terminology
Use “bag metafile” throughout (e.g., “You can also save the bag metafile”) and use the placeholder “” in commands.
- 4426. Remove colon from “Starting storage-daemon” heading
Change “### Starting storage-daemon:” to “### Starting storage-daemon”.
- 4427. Add bash language tags to shell code fences
Add the language identifier “bash” to the opening code fences of all shell/CLI command examples for syntax highlighting.
- 4428. Improve CLI start phrasing
Replace “It’s started like this:” with “Start it as follows:”.
- 4429. Clarify CLI -I vs daemon -p and CLI -p
Explain that storage-daemon-cli uses “-I :” where equals the daemon’s “-p” (TCP console port), and that in storage-daemon-cli “-p” is the server public key path (not a port).
- 4430. Use “on” for first startup
Change “auto-generated at first daemon startup” to “auto-generated on first daemon startup”.
- 4431. Clarify default save directory wording
Replace with “If -d is omitted, the bag is saved to the storage daemon’s default directory.”
- 4432. Add missing article before list command
Change to “visible in the list output using the list command”.
- 4433. Lowercase “bag” in info sentence
Change “shows full information about the Bag” to “shows full information about the bag”.
- 4434. Retitle section to “Partial downloads and priorities”
Change the heading “Partial download, priorities” to “Partial downloads and priorities”.
- 4435. Resolve branch guidance (Testnet vs master)
Remove “The current version of the storage daemon is available in the Testnet branch.” or rephrase to a neutral pointer such as “See source code in the TON repository” (https://github.com/ton-blockchain/ton/) and rely on the compile instructions page for branch selection (or explicitly instruct to check out the required branch).
- 4436. Clarify Merkle root list wording in “Torrent info”
Rephrase “Torrent info contains the Merkle root of the following:” to separate field listings from the Merkle root, e.g., list the fields normally and state that the section also includes a Merkle root computed over the data block.
- 4437. Fix placeholder in add-by-meta example
Change the non-interactive example from -c "add-by-meta m" to -c "add-by-meta " for clarity.
- 4438. Add missing BagID to remove --remove-files
Update the example to include the identifier: remove --remove-files .
- 4439. Clarify SSD requirement phrasing
Change “At least 2 GB SSD, excluding space for torrents” to “At least 2 GB free SSD (excluding space for bag data).”
- 4440. Align wording to “bag” instead of “torrent”
Replace “the daemon begins sharing the torrent” with “the daemon begins sharing the bag,” reserving “torrent” only for protocol analogies.
- 4441. Align DNS field names with DNS guide
Align this page’s DNS field names/options with the documented UI in the DNS guide, or add a short note mapping fields and link to docs/v3/guidelines/web3/ton-proxy-sites/site-and-domain-management.mdx#how-to-link-a-ton-site-to-a-domain; if the UI truly has a "Storage" field or "Host in TON Storage" toggle, reflect it consistently across both pages.
- 4442. Define or remove tonstorage:// scheme
Either link to a page that defines the tonstorage:// scheme and resolution rules, or present it as tonstorage:/// with a brief note that is a 64‑character hex hash (see storage-daemon.mdx#adding-a-bag-of-files); if the scheme is not user-facing, remove or replace it.
- 4443. Capitalize “TON Site” in headings
Update headings to "How to host a static TON Site in TON Storage" and "How to host a static TON Site in TON Storage (low‑level)" for consistency with other pages.
- 4444. Standardize BagID placeholder and definition
Use consistently in text and examples (including the URI example) and, on first use, add that it is a 64‑character hex hash with a reference to storage-daemon.mdx#adding-a-bag-of-files.
- 4445. Add extension confirmation step
In both DNS-edit procedures, after "Save" add "Confirm the transaction in the extension." to match the DNS guide workflow.
- 4446. Add tlb language tags to code fences
Annotate both TL‑B code blocks with the tlb language tag for syntax highlighting (start the code fence with tlb).
- 4447. Format DNS record keys as code
Refer to DNS keys with code formatting and consistent casing, e.g., “assign the value to the sha256("storage") DNS record” and similarly for sha256("site").
- 4448. Clarify wallet extension link and fix list bullets
Replace the ambiguous “TON extension” link text with “TON Wallet” or “wallet browser extension (TON Wallet or MyTonWallet)”, and remove the stray “or” bullet by listing both extensions cleanly or combining into a single sentence.
- 4449. Stabilize NFT migration GitHub links
Make the two GitHub links consistent and stable: avoid mixing main and pinned commits; pin both to a specific commit (optionally keep line anchors) or remove line anchors to prevent brittleness.
- 4450. Cross-link DNS editing guide
After instructing to open dns.ton.org, add a short note linking to docs/v3/guidelines/web3/ton-proxy-sites/site-and-domain-management.mdx#how-to-open-a-domain-for-editing to keep UI expectations consistent.
- 4451. Fix repository links and line anchors
Replace the broken SpyCheese constants.fc link with https://github.com/ton-blockchain/ton/blob/master/storage/storage-daemon/smartcont/constants.fc#L4 and update all GitHub source references to the official ton-blockchain/ton repository using blob (not tree) on the master branch so line anchors work and branch usage is consistent.
- 4452. Remove duplicate provider parameters list and standardize style
Delete the first “Provider parameters” bullet list and keep the “The output includes the following parameters” list, standardizing punctuation and lowercasing “bag.”
- 4453. Standardize “bag” terminology
Use lowercase plain “bag” throughout (no emphasis) except in code or placeholders like .
- 4454. Add bash fences for CLI commands
Mark all CLI examples with bash and wrap standalone inline commands in fenced bash blocks (e.g., get-provider-params, new-contract-message, deploy-provider, get-provider-info variants, set-provider-config/params, send-coins, withdraw, withdraw-all, close-contract).
- 4455. Fix malformed list after enabling accept
Convert the lead sentence into a paragraph and follow with two bullets (or nest them) so only the actions “download and distribute bags” and “generate and submit storage proofs” are list items.
- 4456. Make step 1 verbs parallel
Change to “The owner of the provider launches the storage-daemon, deploys the main smart contract, and configures the necessary parameters.”
- 4457. Remove redundancy in “configure the provider configuration”
Change to “Before activation, configure the provider settings stored in storage-daemon and the on-chain contract parameters.”
- 4458. Use consistent capitalization for “query ID”
Standardize on “query ID” (lowercase “query,” except at the start of a sentence).
- 4459. Use plural “proofs” where applicable
Refer to recurring submissions as “storage proofs” (plural) for accuracy.
- 4460. Clarify sender in client-initiated closure
Replace “from the address with any query ID” with wording that specifies the client’s wallet as the sender and that the message may use any query ID.
- 4461. Standardize apostrophes
Use straight quotes (') consistently instead of mixing curly and straight apostrophes.
- 4462. Improve “prevent disrupting” phrasing
Change to “To avoid disrupting the provider's operations, …”.
- 4463. Use plural “instructions”
Change “follow the instruction” to “follow the instructions.”
- 4464. Clarify min/max size applies to bag
Resolve the “min/max file size” vs bag size ambiguity by renaming to “min bag size”/“max bag size” or by stating explicitly that --min-file-size/--max-file-size set per-bag size limits.
- 4465. Rename section “Using a provider by clients”
Retitle to “Using a provider” (or “Client usage”) for idiomatic English.
- 4466. Rename section “A request to store”
Retitle to “Storage request” for clarity.
- 4467. Normalize “from source” wording
Use a single form “from source” consistently (not “from sources”/“from the source”).
- 4468. Replace “exact process” with “same process”
Change “The exact process occurs automatically …” to “The same process occurs automatically …”.
- 4469. Specify tool for the
listcommand
Clarify that “list” is a storage-daemon-cli command (e.g., “storage-daemon-cli list”).
- 4470. Rephrase “releases the files”
Change to “allows retrieval of the files” to avoid implying on-chain file storage.
- 4471. Clarify parameter viewing commands
Explain when to use get-provider-params (on-chain parameters) versus get-provider-info (local daemon state), or standardize on one and note the distinction.
- 4472. Use canonical working directory path (/var/ton-work)
Replace every occurrence of /var/ton/ with the canonical /var/ton-work/ to align with paths used across the docs (e.g., db and logs locations).
- 4473. Fix symlink command target and link name
Update the symlink example to correctly point the link to /opt/ton and use the canonical link name: ln -s /opt/ton /var/ton-work.
- 4474. Correct MyTonCtrl vs MyToncore log locations
Change the statement about logs in /.local/share/mytonctrl/ to: “/.local/share/mytonctrl/: MyTonCtrl metadata (e.g., VERSION); logs are in ~/.local/share/mytoncore/mytoncore.log (or /usr/local/bin/mytoncore/mytoncore.log when run as root).”
- 4475. Refer to mytoncore as a service, not a script
Reword to: “MyTonCtrl includes the mytoncore background service, which stores files in …” to match systemd usage elsewhere.
- 4476. Remove non-canonical uninstall rm command
Delete the extra step sudo rm -rf /usr/bin/ton and keep the uninstall flow as only sudo bash /usr/src/mytonctrl/scripts/uninstall.sh.
- 4477. Clarify root install section: logs vs configs
Change “The configurations will be stored differently” to “When installed as root, some MyTonCtrl files (e.g., logs) are under: 1) /usr/local/bin/mytonctrl/ 2) /usr/local/bin/mytoncore/.”
- 4478. Remove bogus “man git-fork” instruction
Delete the man git-fork line and instead say “Refer to your Git hosting provider’s documentation on forking a repository.”
- 4479. Fix post-install move: avoid glob; use canonical path
Replace mv /var/ton/* /opt/ton/ with a safe, canonical move that preserves dotfiles (e.g., mv /var/ton-work /opt/ton-work or rsync -a /var/ton-work/ /opt/ton-work/).
- 4480. Add checklist for path changes after directory move
Expand the note beyond mytoncore.db to instruct updating the systemd unit (e.g., validator.service), /var/ton-work/db/config.json, and file ownership/permissions after changing directories.
- 4481. Replace vague experience note with actionable caution
Swap the “Consider experience…” sentence for a docs-style caution admonition advising to back up data and verify service configuration before proceeding.
- 4482. Rephrase validator wording (tool vs node)
Change “…confirm if MyTonCtrl has become a full validator” to “This guide helps you confirm your node is acting as a validator,” using “validator” consistently and not “full validator.”
- 4483. Replace underline+bold with an admonition
Remove the ... backup reminder and present it as a proper admonition block (e.g., :::caution) per docs style.
- 4484. Use “get methods” consistently (no hyphen)
Replace every “get-method” with “get methods”; e.g., change “Processing get-method requests…” to “Processing get methods requests…”.
- 4485. State name in metadata: use
nonexist(notnonexisting)
In the Metadata section list, replace the token nonexisting with the canonical nonexist.
- 4486. Contract type label: use
walletv5r1(no underscore)
In the Metadata example, change wallet_v5r1 to walletv5r1.
- 4487. Remove hard-coded faucet amount
In the Testnet section, remove the exact “2 Toncoin” amount and state that you will receive test Toncoin in your wallet.
- 4488. Tonkeeper UI label: “Testnet Account”
Update the instruction to use the exact UI label with spacing and capitalization: Wallet → Add Wallet → Testnet Account.
- 4489. Add descriptive alt text for Tonkeeper screenshots
Set a meaningful alt attribute for the ThemedImage (e.g., alt="Tonkeeper: adding a Testnet wallet and importing a mnemonic") instead of empty alt.
- 4490. Fix awkward phrasing in learning goals
Change “using the Blueprint for the smart contract development” to “using Blueprint for smart contract development.”
- 4491. Lowercase address state tokens in list
In the Address states section, render tokens in lowercase code style: nonexist, uninit, active, frozen.
- 4492. Fix Crowdin prerequisites link and style guide URL
In Prerequisites step 3, replace the circular self-link and wrong text “How to use crowdin” with “Crowdin online editor guide” linking to https://support.crowdin.com/online-editor/, capitalize “Crowdin,” and use the canonical Translation style guide path without a trailing slash: /v3/contribute/localization-program/translation-style-guide.
- 4493. Capitalize role in heading
Change the heading “Language coordinator guidelines” to “Language Coordinator guidelines” to match role capitalization used elsewhere.
- 4494. Align branch name to l10n_feat
In Developer guidelines steps 1 and 7, replace “i18n_feat” with “l10n_feat” to match the documented branch naming.
- 4495. Fix ISO placeholder typo
Change “YOUR_IOS_LANG_CODE” to “YOUR_ISO_LANG_CODE” in Developer guidelines step 6.
- 4496. Correct parts count in translator workspace
Change “Your workspace has four parts” to “three parts” to match the three listed areas (Top left, Bottom left, Bottom right).
- 4497. Remove unverified ‘within one hour’ SLA
Replace “The preview website displays all approved content within one hour.” with a non-time-specific statement such as “The preview website displays approved content after synchronization.”
- 4498. Replace vague contact instruction with actionable step
Change “Contact the Vercel owner of this repo” to “Open an issue in this repository requesting the language be added to the site menu” (or specify a concrete, maintained contact channel).
- 4499. Clarify pull request instruction
Replace “Create a PR request to the dev branch” with “Open a pull request from [lang]_localization to dev; do not merge—this PR is for preview only.”
- 4500. Standardize terminology to ‘Chinese (Simplified)’
Replace “Mandarin” with “Chinese (Simplified)” to align with the style guide (e.g., zh-CN).
- 4501. Improve non-descriptive image alt text
Replace terse alts like “proofread step1,” “to next,” and “manage-members” with descriptive, context-aware text (e.g., “Crowdin – Proofreader view with blue progress bar,” “Select next file dialog,” “Crowdin – Manage project members screen”) to improve accessibility.
- 4502. Correct ISO code guidance
Replace “ISO language code should be two letters, lowercase” with guidance that matches actual locale keys, e.g., “Use the site locale key (e.g., zh-CN, pt-BR); do not constrain to two lowercase letters.”
- 4503. Fix intro sentence grammar
Replace "After reading this article, you will understand why are NFTs helpful and how you can use them in one of your projects." with "After reading this article, you will understand why NFTs are helpful and how you can use them in your projects."
- 4504. Correct TON DNS article and on‑chain hyphenation
Replace "There is TON DNS service, which works fully onchain." with "The TON DNS service works fully on-chain."