update winterCG to winterTC #694
Conversation
WalkthroughThis pull request updates documentation references from "WinterCG" to "WinterTC" across seven markdown files in the docs directory, including blog entries, integration guides, pattern documentation, and quick-start materials. No functional code changes or logic modifications are included. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes
Poem
Pre-merge checks and finishing touches❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (7)
docs/blog.md(1 hunks)docs/integrations/astro.md(2 hunks)docs/integrations/expo.md(1 hunks)docs/integrations/nextjs.md(2 hunks)docs/patterns/mount.md(2 hunks)docs/patterns/unit-test.md(1 hunks)docs/quick-start.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
docs/quick-start.md
[grammar] ~351-~351: Use a hyphen to join words.
Context: ...slot:web-standard> Elysia is a WinterTC compliant library, which means if a fram...
(QB_NEW_EN_HYPHEN)
🔇 Additional comments (7)
docs/integrations/expo.md (1)
10-14: Intentional inconsistency: meta description vs og:description blocks.The meta
description(line 10) has been updated to "WinterTC", while theog:description(line 14) remains "WinterCG". This aligns with the PR objectives noting that og:description blocks were not updated. No action needed if this is intentional.docs/patterns/mount.md (1)
10-10: Terminology update complete and consistent.All references to WinterCG in descriptive text and meta descriptions have been correctly updated to WinterTC. The og:description block (line 14) was intentionally preserved.
Also applies to: 18-18, 24-24
docs/blog.md (1)
82-82: Terminology update applied to blog entry metadata.The blog listing for Elysia 0.6 has been correctly updated from "WinterCG framework interlop" to "WinterTC framework interlop".
docs/integrations/nextjs.md (1)
10-10: Terminology updates applied consistently.Meta description (line 10) and prose text (line 44) have been correctly updated to reference WinterTC compliance. The og:description block (line 14) remains unchanged per PR scope.
Also applies to: 44-44
docs/patterns/unit-test.md (1)
19-19: Terminology update applied to guidance text.Line 19 correctly reflects the WinterTC standard compliance terminology.
docs/integrations/astro.md (2)
55-55: Apply hyphenation to compound adjective for consistency.Line 55 reads "Elysia will work normally as expected because of WinterTC compliance." The phrase "WinterTC compliance" is a noun phrase (correct as-is), but if this should align with the adjective form used in other files, consider "WinterTC-compliant" when used as a predicate adjective.
However, "because of WinterTC compliance" is idiomatic and grammatically correct. No change needed here.
10-10: Terminology updates applied consistently.Meta description (line 10) and prose references (line 60) have been correctly updated to WinterTC. The og:description block (line 14) remains unchanged per PR scope.
Also applies to: 60-60
| <template v-slot:web-standard> | ||
|
|
||
| Elysia is a WinterCG compliance library, which means if a framework or runtime supports Web Standard Request/Response, it can run Elysia. | ||
| Elysia is a WinterTC compliant library, which means if a framework or runtime supports Web Standard Request/Response, it can run Elysia. |
There was a problem hiding this comment.
Apply hyphenation to compound adjective.
Line 351 reads "WinterTC compliant library". When a compound adjective precedes a noun, it should be hyphenated: "WinterTC-compliant library".
Apply this diff to fix the grammar:
-Elysia is a WinterTC compliant library, which means if a framework or runtime supports Web Standard Request/Response, it can run Elysia.
+Elysia is a WinterTC-compliant library, which means if a framework or runtime supports Web Standard Request/Response, it can run Elysia.Note: This same pattern ("WinterTC compliant" used as adjective before noun) appears in other files and should also be hyphenated for consistency. Check docs/integrations/astro.md line 55 and docs/integrations/nextjs.md line 44.
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| Elysia is a WinterTC compliant library, which means if a framework or runtime supports Web Standard Request/Response, it can run Elysia. | |
| Elysia is a WinterTC-compliant library, which means if a framework or runtime supports Web Standard Request/Response, it can run Elysia. |
🧰 Tools
🪛 LanguageTool
[grammar] ~351-~351: Use a hyphen to join words.
Context: ...slot:web-standard> Elysia is a WinterTC compliant library, which means if a fram...
(QB_NEW_EN_HYPHEN)
🤖 Prompt for AI Agents
In docs/quick-start.md around line 351, change the phrase "WinterTC compliant
library" to "WinterTC-compliant library" (hyphenate the compound adjective
before the noun); also update the same pattern for consistency in
docs/integrations/astro.md around line 55 and docs/integrations/nextjs.md around
line 44 by replacing "WinterTC compliant" with "WinterTC-compliant".
1 participant
Context
WinterCG was officially renamed to WinterTC in early 2025 - article
There was a mix of references throughout the docs, some to the correct WinterTC, and others to the old WinterCG. This PR fixes that.
There were two places that were not updated:
blogs/*- it didn't feel appropriate to rewrite history here, but this may be a candidate for updates as wellog:descriptionmeta blocksSummary by CodeRabbit
Documentation