Capitalize Context in docs

[Dextheking1]

Addresses the Context item in #6713. (The linked PR #6718 has been stale since 2024-04, so this is a fresh full-coverage pass on today's docs.)

What I did

Swept all docs pages (src/content/, excluding blog/ and community/) for prose occurrences of "context(s)" and capitalized them where they refer to the React Context feature (createContext, useContext, Context Providers, reading/passing Context), following the style guide in the issue: capitalize the React-specific concept, keep lowercase for the general concept.

194 line edits across 24 files. Every change is a pure casing change of the word context(s) in prose — link destinations, URL fragments, {/* */} heading anchors, inline code, and identifiers are untouched (link text was capitalized where it refers to the feature, e.g. [Context](/learn/passing-data-deeply-with-context)).

What I deliberately left alone

• General-concept usage: "in this context", "in the context of", "context menu" (UI term), "async context" (the TC39 AsyncContext-proposal sense in useTransition and the react-dom pre* pages), "loses context of the order"
• Code: `context` params, this.context, use(context) call expressions
• URL fragments, {/* */} anchor comments, JSX path= props, and the error-boundaries lint rule name
• One heading anchor kept lowercase while its heading text was capitalized, e.g. ## Passing data deeply with Context {/*passing-data-deeply-with-context*/}

[github-actions]

Size changes

Details

📦 Next.js Bundle Analysis for react-dev

This analysis was generated by the Next.js Bundle Analysis action. 🤖

This PR introduced no changes to the JavaScript bundle! 🙌