Capitalize Components in docs - #8666
Open
Dextheking1 wants to merge 4 commits into
Open
Dextheking1 wants to merge 4 commits into
Dextheking1 wants to merge 4 commits into
Conversation
Size changesDetails📦 Next.js Bundle Analysis for react-devThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Part of #6713 (Components item).
Capitalizes the React concept Component(s) where prose refers to the concept directly, applying @rickhanlonii's guidance from #6717 strictly (capitalize only where it "makes sense to link to the Component reference page"). Deliberately minimal: reviewed all ~3,600 occurrences and found the docs are already substantially capitalized for the clear concept uses, so this is 5 casing-only edits across 4 files:
learn/index.md: "React Components are JavaScript functions that return markup" (definitional)learn/your-first-component.md: two "React Components are regular JavaScript functions" statements (matches the issue's "Functional Components are a core concept in React" example; consistent with the same file's already-capitalized line 175)reference/react/Component.mdandreference/react/PureComponent.md: "Class Components are still supported by React" (categorical statement about the concept's support status; matches the existing "Class Components:" labels inlegacy.md)Deliberately left lowercase after full review: descriptive/instance uses ("your/this/child/named components"), indefinite-article definitions ("A React component is..."), behavioral statements ("upgrade your apps one component at a time"), built-in browser components ("the component"), counts/idioms, "function/class components" in instructional phrasing (current docs convention), compound "subcomponent(s)", and everything in
blog/,community/, and the homepage.URLs, anchors, inline code, and identifiers untouched.