[Doc] translate documentation, overview#1539
Conversation
|
Thanks for your contribution! I will check it and help to improve it! |
Co-authored-by: Yanhong Zeng <zengyh1900@gmail.com>
Co-authored-by: Yanhong Zeng <zengyh1900@gmail.com>
Co-authored-by: Yanhong Zeng <zengyh1900@gmail.com>
Co-authored-by: Yanhong Zeng <zengyh1900@gmail.com>
Co-authored-by: Yanhong Zeng <zengyh1900@gmail.com>
Co-authored-by: Yanhong Zeng <zengyh1900@gmail.com>
Co-authored-by: Yanhong Zeng <zengyh1900@gmail.com>
Co-authored-by: Yanhong Zeng <zengyh1900@gmail.com>
Co-authored-by: Yanhong Zeng <zengyh1900@gmail.com>
Co-authored-by: Yanhong Zeng <zengyh1900@gmail.com>
Co-authored-by: Yanhong Zeng <zengyh1900@gmail.com>
Co-authored-by: Yanhong Zeng <zengyh1900@gmail.com>
Co-authored-by: Yanhong Zeng <zengyh1900@gmail.com>
Co-authored-by: Yanhong Zeng <zengyh1900@gmail.com>
|
@whu-lee please fix the lint check. |
|
Dear whu-lee, |
Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
translate documentation, overview
Modification
translate documentation, overview
Who can help? @ them here!
BC-breaking (Optional)
Does the modification introduce changes that break the backward-compatibility of the downstream repositories?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here, and update the documentation.
Checklist
Before PR:
After PR: