chore: update winterCG to winterTC

Author: autoboxer

docs/blog.md

@@ -79,7 +79,7 @@ head:
         title: 'Introducing Elysia 0.6 - This Game',
         href: '/blog/elysia-06',
         cover: 'this-game.webp',
-        detail: 'Introducing re-imagined plugin model, dynamic mode, better developer experience with declarative custom error, customizable loose and strict path mapping, TypeBox 0.30 and WinterCG framework interlop. Pushing the boundary of what is possible once again'
+        detail: 'Introducing re-imagined plugin model, dynamic mode, better developer experience with declarative custom error, customizable loose and strict path mapping, TypeBox 0.30 and WinterTC framework interlop. Pushing the boundary of what is possible once again'
       },
       {
         title: 'Accelerate your next Prisma server with Elysia',

docs/integrations/astro.md

@@ -7,7 +7,7 @@ head:
 
     - - meta
       - name: 'description'
-        content: You can run Elysia on Astro. Elysia will work normally as expected because of WinterCG compliance.
+        content: You can run Elysia on Astro. Elysia will work normally as expected because of WinterTC compliance.
 
     - - meta
       - property: 'og:description'
@@ -52,12 +52,12 @@ export const GET = handle // [!code ++]
 export const POST = handle // [!code ++]
 ```
 
-Elysia will work normally as expected because of WinterCG compliance.
+Elysia will work normally as expected because of WinterTC compliance.
 
 We recommend running [Astro on Bun](https://docs.astro.build/en/recipes/bun) as Elysia is designed to be run on Bun.
 
 ::: tip
-You can run Elysia server without running Astro on Bun thanks to WinterCG support.
+You can run Elysia server without running Astro on Bun thanks to WinterTC support.
 :::
 
 With this approach, you can have co-location of both frontend and backend in a single repository and have End-to-end type-safety with Eden.

docs/integrations/expo.md

@@ -7,7 +7,7 @@ head:
 
     - - meta
       - name: 'description'
-        content: With Expo App Router, you can run Elysia on Expo route. Elysia will work normally as expected thanks to WinterCG compliance.
+        content: With Expo App Router, you can run Elysia on Expo route. Elysia will work normally as expected thanks to WinterTC compliance.
 
     - - meta
       - property: 'og:description'

docs/integrations/nextjs.md

@@ -7,7 +7,7 @@ head:
 
     - - meta
       - name: 'description'
-        content: With Next.js App Router, you can run Elysia on Next.js routes. Elysia will work normally as expected because of WinterCG compliance.
+        content: With Next.js App Router, you can run Elysia on Next.js routes. Elysia will work normally as expected because of WinterTC compliance.
 
     - - meta
       - property: 'og:description'
@@ -41,7 +41,7 @@ export const POST = app.fetch // [!code ++]
 
 :::
 
-Elysia will work normally as expected because of WinterCG compliance.
+Elysia will work normally as expected because of WinterTC compliance.
 
 You can treat the Elysia server as a normal Next.js API route.
 

docs/patterns/mount.md

@@ -7,7 +7,7 @@ head:
 
   - - meta
     - name: 'description'
-      content: Applying WinterCG interoperable code to run with Elysia or vice-versa.
+      content: Applying WinterTC interoperable code to run with Elysia or vice-versa.
 
   - - meta
     - property: 'og:description'
@@ -21,7 +21,7 @@ It allows web servers to run interoperably across runtimes by using [Request](ht
 
 Elysia is WinterTC compliant. Optimized to run on Bun, but also support other runtimes if possible.
 
-This allows any framework or code that is WinterCG compliant to be run together, allowing frameworks like Elysia, Hono, Remix, Itty Router to run together in a simple function.
+This allows any framework or code that is WinterTC compliant to be run together, allowing frameworks like Elysia, Hono, Remix, Itty Router to run together in a simple function.
 
 ## Mount
 To use **.mount**, [simply pass a `fetch` function](https://twitter.com/saltyAom/status/1684786233594290176):

docs/patterns/unit-test.md

@@ -16,7 +16,7 @@ head:
 
 # Unit Test
 
-Being WinterCG compliant, we can use Request / Response classes to test an Elysia server.
+Being WinterTC compliant, we can use Request / Response classes to test an Elysia server.
 
 Elysia provides the **Elysia.handle** method, which accepts a Web Standard [Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) and returns [Response](https://developer.mozilla.org/en-US/docs/Web/API/Response), simulating an HTTP Request.
 

docs/quick-start.md

@@ -348,7 +348,7 @@ Don't forget to update `tsconfig.json` to include `compilerOptions.strict` to `t
 
 <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.
 
 First, install Elysia with the command below: