Merge branch 'main' into elysia-http-status

Author: SaltyAom

docs/blog/elysia-05.md

@@ -177,7 +177,7 @@ type ContentType = |
     | 'application/x-www-form-urlencoded'
 ```
 
-You can find more detail at [explicity body](/concept/explicit-body) page in concept.
+You can find more detail at the [explicit body](/concept/explicit-body) page in concept.
 
 ### Numeric Type
 We found that one of the redundant task our developers found using Elysia is to parse numeric string.

docs/concept/explicit-body.md

@@ -15,7 +15,7 @@ head:
       content: By default, Elysia will try to determine body parsing function ahead of time and pick the most suitable function to speed up the process. This allows Elysia to optimize body parser ahead of time, and reduce overhead in compile time but you can explicitly control Elysia to use a certain function.
 ---
 
-# Explicity Body
+# Explicit Body
 
 By default, Elysia will try to determine body parsing function ahead of time and pick the most suitable function to speed up the process.
 

docs/concept/life-cycle.md

@@ -17,7 +17,7 @@ head:
 # Life Cycle
 Elysia supports Life Cycle events, which trigger at specific moments.
 
-A _Middleware__ or _Hook_ acts as an event listener, allowing you to "hook" into these events. This Hook capability enables you to modify data as it moves through the data pipeline.
+A _Middleware_ or _Hook_ acts as an event listener, allowing you to "hook" into these events. This Hook capability enables you to modify data as it moves through the data pipeline.
 
 Whether you aim to implement a custom body parser, generate a tailored response based on your handler, or set up an authentication guard, the Hook empowers you to harness the full potential of Elysia.
 

docs/concept/numeric.md

@@ -17,7 +17,7 @@ head:
 
 # Numeric
 
-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.
+Sometimes 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 re-use the transform function in other handler as well.
 
@@ -35,7 +35,7 @@ app.get('/id/:id', ({ params: { id } }) => id, {
 })
 ```
 
-However, it's a little bit redundant and require a boilerplate, so Elysia has a custom type to speed up the situation with `t.Numeric`
+However, it's a little bit redundant and requires boilerplate, so Elysia has a custom type to speed up the situation with `t.Numeric`
 
 ```ts
 app.get('/id/:id', ({ params: { id } }) => id, {
@@ -45,11 +45,11 @@ app.get('/id/:id', ({ params: { id } }) => id, {
 })
 ```
 
-This allows us to convert **valid** numeric string to number automatically.
+This allows us to convert a **valid** numeric string to a number automatically.
 
-If string is not a valid numeric string, it will throw an error in the runtime and prevent and execution inside the handler.
+If the string is not a valid numeric string, it will throw an error in the runtime and prevent execution inside the handler.
 
-You can use numeric type on any property that support schema typing, including:
+You can use the numeric type on any property that supports schema typing, including:
 - params
 - query
 - headers

docs/concept/plugin.md

@@ -33,12 +33,13 @@ const app = new Elysia()
     .listen(8080)
 ```
 
-Plugin can be registered by using `use` method.
+Plugins can be registered by using `use` method.
 
-Registering a plugin will combine types between plugin and current instance, and the scope of hooks and schema get merged as well.
+Registering a plugin will combine types between the plugin and current instance, and the scope of hooks and schema get merged as well.
 
 ## Separate file
-Using plugin pattern, you can define decouple your logic into a separate file.
+
+Using the plugin pattern, you can define and decouple your logic into a separate file.
 
 ```ts
 // plugin.ts
@@ -64,11 +65,11 @@ import { plugin } from './plugin'
 const app = new Elysia().use(plugin).listen(8080)
 ```
 
-Functional callback will allow user to access main instance values like routes schema, store.
+Functional callback will allow a user to access main instance values like routes, schema, store, etc.
 
 ## Config
 
-You can customize plugin by creating function to return callback which accepts Elysia.
+You can customize a plugin by creating a function to return callback which accepts Elysia.
 
 ```typescript
 import { Elysia } from 'elysia'

