Docs/i18n updates
Author: lilin-1
Pull request: yes

**PR Summary**

- This PR updates the Chinese documentation (Traditional and Simplified) to unify terminology, phrasing, and examples across both versions for improved consistency and clarity.

**What Does This PR Do?**

- In the Traditional Chinese glossary, revises the entry for "Trainer" from `"Trainer: Trainer（不翻譯）"` to `"Trainer: 訓練器。當作為類名出現時不翻譯."`
  - **Reason**: Unifies the translation policy across both documents and clarifies when to translate the term versus when to keep the original class name, preventing ambiguity.
- In the Traditional Chinese text, changes `"一般的 PyTorch 或 TensorFlow 訓練迴圈"` (general PyTorch or TensorFlow training loop) to `"經典的 PyTorch 或 TensorFlow 訓練迴圈"` (classic PyTorch or TensorFlow training loop).
  - **Reason**: Unifies the descriptive adjective used in both documents and improves phrasing for better readability and technical accuracy.
- In the Simplified Chinese examples, updates the confidence score display to `"99.97%"`.
  - **Reason**: Unifies the format of example outputs across both versions and uses precise percentage formatting to better reflect real model outputs, improving user understanding.
- In the Simplified Chinese installation instructions, standardizes `"安装页"` to `"安装页面"` and revises the sentence structure to `"关于如何在你使用的平台上安装这些框架，请参阅……"` (Regarding how to install these frameworks on your platform, please refer to...).
  - **Reason**: Unifies terminology (`"安装页面"`) and phrasing for consistency between the Simplified and Traditional Chinese documents. Adding the word `"如何"` (how) creates a more natural and grammatically complete sentence, improving flow and clarity for the reader.
- In the Simplified Chinese text, standardizes the term for `"Named Entity Recognition (NER)"` to `"专有名词辨识"`.
  - **Reason**: This change unifies the terminology used across both the Simplified and Traditional Chinese documents. The term `"专有名词辨识"` is chosen as it is more intuitive and easier for a general audience to understand.

**Fixes # (issue)**

- N/A

**Scope**

- Affected files:
  - `i18n/README_zh-hant.md`
  - `i18n/README_zh-hans.md`

**Motivation and Context**

- Ensures consistent terminology across Chinese docs, improves accuracy in example outputs, and standardizes phrasing for better comprehension. These changes reduce ambiguity for readers switching between code and documentation and align with common practices in the community.

**Dependencies**

- None.

**Before Submitting**

- [x] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
- [x] Did you read the [`https://github.com/huggingface/transformers/blob/main/CONTRIBUTING.md#create-a-pull-request`](https://github.com/huggingface/transformers/blob/main/CONTRIBUTING.md#create-a-pull-request) , Pull Request section?
- [ ] Was this discussed/approved via a Github issue or the [`https://discuss.huggingface.co/`](https://discuss.huggingface.co/) ? Please add a link to it if that's the case.
  - Note: Not discussed via issue/forum; minor documentation improvements.
- [x] Did you make sure to update the documentation with your changes? Here are the [`https://github.com/huggingface/transformers/tree/main/docs`](https://github.com/huggingface/transformers/tree/main/docs) , and [`https://github.com/huggingface/transformers/tree/main/docs#writing-source-documentation`](https://github.com/huggingface/transformers/tree/main/docs#writing-source-documentation).
- [ ] Did you write any new necessary tests?
  - Note: Documentation-only changes; tests not applicable.

**Who Can Review?**

- Documentation: @stevhliu

Comments:
The docs for this PR live [here](https://moon-ci-docs.huggingface.co/docs/transformers/pr_42006). All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

Hi @stevhliu,

Thanks for asking! Yes, I'm happy to give it a try and update the Chinese READMEs to align with the main branch.

I'll look into it and do my best.