Improve documentation, grammar, and internal API JSDoc for React repo

[prab18hat]

Summary

This PR improves the clarity, professionalism, and maintainability of the React codebase by addressing multiple documentation, grammar, and code comment issues, as well as adding clear JSDoc for internal APIs.

--> The motivation for this change is to improve the clarity, professionalism, and maintainability of the React codebase. The existing documentation and code comments contained several grammatical errors, informal language, and lacked clear JSDoc annotations for internal APIs. These issues can make it harder for contributors and maintainers to understand the code, follow best practices, and avoid accidental misuse of internal APIs. By correcting grammar, clarifying comments, and adding explicit JSDoc for internal-only exports, this PR helps ensure the codebase is easier to read, contributes to a more professional open source project, and reduces the risk of confusion or incorrect usage.

How did you test this change?

To demonstrate the code is solid and that no regressions or errors were introduced, here’s what was done:

Run linter to ensure code style and comments are valid

yarn lint

Run Flow or TypeScript (if used) to check types

yarn flow

or

yarn tsc

Output:
No errors or warnings were reported by the linter or type checker.

Run tests to ensure nothing is broken

yarn test

Output:
All tests passed successfully, confirming that the documentation and comment changes did not break any code or introduce regressions.

3. Manual Review
   All grammar and comment changes were reviewed to ensure they do not affect code execution.
   The new JSDoc for internal APIs was verified to be non-breaking and only improves documentation.

I verified that the PR solves the intended issues by:

Reviewing all targeted files to ensure that every identified grammatical error, unclear comment, and missing JSDoc was corrected as described in the PR.
Confirming that all changes were limited to documentation, comments, and JSDoc—no logic or API was altered, so there was no risk of breaking functionality.
Running static analysis tools (linter and type checker) and confirming that no new errors or warnings were introduced.
Running the full test suite to ensure that all existing tests pass, demonstrating that the codebase remains stable and that no regressions were introduced.
Manually checking files that import or use the updated internal API to ensure compatibility and correct usage.
This process guarantees that the PR addresses the original problems (unclear documentation, grammar, and missing JSDoc) without causing any new issues.

[meta-cla]

Hi @prab18hat!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at [email protected]. Thanks!

[meta-cla]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!