docs/concept/route.md

@@ -19,7 +19,7 @@ Like Express, and Fastify.
 
 You define route using method as a building block for your server.
 
-By calling `.[method name](path, callback, hook?)`, you attach route to Elysia, and the library will handle the routing for you.
+By calling `.[method name](path, callback, hook?)`, you attach the route to Elysia, and the library will handle the routing for you.
 
 For example:
 ```typescript
@@ -55,7 +55,7 @@ new Elysia()
 ## Path Parameters
 Path parameters can retrieve data from URL.
 
-For example, getting a user id from path like many social media is when you need a path parameters.
+For example, getting a user id from path (like many social media) is when you may need path parameters.
 
 ```typescript
 new Elysia()

docs/concept/state-decorate.md

@@ -58,7 +58,7 @@ app
 ```
 
 ## TypeScript
-You can type state and decorator explictly using TypeScript with `as`:
+You can type state and decorator explicitly using TypeScript with `as`:
 ```typescript
 app
     // Will type version as `number | null`
@@ -68,7 +68,7 @@ app
     }) => version
 ```
 
-If explictly typed doesn't type `null` or `undefined`, make sure to set `strict` to `true` in `tsconfig.json`:
+If the explicit type doesn't type `null` or `undefined`, make sure to set `strict` to `true` in `tsconfig.json`:
 ```json
 // tsconfig.json
 {

docs/patterns/after-handle.md

@@ -17,7 +17,7 @@ head:
 # After Handle
 **After Handle** can transform a response into a new response.
 
-**After Handle** is like `transform`, but instead of transforming incoming request, it is use to transform a response returned from main handler.
+**After Handle** is like `transform`, but instead of transforming the incoming request, it is used to transform a response returned from main handler.
 
 Allowing you to remap the returned value into a new value or force the value to early return.
 
@@ -42,7 +42,7 @@ new Elysia()
 The above code will return `3` as a result.
 
 ## Early return
-Sometime, you may want to prevent the on-going chain of **afterHandle**, just like **beforeHandle**, if you return the value in a **afterHandle** function, it will be an early return and skip the rest of **afterHandle**
+Sometimes you may want to prevent the on-going chain of **afterHandle**, just like **beforeHandle**. If you return the value in a **afterHandle** function, it will be an early return and skip the rest of **afterHandle**
 
 ```typescript
 import { Elysia } from 'elysia'

docs/patterns/body-parser.md

@@ -15,7 +15,7 @@ head:
 ---
 
 # Body Parser
-Like Express, body-parser is a function to parse body of an incoming request.
+Like Express, body-parser is a function to parse the body of an incoming request.
 
 By default, Elysia will parse the body with content-type of:
 - `text/plain`

docs/patterns/error-handling.md

@@ -54,7 +54,7 @@ new Elysia()
 ```
 
 ## Local Error
-You can assign error handling method to a scope using [hook](/concept/life-cycle.html#local-hook) or [guard](/concept/guard.html)
+You can assign an error handling method to a scope using [hook](/concept/life-cycle.html#local-hook) or [guard](/concept/guard.html)
 ```typescript
 app.get('/', () => 'Hello', {
     beforeHandle({ set, request: { headers } }) {
@@ -71,7 +71,7 @@ app.get('/', () => 'Hello', {
 ```
 
 ## Custom Error Message
-You can provide custom error message by providing `error`:
+You can provide a custom error message by providing `error`:
 ```ts
 new Elysia()
 	.post('/', ({ body }) => body, {
@@ -99,9 +99,9 @@ If no error response is returned, the error will be returned using `error.name`.
 :::
 
 ## Custom Error
-Elysia supports custom error both in type-level and implementaiton level.
+Elysia supports custom error both in the type-level and implementation level.
 
-Helping you to easly classify and narrow down the error type for fully type safety with an auto-complete:
+Helping you to easily classify and narrow down the error type for full type safety with auto-complete:
 ```ts
 class CustomError extends Error {
     constructor(public message: string) {