New Crowdin updates (#479)

* New translations constant.md (Chinese Simplified)

* New translations cfx-namespace.md (Chinese Simplified)

* New translations cfx-namespace.md (Chinese Simplified)

* New translations pos-namespace.md (Chinese Simplified)

* New translations trace-namespace.md (Chinese Simplified)

* New translations accounts.md (Chinese Simplified)

* New translations configuration-files.md (Chinese Simplified)

* New translations downloading-conflux-client.md (Chinese Simplified)

* New translations running-light-node.md (Chinese Simplified)

* New translations node-configuration.md (Chinese Simplified)

* New translations stratum.md (Chinese Simplified)

* New translations how-to-contribute.md (Chinese Simplified)

* New translations userguide.md (Chinese Simplified)

* New translations contributor-poaps.md (Chinese Simplified)

* New translations reward-guidelines.md (Chinese Simplified)

* New translations contracts.md (Chinese Simplified)

* New translations glossary.md (Chinese Simplified)

i18n/zh/docusaurus-plugin-content-docs/current/core/build/json-rpc/pos-namespace.md

@@ -91,7 +91,7 @@ Returns the current status of the PoS chain.
 
 `Empty`
 
-#### Returns
+#### 返回值
 
 `Object` - PoS status object.
 
@@ -149,7 +149,7 @@ params: [
 ]
 ```
 
-#### Returns
+#### 返回值
 
 `Object` - the account object, or `null` (if the account corresponding to the address does not exist)
 
@@ -202,7 +202,7 @@ Get the current PoS committee information in default. It is also able to get the
 
 1. [`QUANTITY`]:  block number, optional for querying the committee information at a certain block height
 
-#### Returns
+#### 返回值
 
 * `currentCommittee`: `OBJECT` -  current committee members, see [CurrentCommittee](#currentcommittee) for more information
 * `elections`: `Array` - nodes who are running for election
@@ -305,7 +305,7 @@ params: [
 ]
 ```
 
-#### Returns
+#### 返回值
 
 * `epoch`: `QUANTITY` - the epoch that the block is in
 * `hash`: `HASH` - the hash value of the block
@@ -381,7 +381,7 @@ Get block information by its block number
 
 1. `QUANTITY|TAG`: block number or block TAG（`latest_committed`, `latest_voted`）
 
-#### Returns
+#### 返回值
 
 the same as [pos_getBlockByHash](#pos_getblockbyhash)
 
@@ -414,7 +414,7 @@ params: [
 ]
 ```
 
-#### Returns
+#### 返回值
 
 * `accountRewards`: `Array` of [AccountReward](#accountreward)
 * `powEpochHash`: `HASH` - the hash value of the PoW block when the rewards are made
@@ -478,7 +478,7 @@ params: [
 ]
 ```
 
-#### Returns
+#### 返回值
 
 交易详情
 

i18n/zh/docusaurus-plugin-content-docs/current/core/build/json-rpc/trace-namespace.md

@@ -53,7 +53,7 @@ Get block traces by block hash
 
 1. DATA, 32 Bytes - hash of a block
 
-#### Returns
+#### 返回值
 
 * `blockHash`: `HASH` - Hash of block
 * `epochHash`: `HASH` - Hash of epoch
@@ -192,7 +192,7 @@ curl --location --request POST 'http://testnet-rpc:12537' \
 }
 ```
 
-#### Returns
+#### 返回值
 
 ### trace_transaction
 
@@ -202,7 +202,7 @@ Get transaction's trace by it's hash
 
 1. DATA, 32 Bytes - hash of a transaction
 
-#### Returns
+#### 返回值
 
 * `type`: `string` - Avaliable value is `call`, `create`, `call_result`, `create_result`, `internal_transfer_action`
 * `transactionPosition`: `QUANTITY` - Position of transaction in block
@@ -383,9 +383,9 @@ Get whole epoch transaction's trace by it's number
 
 #### 参数
 
-1. `QUANTITY|TAG` - the epoch number, or the string `"latest_mined"`, `"latest_state"`, `"latest_confirmed"`, `"latest_checkpoint"` or `"earliest"`, see the [epoch number parameter](#the-default-epochnumber-parameter).
+1. `QUANTITY|TAG` - 纪元号，或字符串`"latest_mined"`、`"latest_state"`、`"latest_confirmed"`、"`latest_checkpoint"`或`"earliest"`，请参见[纪元号参数](#the-default-epochnumber-parameter)。
 
-#### Returns
+#### 返回值
 
 TODO
 
@@ -405,7 +405,7 @@ Returns all traces matching the provided filter.
     * `after`: `QUANTITY` - (optional) The offset trace number.
     * `count`: `QUANTITY` - (optional) The number of traces to display in a batch.
 
-#### Returns
+#### 返回值
 
 Same as `trace_transaction`
 

i18n/zh/docusaurus-plugin-content-docs/current/core/core-space-basics/accounts.md

@@ -4,7 +4,7 @@ title: 账户
 displayed_sidebar: coreSidebar
 ---
 
-:::注意
+:::note
 
 本页面是为了提供有关 CORE SPACE ACCOUNTS 的信息。 Refer to [General-Accounts](../../general/conflux-basics/accounts.md) for the overall introduction of the concept of ACCOUNTS.
 

i18n/zh/docusaurus-plugin-content-docs/current/general/CONTRIBUTING/contributor-poaps.md

@@ -11,7 +11,7 @@ Contributor POAPs operate distinctly from [FC reward guidelines](./reward-guidel
 
 :::
 
-After the end of each quarter, we issue a batch of Contributor POAPs (Proof of Attendance Protocol) to recognize individuals who have made contributions to our documentation site. 想要有资格铸造一个 POAP，您的贡献必须符合以下 “ACCEPTED” 的标准：
+在每季度结束后， 我们将会发行一批贡献者 POAPs (活动参与证明)，以表彰为我们的文档网站做出贡献的贡献者。 想要有资格铸造一个 POAP，您的贡献必须符合以下 “ACCEPTED” 的标准：
 
 - 创建了一个被仓库维护者标记为 “ACCEPTED” 的问题。
 - 将拉取请求成功合并到主分支。
@@ -30,11 +30,11 @@ After the end of each quarter, we issue a batch of Contributor POAPs (Proof of A
 
 ## POAP 持有者的 FC（FansCoin）奖励
 
-As a token of appreciation, contributors can claim [FansCoin (FC)](https://confluxscan.io/token/cfx:achc8nxj7r451c223m18w2dwjnmhkd6rxawrvkvsy2) rewards for each POAP they own. The amount of FC awarded varies depending on the specific POAP.
+为了表达我们的感谢，贡献者可以凭借他们拥有的每个 POAP 领取 FansCoin（FC）奖励。 不同的 POAP 获得的 FC 奖励数量也各不相同。
 
 这是与POAP相关联的附加奖励，并不影响与 [奖励指南](./reward-guidelines.md)相关的奖励。
 
-> Please note that the FC reward pool is located exclusively in Core Space at [cfx:achm6kb92by13rpvwd04zscn1127zuaseu25usm7sc](https://confluxscan.io/address/cfx:achm6kb92by13rpvwd04zscn1127zuaseu25usm7sc).
+> 请注意，FC 奖池位于 Core Space [cfx:achm6kb92by13rpvwd04zscn1127zuaseu25usm7sc](https://confluxscan.io/address/cfx:achm6kb92by13rpvwd04zscn1127zuaseu25usm7sc)。
 
 ## 对于 POAP 发放规则的定期审查
 

i18n/zh/docusaurus-plugin-content-docs/current/general/CONTRIBUTING/how-to-contribute.md

@@ -31,16 +31,16 @@ displayed_sidebar: generalSidebar
 
 ## Create an Issue
 
-You can create an issue for the following purposes:
+您可以为以下目的创建一个问题：
 
 - 报告您发现的任何错误或打字/排版问题。
 - 请求新内容或对当前内容进行改进。
 
 您通常可以通过 [GitHub网页](https://github.com/Conflux-Chain/conflux-documentation/issues/new/choose) 直接创建一个问题。 在这里，您会找到各种模板来指导您的问题提交。
 
-![issue templates](../image/2023-04-13-15-16-53.png)
+![问题模板](../image/2023-04-13-15-16-53.png)
 
-If you're able to address the issue yourself, we encourage you to take the initiative. When creating an issue, you can indicate your willingness to resolve it. For bug reports, select the option “I'd be willing to fix this issue myself” in the BUG template. For feature requests, select “I'd be willing to contribute this feature myself” in the Feature Request template.
+如果您能够自行解决这个问题，我们鼓励您主动采取行动。 在创建问题时，您可以表明您愿意解决它。 For bug reports, select the option “I'd be willing to fix this issue myself” in the BUG template. For feature requests, select “I'd be willing to contribute this feature myself” in the Feature Request template.
 
 ```md
 
@@ -53,42 +53,42 @@ If you're able to address the issue yourself, we encourage you to take the initi
 
 另外，您也可以通过[ Conflux文档问题表单](https://forms.office.com/r/pKVBywZwLY) 提交您的问题。 如果您提交的问题被批准，它将在 GitHub 仓库中被创建。
 
-![Conflux Documentation Issue Form](../image/Conflux%20Documentation%20Issue%20Form.png)
+![Conflux 文档问题表单](../image/Conflux%20Documentation%20Issue%20Form.png)
 
 ## Create a Pull Request
 
-通过创建拉取请求（PR）对项目作出贡献是改进现有文档或代码十分有价值的方式。 This guide will walk you through the process step by step, ensuring clarity and ease of understanding, especially for those new to GitHub and git operations.
+通过创建拉取请求（PR）对项目作出贡献是改进现有文档或代码十分有价值的方式。 本指南将逐步引导您完成整个过程，确保清晰易懂，特别是对于那些对GitHub和git操作不熟悉的人。
 
-For complex operations, you can also check the [closed pull requests](https://github.com/Conflux-Chain/conflux-documentation/pulls?q=is%3Apr+is%3Aclosed) for grammar reference. For example,
+For complex operations, you can also check the [closed pull requests](https://github.com/Conflux-Chain/conflux-documentation/pulls?q=is%3Apr+is%3Aclosed) for grammar reference. 例如，
 
 - [Added Ecosystem Page + Video](https://github.com/Conflux-Chain/conflux-documentation/pull/392) shows how to add an article with video reference.
 - [feat: template example](https://github.com/Conflux-Chain/conflux-documentation/pull/410) shows how to make use of mdx's feature to create similar pages using template.
 
-:::注意
+:::note
 
-This process does not apply to [TRANSLATIONS](#provide-translation).
+此过程不适用于 [翻译](#provide-translation)。
 
 :::
 
 ### Minor Changes via Github Web UI
 
-For simple corrections or enhancements like typos or sentence improvements:
+对于简单的更正或完善，如拼写错误或句子改进：
 
-1. Navigate to the Page:
-   - Go to the **English version** of the page you wish to edit and click the "Edit this page" button. This button is typically found at the top or bottom of the page.
-     - ![Edit this page](../image/2024-01-04-17-09-22.png)
+1. 导航到页面：
+   - 前往您希望编辑的页面的**英文版本**并点击“编辑此页面”。 它通常位于页面的顶部或底部。
+     - ![编辑此页面](../image/2024-01-04-17-09-22.png)
 
-2. Forking the Repository:
-   - You'll be redirected to GitHub, where you might see a prompt saying, "You need to fork this repository to propose changes." Click "Fork this repository".
-     - ![Fork this repository](../image/2024-01-04-17-12-54.png)
+2. 分叉仓库：
+   - 您将被重定向到 GitHub，在那里您可能会看到一个提示，显示“您需要分叉这个仓库以提出更改”。 点击“分叉这个仓库”。
+     - ![分叉这个仓库](../image/2024-01-04-17-12-54.png)
 
-3. Making Edits:
-   - Once in the editor mode, make the necessary changes. After editing, scroll to the bottom where you'll find the "Commit changes" section. Fill in a brief description of your changes, then click "Propose changes".
+3. 进行编辑：
+   - 一旦进入编辑模式，您便可以进行必要的更改。 编辑内容后，滚动到底部，您会找到“提交更改”部分。 填写对于您更改的简短描述，然后点击“提交更改”。
 
-4. Submitting the Pull Request:
-   - After proposing changes, you'll be directed to a new page to initiate the pull request. Click "Create pull request". Double-check the changes and fill in any additional information if necessary, then finalize by clicking "Create pull request" again.
-     - Remember to check preflight checks by adding "x".
-     - ![preflight checks](../image/2024-01-04-17-36-59.png)
+4. 提交拉取请求：
+   - 提出更改后，您将被引导到一个新页面以发起拉取请求。 点击“创建拉取请求”。 仔细检查更改并填写任何必要的额外信息，然后再次点击“创建拉取请求”完成操作。
+     - 记得通过添加 "x" 以进行预检查核对。
+     - ![预检查](../image/2024-01-04-17-36-59.png)
 
 ### Local Development for Substantial Changes
 
@@ -98,23 +98,23 @@ For simple corrections or enhancements like typos or sentence improvements:
 
 :::
 
-For more significant contributions like adding a new page or extensive revisions:
+对于添加新页面或广泛的修订等更重大的贡献：
 
-1. Setting Up:
-   - Ensure you have [node.js](https://nodejs.org/en) (version `>= 18`) and [yarn](https://yarnpkg.com/getting-started/install) installed.
-   - Fork and clone the [documentation repository](https://github.com/Conflux-Chain/conflux-documentation). Detailed instructions for forking and cloning are available on GitHub's help pages.
+1. 设置：
+   - 确保您安装了[node.js](https://nodejs.org/en)（版本 `>= 18`）和 [yarn](https://yarnpkg.com/getting-started/install)。
+   - 分叉并克隆[文档仓库](https://github.com/Conflux-Chain/conflux-documentation)。 关于分叉和克隆的详细指南可在 GitHub 的帮助页面上找到。
 
-2. Making Changes Locally:
-   - Run `yarn && yarn start` in your terminal to preview the site at `http://localhost:3000`.
-   - Navigate to the `docs/**` folder in your cloned repository to make changes. Refresh your local server to see updates.
+2. 在本地进行更改：
+   - 在您的终端运行 `yarn && yarn start` 以在 `http://localhost:3000` 预览站点。
+   - 导航到您克隆仓库中的 `docs/**` 文件夹进行更改。 刷新您的本地服务器以查看更新。
 
-3. Submitting Your Changes:
-   - After making changes, run `yarn build` to ensure everything compiles correctly.
-   - Commit your changes with a meaningful message, then push to your forked repository. Initiate a pull request on GitHub by comparing your branch to the original repository.
+3. 提交您的更改：
+   - 进行更改后，运行 `yarn build` 确保一切正确编译。
+   - 确保您的更改是有价值的，然后将它推送到您的分叉仓库。 在 GitHub 上发起一个拉取请求，将您的分支与原始仓库进行比较。
 
-### Working on an Existing Issue
+### 处理现有问题
 
-To avoid overlapping efforts and streamline contributions, it is suggested to follow these steps:
+为了避免工作重叠并精简贡献流程，我们建议您遵循以下步骤：
 
 1. 检查已接受的问题：
    - 寻找标有类似于 “ACCEPTED” 等的表示准备好作出贡献的问题标签。 如果您对此不确定，您可以在问题评论中询问。
@@ -127,30 +127,30 @@ To avoid overlapping efforts and streamline contributions, it is suggested to fo
 
 ## 提供翻译
 
-:::注意
+:::note
 
 在 Github 仓库中提交的翻译拉取请求将不会被接受。
 
 :::
 
-We are using [Crowdin](https://crowdin.com/project/conflux) for document translation integration. Crowdin helps us to know whether translation strings are outdated after the source files are changed. Anyone can submit translation strings in Crowdin, and translation strings will be pushed to Github repo after they are reviewed.
+我们使用 [Crowdin](https://crowdin.com/project/conflux) 进行文档翻译集成。 Crowdin 能够帮助我们了解在源文件更改后已翻译内容是否需要变更。 任何人都可以在 Crowdin 中提交翻译，已翻译内容在审查后会被推送至文档的 Github 仓库。
 
-### Crowdin Tutorial
+### Crowdin 教程
 
-Visit our project page on Crowdin at either https://crowdin.com/project/conflux or https://zh.crowdin.com/project/conflux and select the language you wish to translate.
+访问我们在 Crowdin 上的项目页面，网址为 https://crowdin.com/project/conflux 或 https://zh.crowdin.com/project/conflux，并选择您想要翻译的语言。
 
-![languages](../image/2023-04-13-15-54-46.png)
+![语言](../image/2023-04-13-15-54-46.png)
 
-You will be able to select a file to begin translating.
+您可以选择一个文件并开始翻译。
 
-![files](../image/2023-04-13-15-57-59.png)
+![文件](../image/2023-04-13-15-57-59.png)
 
-In order to edit, you will need to be logged in. No need to fret though, you can easily log in with your Github account by clicking a few buttons.
+您需要登录才能编辑翻译。 不过不用担心，您只需要点击几个按钮，便可轻松地使用您的 Github 帐户登录。
 
-![login](../image/2023-04-13-16-01-17.png)
+![登录](../image/2023-04-13-16-01-17.png)
 
-Once you are in, you can start the translation process! Simply click on a source string on the left-hand panel and input the translation or edited string. Remember to click SAVE and wait for your translation to be reviewed.
+一旦登录，您就可以开始翻译过程了！ 只需点击左侧面板上的源字符串，然后输入翻译或编辑后的字符串。 记得点击保存，并等待您的翻译被审核。
 
-![translation](../image/2023-04-13-16-06-44.png)
+![翻译](../image/2023-04-13-16-06-44.png)
 
-Once reviewed, the translation string will be pushed to the Github repository and you can visit your translation on the official documentation site.
+一经审核通过，翻译字符串将被推送到 Github 仓库，您可以在官方文档网站上访问您的翻译。

i18n/zh/docusaurus-plugin-content-docs/current/general/CONTRIBUTING/reward-guidelines.md

@@ -1,31 +1,31 @@
 ---
 displayed_sidebar: generalSidebar
-title: 奖励指南
-description: The reward guidelines for your contribution
+title: 奖励准则
+description: 贡献奖励准则
 sidebar_position: 2
 ---
 
 ## 简介
 
-Welcome to the Conflux Contribution Reward Guidelines. Our mission is to build a robust, accessible, and community-driven platform, and your contributions are integral to achieving this vision. Whether you are an experienced developer, a technical writer, a first-time contributor, or simply an enthusiast, your insights, ideas, and improvements can make a significant impact. Understanding that every effort put toward enhancing the Conflux environment deserves recognition, we've implemented a reward system based on FansCoin (FC).
+欢迎来到 Conflux 贡献奖励准则。 我们的使命是建立一个强大、可访问且由社区驱动的平台，而您的贡献对于实现这一愿景至关重要。 无论您是经验丰富的开发者、技术撰稿人、首次贡献者还是简单的爱好者，您的见解、想法和改进都能产生重大影响。 我们深知每一份为增强Conflux环境所做的努力都值得认可，因此我们已经实施了基于FansCoin（FC）的奖励制度。
 
 This article details how your contributions, categorized under 'Issues' and 'Pull Requests', are rewarded. You will learn how identifying problems or presenting enhancements in various aspects—ranging from formatting and readability to error identification—is rewarded. With your support, Conflux continues to evolve and improve by the day.
 
-## Guidelines
+## 准则
 
 ### Issues (16 \~ 80 FC)
 
-- If the individual who raised the issue also offers a solution, the reward will be doubled. Here are some examples:
-  - **Formatting**
-    - Identifying spelling or grammar errors: 16 FC
-    - Spotting broken links or obsolete details: 16 FC
-    - Highlighting issues with code blocks or other format-related problems: 16 FC
-    - Flagging issues with images, diagrams: 16 FC
-  - **Readability Enhancements**
-    - Proposing that existing explanations are unclear: 16 FC
-    - Recommending improved descriptions for certain issues: 16 FC
-    - Suggesting supplementary explanations for specific use-cases of features: 32 FC
-    - Indicating lack of contextual information causing comprehension difficulties: 32 FC
+- 如果在提出问题的同时提供了解决方案，奖励将加倍。 以下是一些示例：
+  - **格式化**
+    - 发现拼写或语法错误：16 FC
+    - 发现损坏的链接或过时的细节：16 FC
+    - 发现代码块等格式问题：16 FC
+    - 标记图片、图表相关问题：16 FC
+  - **增强可读性**
+    - 提出现有解释不清晰：16 FC
+    - 建议完善对某些问题的描述：16 FC
+    - 建议举出用例以使得对特定功能的解释更清晰：32 FC
+    - 指出因缺乏上下文语境而导致的理解困难：32 FC
     - Highlighting deficient tool/document links resulting in limited interactivity: 32 FC
     - Recommending creation or improvement of diagrams, charts, or visual aids: 32 FC
     - Requesting additional details on a specific topic: 48 FC
@@ -46,7 +46,7 @@ This article details how your contributions, categorized under 'Issues' and 'Pul
 - It's desirable to always raise an issue prior to creating a pull request. If the pull request fully resolves an issue, the reward is at least equivalent to that of the issue, regardless of the effort involved.
 - If the originator of the pull request solves an issue they raised, they receive an extra 25% reward.
 - Examples include :
-  - **Formatting**
+  - **格式化**
     - Fixing spelling or grammar errors: 16 FC.
     - Updating broken links or outdated information: 16 FC.
     - Resolving issues with code blocks or other formatting: 32 FC.