From 98f3b1ea3cb369e245b03c583ae657f145874a92 Mon Sep 17 00:00:00 2001 From: camcui <166618273+camcui@users.noreply.github.com> Date: Mon, 20 Jan 2025 10:35:19 +0800 Subject: [PATCH] chore: fix spelling issues (#402) Signed-off-by: camcui --- docs/releases/history.md | 2 +- docs/using_javatron/backup_restore.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/releases/history.md b/docs/releases/history.md index f9c7e038..766c103e 100644 --- a/docs/releases/history.md +++ b/docs/releases/history.md @@ -334,7 +334,7 @@ node.rpc.reflectionService=true Source Code: [https://github.com/tronprotocol/java-tron/pull/5583](https://github.com/tronprotocol/java-tron/pull/5583) #### 6. Delete the LiteFullNodeTool related code under the framework module -In order to facilitate tool maintenance and developer use, TRON has launched the `Toolkit.jar` toolbox, which includes various TRON development tools. As early as the Aristotle version, the code related to the LiteFullNode data clipping tool has been integrated into the `Toolkit` toolbox (located under the plugin module), and `Tookit` can completely replace `LiteFullNodeTool` (located under the framework module). Therefore, the Bias version deletes the `LiteFullNodeTool` related code under the framework module, which not only reduces code redundancy, but also makes the division of functional modules clearer. The commands to use the LiteFullNode data pruning function in the `Toolkit` are as follows: +In order to facilitate tool maintenance and developer use, TRON has launched the `Toolkit.jar` toolbox, which includes various TRON development tools. As early as the Aristotle version, the code related to the LiteFullNode data clipping tool has been integrated into the `Toolkit` toolbox (located under the plugin module), and `Toolkit` can completely replace `LiteFullNodeTool` (located under the framework module). Therefore, the Bias version deletes the `LiteFullNodeTool` related code under the framework module, which not only reduces code redundancy, but also makes the division of functional modules clearer. The commands to use the LiteFullNode data pruning function in the `Toolkit` are as follows: ``` $ java -jar Toolkit.jar db lite diff --git a/docs/using_javatron/backup_restore.md b/docs/using_javatron/backup_restore.md index 9d373a02..4b4e9bbd 100644 --- a/docs/using_javatron/backup_restore.md +++ b/docs/using_javatron/backup_restore.md @@ -54,7 +54,7 @@ The following table shows the download address of Fullnode data snapshots. Pleas | Official data source (North America: Virginia) | http://34.86.86.229/ | LevelDB, exclude internal transactions (About 1821G on 6 Aug. 2024) | | Official data source (Singapore) | http://34.143.247.77/ | LevelDB, exclude internal transactions (About 1819G on 5 Aug. 2024) | | Official data source (Singapore) | http://35.197.17.205/ | RocksDB, exclude internal transactions (About 1799G on 6 Aug. 2024) | -| Official data source (Singapore) | http://35.247.128.170/ | LevelDB, inlcude internal transactions (About 2000G on 6 Aug. 2024) | +| Official data source (Singapore) | http://35.247.128.170/ | LevelDB, include internal transactions (About 2000G on 6 Aug. 2024) | | Official data source ((North America: Virginia)) | http://34.48.6.163/ | LevelDB, exclude internal transactions, include account history TRX balance (About 2288G on 6 Aug. 2024) |