fix: correct spelling mistakes in code and error messages #34118
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fix a consistent spelling error in SuspenseList component error messages. The word 'explicitly' was misspelled as 'explictly' in error messages that warn developers about future-compatibility requirements for SuspenseList props.
Problem: User-facing error messages contained the typo "explictly" instead of "explicitly", which affects the professionalism and clarity of React's developer experience.
Solution:
ReactFiberBeginWork.js
error messages (2 locations)ReactSuspenseList-test.js
(2 locations)This ensures consistency between runtime error messages and their test expectations.
How did you test this change?
Verification steps taken:
Code Review: Manually verified all 4 instances of the typo were corrected
ReactFiberBeginWork.js
ReactSuspenseList-test.js
File Validation: Confirmed only the intended files were modified: