docs(readme): fix broken anchor links in recommended reading section

[longway-code]

• Fix broken internal anchor links in the "Recommended reading" tips of both README.md and README_zh.md
• The link #one-line-install-recommended (EN) and #一键安装推荐 (ZH) no longer matched the actual section heading ### One-line install (beta, continuously improving), causing the link cannot jump to the intended section
• Updated both anchors to match the current heading

[gemini-code-assist]

Summary of Changes

Hello, 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 resolves an issue where internal anchor links within the project's README.md and README_zh.md files were broken. The changes ensure that users can now correctly navigate to the "One-line install" section from the recommended reading tips, enhancing the usability and accuracy of the documentation for both English and Chinese readers.

Highlights

• Broken Anchor Links Fixed: Fixed internal anchor links in the "Recommended reading" sections of both README.md and README_zh.md. The previous anchors no longer matched the actual section headings, causing navigation issues.
• Improved Documentation Navigation: Updated the English anchor from #one-line-install-recommended to #one-line-install-beta-continuously-improving and the Chinese anchor from #一键安装推荐 to #一键安装beta持续完善中 to ensure correct linking to the "One-line install" section.

Changelog

• README.md
  • Updated the internal anchor link for the "One-line install" section to match the current heading.
• README_zh.md
  • Updated the internal anchor link for the "一键安装" (One-line install) section to match the current heading.

Activity

• No specific activity (comments, reviews, or progress updates) has been recorded for this pull request yet.

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 addresses broken internal anchor links in README.md and README_zh.md by updating them to match the revised section headings. The changes correctly fix the broken links. For future improvement, consider aligning the section headings in website/public/docs/quickstart.en.md and website/public/docs/quickstart.zh.md. Currently, they refer to the 'One-line install' as '(recommended)', while the READMEs use '(beta, continuously improving)'. Aligning these would improve documentation consistency.

[xieyxclack]

Thanks a lot for your contribution :)