Update Benchmark doc and FAQ

[pan-x-c]

Description

As the title says

Checklist

Please check the following items before code is ready to be reviewed.

• Code has passed all tests
• Docstrings have been added/updated in Google Style
• Documentation has been updated
• Code is ready for review

[gemini-code-assist]

Summary of Changes

Hello @pan-x-c, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request primarily focuses on improving the project's documentation by expanding the benchmark section with new examples and detailed reports, and by enhancing the Frequently Asked Questions (FAQ) guides. The updates aim to provide clearer instructions on configuration, debugging, and a better understanding of the system's architecture and its relation to underlying frameworks, thereby making the project more accessible and user-friendly.

Highlights

• Benchmark Documentation Expansion: Added new benchmark examples (Guru-Math, FrozenLake, Alfworld) and their detailed reports to benchmark/README.md, and updated the main README.md and docs/sphinx_doc/source/main.md (both English and Chinese versions) to include links to these new benchmarks under a dedicated "Benchmarks" section.
• FAQ Section Enhancement: Significantly revised the FAQ documents (docs/sphinx_doc/source/tutorial/faq.md and its Chinese counterpart) to offer more comprehensive guidance on configuration, detailed logging for debugging, and a new section explaining the architectural differences between Trinity-RFT and veRL.
• RL Framework Acknowledgment: Included rLLM in the list of inspiring RL frameworks within README.md and README_zh.md.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates the benchmark documentation and the FAQ across both English and Chinese versions. A new 'Benchmarks' section has been added to the READMEs and main documentation pages, including links to new benchmark reports. The FAQ has been significantly restructured and expanded for better clarity. My review includes suggestions to fix a few typos, formatting inconsistencies, and, most importantly, some potentially broken links in the Sphinx documentation that should be addressed to ensure the documentation renders correctly.

[yanxi-chen]

Please see the inline comments, otherwise lgtm

[hiyuchang]

Others LGTM