Fix typos in README

[zuyu]

What type of PR is this?

• API-change
• BUG
• Improvement
• Documentation
• Feature
• Test and CI
• Code Refactoring

What this PR does / why we need it:

Fix the typo introduced in #15645

CC: @yangj1211

[CLAassistant]

All committers have signed the CLA.

[matrix-meow]

@zuyu Thanks for your contributions!

Pull Request Review:

Problems Identified:

1. Typos in README:
   • The pull request aims to fix typos in the README file.
   • The changes made are correcting minor spelling errors in the README content.
   • The typos fixed are related to text formatting and do not impact the functionality of the codebase.

Suggestions for Improvement:

1. Comprehensive Review:

   • While fixing typos is important for maintaining a professional appearance, it is recommended to conduct a thorough review of the entire README file for any other potential errors or outdated information.

2. Consistency in Formatting:

   • Ensure consistent formatting throughout the README file to maintain a cohesive and professional appearance.

3. Automated Spell Check:

   • Consider integrating automated spell-check tools or plugins in the development workflow to catch typos and spelling errors early on.

4. Peer Review:

   • Encourage peer reviews for documentation changes to ensure accuracy and clarity in the content.

Optimization Suggestions:

1. Batch Changes:

   • If there are multiple documentation-related fixes to be made, consider bundling them into a single pull request to minimize the number of PRs for minor changes.

2. Documentation Standards:

   • Establish clear documentation standards within the project to maintain consistency and quality across all documentation files.

3. Documentation Testing:

   • Implement a documentation testing process to verify the correctness of documentation changes automatically.

4. Version Control:

   • Ensure that the README file is updated in sync with code changes to reflect the most current information about the project.

Security Concerns:

There are no security concerns related to the changes made in this pull request as they are limited to fixing typos in the README file and do not involve any sensitive information or code modifications.

By addressing the suggestions provided and considering the optimization strategies, the quality and consistency of the project's documentation can be improved. Additionally, incorporating automated checks and peer reviews can help maintain high-quality documentation in the long term.