@samitouri / QOS-React-1 / commits / f944b4c535

Fix typos in comments (#35701)

<!-- Thanks for submitting a pull request! We appreciate you spending the time to work on these changes. Please provide enough information so that others can review your pull request. The three fields below are mandatory. Before submitting a pull request, please make sure the following is done: 1. Fork [the repository](https://github.com/facebook/react) and create your branch from `main`. 2. Run `yarn` in the repository root. 3. If you've fixed a bug or added code that should be tested, add tests! 4. Ensure the test suite passes (`yarn test`). Tip: `yarn test --watch TestName` is helpful in development. 5. Run `yarn test --prod` to test in the production environment. It supports the same options as `yarn test`. 6. If you need a debugger, run `yarn test --debug --watch TestName`, open `chrome://inspect`, and press "Inspect". 7. Format your code with [prettier](https://github.com/prettier/prettier) (`yarn prettier`). 8. Make sure your code lints (`yarn lint`). Tip: `yarn linc` to only check changed files. 9. Run the [Flow](https://flowtype.org/) type checks (`yarn flow`). 10. If you haven't already, complete the CLA. Learn more about contributing: https://reactjs.org/docs/how-to-contribute.html --> ## Summary This PR fixes a few small spelling errors in comments across the codebase (`teh`→`the`, `occuring`→`occurring`, `occured`→`occurred`). No behavior changes. <!-- Explain the **motivation** for making this change. What existing problem does the pull request solve? --> ## How did you test this change? <!-- Demonstrate the code is solid. Example: The exact commands you ran and their output, screenshots / videos if the pull request changes the user interface. How exactly did you verify that your PR solves the issue you wanted to solve? If you leave this empty, your PR will very likely be closed. --> This is a comments-only change. I verified the diff is limited to comment text and does not affect logic or runtime behavior.

Pavan Shinde committed Mar 28, 2026 at 03:25 UTC f944b4c5352be02623d2d7415c0806350f875114
3 files changed +3 -3
packages/react-dom-bindings/src/client/ReactFiberConfigDOM.js
+1 -1
@@ -4062,7 +4062,7 @@ export function registerSuspenseInstanceRetry(
4062 instance.data !== SUSPENSE_PENDING_START_DATA ||
4063 // The boundary is still in pending status but the document has finished loading
4064 // before we could register the event handler that would have scheduled the retry
4065 - // on load so we call teh callback now.
4065 + // on load so we call the callback now.
4066 ownerDocument.readyState !== DOCUMENT_READY_STATE_LOADING
4067 ) {
4068 callback();
packages/react-reconciler/src/ReactFiberWorkLoop.js
+1 -1
@@ -3034,7 +3034,7 @@ function renderRootConcurrent(root: FiberRoot, lanes: Lanes): RootExitStatus {
3034 function workLoopConcurrent(nonIdle: boolean) {
3035 // We yield every other "frame" when rendering Transition or Retries. Those are blocking
3036 // revealing new content. The purpose of this yield is not to avoid the overhead of yielding,
3037 - // which is very low, but rather to intentionally block any frequently occuring other main
3037 + // which is very low, but rather to intentionally block any frequently occurring other main
3038 // thread work like animations from starving our work. In other words, the purpose of this
3039 // is to reduce the framerate of animations to 30 frames per second.
3040 // For Idle work we yield every 5ms to keep animations going smooth.
packages/react-reconciler/src/__tests__/ReactAsyncActions-test.js
+1 -1
@@ -1700,7 +1700,7 @@ describe('ReactAsyncActions', () => {
1700 'regression: updates in an action passed to React.startTransition are batched ' +
1701 'even if there were no updates before the first await',
1702 async () => {
1703 - // Regression for a bug that occured in an older, too-clever-by-half
1703 + // Regression for a bug that occurred in an older, too-clever-by-half
1704 // implementation of the isomorphic startTransition API. Now, the
1705 // isomorphic startTransition is literally the composition of every
1706 // reconciler instance's startTransition, so the behavior is less likely