Merge branch 'main' into main

Author: bogeychan

components/midori/editor.vue

@@ -176,7 +176,7 @@ onMounted(() => {
         <p
             class="text-xl md:text-2xl leading-relaxed text-gray-400 text-left md:text-center w-full max-w-2xl"
         >
-            Being WinterCG compliance, Elysia can run in your browser!
+            Being WinterCG compliant, Elysia can run in your browser!
             <br />
             Edit the code and see live update immediately.
         </p>

components/midori/openapi.vue

@@ -3,7 +3,7 @@ import Prism from 'vue-prism-component'
 
 const code = `import { Elysia, t } from 'elysia'
 import { swagger } from '@elysiajs/swagger'
-import { user, feed } from './controllers'
+import { users, feed } from './controllers'
 
 new Elysia()
     .use(swagger())

docs/blog/elysia-06.md

@@ -122,7 +122,7 @@ By this, Elysia is partially follows WinterCG compliance as we are optimized to
 
 This allows any framework and code that is WinterCG compliance to be run together in theory, an implementation is proved by [Hono](https://honojs.dev) which introduce the **.mount** method to [runs multiple framework together in one codebase](https://twitter.com/honojs/status/1684839623355490304), including Remix, Elysia, Itty Router, and Hono itself in a simple function.
 
-By this, we implemented the same logic for Elysia by introducing `.mount` method to runs any framework or code that WinterCG compliance.
+By this, we implemented the same logic for Elysia by introducing `.mount` method to runs any framework or code that is WinterCG compliant.
 
 To use `.mount`, [simply pass a `fetch` function](https://twitter.com/saltyAom/status/1684786233594290176):
 ```ts
@@ -146,7 +146,7 @@ By default, this declaration are used by:
 - Netlify Edge Function
 - Remix Function Handler
 
-Which means you can run all of the above code to interlop with Elysia all in a single server, or reused and existing function all in one deployment, no need to setting up Reverse Proxy for handling multiple server.
+Which means you can run all of the above code to interlop with Elysia all in a single server, or re-used and existing function all in one deployment, no need to setting up Reverse Proxy for handling multiple server.
 
 If the framework also support a **.mount** function, you can deeply nested a framework that support it infinitely.
 ```ts
@@ -163,7 +163,7 @@ const main = new Elysia()
     .listen(3000)
 ```
 
-You can even reused multiple existing Elysia project in your server.
+You can even re-used multiple existing Elysia project in your server.
 
 ```ts
 import A from 'project-a/elysia'

docs/blog/elysia-supabase.md

@@ -326,7 +326,7 @@ const authen = (app: Elysia) =>
 Great! We have just used name reference on our route!
 
 ::: tip
-If you found yourself with a long schema, you can declare them in a separate file and reuse them in any Elysia route to put the focus back on business logic instead.
+If you found yourself with a long schema, you can declare them in a separate file and re-use them in any Elysia route to put the focus back on business logic instead.
 :::
 
 ## Storing user session
@@ -478,7 +478,7 @@ And that's it!
 
 We have just implemented user authentication which is fun and game, but now you might find yourself in need of authorization for each route, and duplicating the same code to check for cookies all over the place.
 
-Luckily, we can reuse the function in Elysia.
+Luckily, we can re-use the function in Elysia.
 
 Let's paint the example by saying that we might want a user to create a simple blog post that can have the database schema as the following:
 

docs/blog/with-prisma.md

@@ -283,7 +283,7 @@ This will return a JSON equivalent of our custom error message when a unique con
 Allowing us to seemlessly define any custom error from Prisma error.
 
 ## Bonus: Reference Schema
-When our server grow complex and type becoming more redundant and become a boilerplate, inlining an Elysia type can be improved by using **Reference Schmea**.
+When our server grow complex and type becoming more redundant and become a boilerplate, inlining an Elysia type can be improved by using **Reference Schema**.
 
 To put it simply, we can named our schema and reference the type by using the name.
 

docs/concept/config.md

@@ -52,7 +52,7 @@ new Elysia()
 ```
 
 ::: tip
-For providing WebSocket, please use [`@elysiajs/websocket`](https://github.com/elysiajs/elysia-websocket)
+For providing WebSocket, please use [`WebSocket`](/patterns/websocket)
 :::
 
 ## Custom Port

docs/concept/derive.md

@@ -17,7 +17,7 @@ head:
 # Derive
 Just like _state_ and _decorate_, derive allows you to customize `Context` based on existing `Context` as `Context.store`.
 
-This is useful when you to need to create a value based on an existing value reactively.
+This is useful when you need to create a value based on an existing value reactively.
 
 ### Example
 ```typescript

docs/concept/explicit-body.md

@@ -31,9 +31,9 @@ app.post('/', ({ body }) => body, {
 })
 ```
 
-Elysia read the body schema and found that, the type is entirely an object, so it's likely that the body will be JSON, Elysia then pick the JSON body parser function ahead of time and try to parse the body.
+Elysia read the body schema and found that, the type is entirely an object, so it's likely that the body will be JSON. Elysia then picks the JSON body parser function ahead of time and tries to parse the body.
 
-Here's a criteria that Elysia use to pick up type of body parser
+Here's a criteria that Elysia uses to pick up type of body parser
 
 - `application/json`: body typed as `t.Object`
 - `multipart/form-data`: body typed as `t.Object`, and is 1 level deep with `t.File`
@@ -43,7 +43,7 @@ Here's a criteria that Elysia use to pick up type of body parser
 This allows Elysia to optimize body parser ahead of time, and reduce overhead in compile time.
 
 ## Explicit Content Type
-However, is some scenario that Elysia fail to pick the correct body parser function, you can explicitly tell Elysia to use a certain function by specifying `type`
+However, in some scenario if Elysia fails to pick the correct body parser function, you can explicitly tell Elysia to use a certain function by specifying `type`
 
 ```ts
 app.post('/', ({ body }) => body, {
@@ -52,7 +52,7 @@ app.post('/', ({ body }) => body, {
 })
 ```
 
-This allows you to control Elysia behavior for picking body parser function to fits your need in complex scenario.
+This allows you to control Elysia behavior for picking body parser function to fit your needs in a complex scenario.
 
 `type` may be one of the following:
 ```ts
@@ -71,4 +71,4 @@ type ContentType = |
     | 'application/x-www-form-urlencoded'
 ```
 
-You can extends Elysia by adding a custom body parser function yourself with `onParse`, see [body parser](/patterns/body-parser).
+You can extend Elysia by adding a custom body parser function yourself with `onParse`, see [body parser](/patterns/body-parser).

docs/concept/guard.md

@@ -21,7 +21,7 @@ Suppose you have many shared local hooks.
 Instead of duplicating an existing hook, you can define a shared hook scope using `guard`.
 
 ---
-**Guard** lets you inject multiple life-cycle events into multiple routes at once. Guard is useful when you have listen to same life-cycle events in the multiple routes, for example: logging, schema validation, or error handling.
+**Guard** lets you inject multiple life-cycle events into multiple routes at once. Guard is useful when you have to listen to the same life-cycle event in multiple routes, for example: logging, schema validation, or error handling.
 
 To encapsulate all hooks into the scope, instead of writing:
 ```typescript

docs/concept/numeric.md

@@ -19,7 +19,7 @@ head:
 
 Sometime you might find yourself in need of numeric string like extracting path parameter, but it's typed as string and need to be convert to number.
 
-Using Elysia's `transform` life-cycle, you can manually parse number to string and reuse the transform function in other handler as well.
+Using Elysia's `transform` life-cycle, you can manually parse number to string and re-use the transform function in other handler as well.
 
 ```ts
 app.get('/id/:id', ({ params: { id } }) => id, {