chore: fix some words

[enkilee]

chore: fix some words

[gemini-code-assist]

Summary of Changes

Hello @enkilee, 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 is a comprehensive cleanup effort focused on enhancing the overall quality of the codebase by rectifying a wide array of spelling mistakes and grammatical errors. The changes span across documentation, code comments, and variable names, ensuring that the project's textual content is accurate, professional, and easy to understand. This improves maintainability and reduces potential confusion for developers and users alike.

Highlights

• Documentation Clarity: Corrected various spelling and grammatical errors in documentation files, including docs/src/develop/example_psi.rst and docs/src/research/index.rst, to improve readability and accuracy.
• Code Comments Refinement: Addressed numerous typos and inconsistencies in code comments across multiple modules (e.g., examples/psi/cpp/ecdh_psi.h, yacl/crypto/aead/aead.cc, yacl/crypto/experimental/dpf/pprf.h), enhancing the clarity and precision of code explanations.
• Consistent Terminology: Standardized terminology by renaming CheckParms to CheckParams and DHTripple to DHTriple in the ZKP examples, ensuring consistent naming conventions throughout the codebase.
• Benchmark Variable Naming: Fixed a typo in a global variable name from g_interations to g_iterations in yacl/base/block_bench.cc for better accuracy.
• DRBG Module Corrections: Improved the accuracy of comments and variable names within the DRBG (Deterministic Random Bit Generator) module, correcting words like 'GetEntrpoy' to 'GetEntropy' and 'avaliability' to 'availability'.

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 a number of typos and wording issues throughout the codebase, which improves overall code and documentation quality. The changes are mostly correct and beneficial. I've found one additional minor grammatical error that could also be fixed. Please see the detailed comment.