diff --git a/docs/at-glance.md b/docs/at-glance.md
index 6d86a149..0f314f8e 100644
--- a/docs/at-glance.md
+++ b/docs/at-glance.md
@@ -7,11 +7,11 @@ head:
 
     - - meta
       - name: 'description'
-        content: Designed with ergonomic design, extensive support for TypeScript, modern JavaScript API, optimized for Bun. Offers a unique experience unified type, and end-to-end type safety while maintaining excellent performance.
+        content: Designed with ergonomic design, extensive support for TypeScript, modern JavaScript API, optimized for Bun. Offers a unique experience with unified types, and end-to-end type safety while maintaining excellent performance.
 
     - - meta
       - property: 'og:description'
-        content: Designed with ergonomic design, extensive support for TypeScript, modern JavaScript API, optimized for Bun. Offers a unique experience unified type, and end-to-end type safety while maintaining excellent performance.
+        content: Designed with ergonomic design, extensive support for TypeScript, modern JavaScript API, optimized for Bun. Offers a unique experience with unified types, and end-to-end type safety while maintaining excellent performance.
 ---
 
 <script setup>
diff --git a/docs/blog/elysia-10.md b/docs/blog/elysia-10.md
index 6a68a720..1cbc216e 100644
--- a/docs/blog/elysia-10.md
+++ b/docs/blog/elysia-10.md
@@ -45,7 +45,7 @@ head:
 
 Elysia 1.0 is the first stable release after development for 1.8 years.
 
-Since started, we have always waiting for a framework that focuses on developer experience, velocity, and how to make writing code for humans, not a machine.
+Since we started, we have always been waiting for a framework that focuses on developer experience, velocity, and how to make writing code for humans, not a machine.
 
 We battle-test Elysia in various situations, simulate medium and large-scale projects, shipping code to clients and this is the first version that we felt confident enough to ship.
 
diff --git a/docs/blog/elysia-11.md b/docs/blog/elysia-11.md
index 4f2cd16d..847883a7 100644
--- a/docs/blog/elysia-11.md
+++ b/docs/blog/elysia-11.md
@@ -89,7 +89,7 @@ new Elysia()
 
 ![jaeger showing collected trace automatically](/blog/elysia-11/jaeger.webp)
 
-Elysia OpenTelemetry is will **collect span of any library compatible OpenTelemetry standard**, and will apply parent and child span automatically.
+Elysia OpenTelemetry will **collect span of any library compatible with the OpenTelemetry standard**, and will apply parent and child span automatically.
 
 In the code above, we apply `Prisma` to trace how long each query took.
 
diff --git a/docs/blog/elysia-12.md b/docs/blog/elysia-12.md
index ab86edcf..9573fdb2 100644
--- a/docs/blog/elysia-12.md
+++ b/docs/blog/elysia-12.md
@@ -10,11 +10,11 @@ head:
 
     - - meta
       - name: 'description'
-        content: Introducing Adapter for universal runtime suppport, Object macro with resolve, Parser with custom name, WebSocket with lifecycle, TypeBox 0.34 with recursive type, and Eden validation inference.
+        content: Introducing Adapter for universal runtime support, Object macro with resolve, Parser with custom name, WebSocket with lifecycle, TypeBox 0.34 with recursive type, and Eden validation inference.
 
     - - meta
       - property: 'og:description'
-        content: Introducing Adapter for universal runtime suppport, Object macro with resolve, Parser with custom name, WebSocket with lifecycle, TypeBox 0.34 with recursive type, and Eden validation inference.
+        content: Introducing Adapter for universal runtime support, Object macro with resolve, Parser with custom name, WebSocket with lifecycle, TypeBox 0.34 with recursive type, and Eden validation inference.
 
     - - meta
       - property: 'og:image'
@@ -38,9 +38,9 @@ head:
     shadow
 >
 
-Named after the song [Φ²](https://youtu.be/b9IkzWO63Fg) from album "At the Fingertip of the Sea" by HoyoMix as used in as in [**"You and Me"**](https://youtu.be/nz_Ra4G57A4).
+Named after the song [Φ²](https://youtu.be/b9IkzWO63Fg) from album "At the Fingertip of the Sea" by HoyoMix as used in [**"You and Me"**](https://youtu.be/nz_Ra4G57A4).
 
-Elysia 1.2 focus on commitment to expand universal runtime support and developer experience:
+Elysia 1.2 focuses on commitment to expand universal runtime support and developer experience:
 - [Adapter](#adapter)
 - [Macro with resolve](#macro-with-resolve)
 - [Parser](#parser)
@@ -92,7 +92,7 @@ We will continue to expand support for more runtimes in the future starting with
 - uWebSocket.js
 
 ### Universal runtime API
-To be comaptible with different runtime, Elysia now wrap over a hand-picked utility function to provide a consistent API across different runtime.
+To be compatible with different runtime, Elysia now wraps over a hand-picked utility function to provide a consistent API across different runtime.
 
 For example, in Bun you may use `Bun.file` to return a file response which is not available in Node.
 
diff --git a/docs/blog/elysia-13.md b/docs/blog/elysia-13.md
index 349bf35f..a63b6265 100644
--- a/docs/blog/elysia-13.md
+++ b/docs/blog/elysia-13.md
@@ -102,7 +102,7 @@ When comparing to the same code **without schema**, we see < 2% performance diff
 
 This is huge.
 
-Previously, you have to choose between safety and performance but as we close the performance gap between using and not using validation. But now you don't have to worry about it.
+Previously, you had to choose between safety and performance as we close the performance gap between using and not using validation. But now you don't have to worry about it.
 
 But now, we drop validation overhead from a significant amount to almost near zero without requiring any changes on your side.
 
@@ -150,13 +150,13 @@ We can then override a public schema by providing a schema in a route handler wh
 ![Elysia run with default override guard showing schema gets override](/blog/elysia-13/schema-override.webp)
 > Elysia run with default override guard
 
-But sometime we **don't want to override** a schema.
+But sometimes we **don't want to override** a schema.
 
 Instead we want it to work both allowing us to combine schemas instead of overriding them.
 
 Starting from Elysia 1.3, we can do just that.
 
-We can now tell Elysia to not to override it and instead treat it as its own by providing a schema as **standalone**.
+We can now tell Elysia not to override it and instead treat it as its own by providing a schema as **standalone**.
 
 ```ts
 import { Elysia } from 'elysia'
@@ -170,7 +170,7 @@ new Elysia()
 	})
 ```
 
-As a result, we have a results that like merging a local and global schema together.
+As a result, we have results that are like merging a local and global schema together.
 
 ![Elysia run with standalone merging multiple guard together](/blog/elysia-13/schema-standalone.webp)
 > Elysia run with standalone merging multiple guard together
@@ -181,7 +181,7 @@ Elysia's type inference is already extremely fast.
 
 We are really confident in our optimization of type inference and it's faster than most frameworks that use an express-like syntax.
 
-However, our users with really **really** large scale with multiple routes and complex type inference.
+However, our users with really **really** large scale applications with multiple routes and complex type inference.
 
 We managed to **reduce type instantiation by half** in most cases, and measured up to 60% improvement in inference speed.
 
@@ -195,7 +195,7 @@ This should solve the problem with users who use heavy object/class for example
 As a result, we should end up with faster IDE auto-completion, suggestion, type checking and Eden Treaty.
 
 ## Performance Improvement
-We have refactored and optimized a lot of internal code which accumulate up to significant improvements.
+We have refactored and optimized a lot of internal code which accumulates up to significant improvements.
 
 ### Route Registration
 
diff --git a/docs/eden/fetch.md b/docs/eden/fetch.md
index af25cea0..e89a363b 100644
--- a/docs/eden/fetch.md
+++ b/docs/eden/fetch.md
@@ -15,9 +15,9 @@ head:
 ---
 
 # Eden Fetch
-A fetch-like alternative to Eden Treaty .
+A fetch-like alternative to Eden Treaty.
 
-With Eden Fetch can interact with Elysia server in a type-safe manner using Fetch API.
+With Eden Fetch, you can interact with Elysia server in a type-safe manner using Fetch API.
 
 ---
 
diff --git a/docs/eden/overview.md b/docs/eden/overview.md
index 413f2f4e..d5ae8ed8 100644
--- a/docs/eden/overview.md
+++ b/docs/eden/overview.md
@@ -7,11 +7,11 @@ head:
 
   - - meta
     - name: 'description'
-      content: Elysia supports end-to-end type safety with Elysia Eden since start. End-to-end type-safety refers to a system in which every component of the system is checked for type consistency, meaning that data is passed between components only if the types of the data are compatible.
+      content: Elysia supports end-to-end type safety with Elysia Eden from the start. End-to-end type-safety refers to a system in which every component of the system is checked for type consistency, meaning that data is passed between components only if the types of the data are compatible.
 
   - - meta
     - property: 'og:description'
-      content: Elysia supports end-to-end type safety with Elysia Eden since start. End-to-end type-safety refers to a system in which every component of the system is checked for type consistency, meaning that data is passed between components only if the types of the data are compatible.
+      content: Elysia supports end-to-end type safety with Elysia Eden from the start. End-to-end type-safety refers to a system in which every component of the system is checked for type consistency, meaning that data is passed between components only if the types of the data are compatible.
 ---
 
 # End-to-End Type Safety
@@ -23,14 +23,14 @@ End-to-end type safety is like making sure all the pieces of the track match up
 
 For a framework to have end-to-end type safety means you can connect client and server in a type-safe manner.
 
-Elysia provide end-to-end type safety **without code generation** out of the box with RPC-like connector, **Eden**
+Elysia provides end-to-end type safety **without code generation** out of the box with an RPC-like connector, **Eden**
 
 <video mute controls>
   <source src="/eden/eden-treaty.mp4" type="video/mp4" />
   Something went wrong trying to load video
 </video>
 
-Others framework that support e2e type safety:
+Other frameworks that support e2e type safety:
 - tRPC
 - Remix
 - SvelteKit
@@ -52,20 +52,20 @@ Hover over variable and function to see type definition.
 Elysia allows you to change the type on the server and it will be instantly reflected on the client, helping with auto-completion and type-enforcement.
 
 ## Eden
-Eden is a RPC-like client to connect Elysia  **end-to-end type safety** using only TypeScript's type inference instead of code generation.
+Eden is an RPC-like client to connect Elysia with **end-to-end type safety** using only TypeScript's type inference instead of code generation.
 
-Allowing you to sync client and server types effortlessly, weighing less than 2KB.
+It allows you to sync client and server types effortlessly, weighing less than 2KB.
 
-Eden is consists of 2 modules:
+Eden consists of 2 modules:
 1. Eden Treaty **(recommended)**: an improved version RFC version of Eden Treaty
-2. Eden Fetch: Fetch-like client with type safety.
+2. Eden Fetch: Fetch-like client with type safety
 
 Below is an overview, use-case and comparison for each module.
 
 ## Eden Treaty (Recommended)
 Eden Treaty is an object-like representation of an Elysia server providing end-to-end type safety and a significantly improved developer experience.
 
-With Eden Treaty we can connect interact Elysia server with full-type support and auto-completion, error handling with type narrowing, and creating type safe unit test.
+With Eden Treaty we can interact with an Elysia server with full-type support and auto-completion, error handling with type narrowing, and create type-safe unit tests.
 
 Example usage of Eden Treaty:
 ```typescript twoslash
@@ -131,5 +131,5 @@ const { data } = await fetch('/name/:name', {
 ```
 
 ::: tip NOTE
-Unlike Eden Treaty, Eden Fetch doesn't provide Web Socket implementation for Elysia server
+Unlike Eden Treaty, Eden Fetch doesn't provide Web Socket implementation for Elysia server.
 :::
diff --git a/docs/eden/treaty/config.md b/docs/eden/treaty/config.md
index 720cb4c4..1cca14bb 100644
--- a/docs/eden/treaty/config.md
+++ b/docs/eden/treaty/config.md
@@ -34,21 +34,21 @@ import type { App } from './server'
 const api = treaty<App>('localhost:3000')
 ```
 
-You may or may not specified a protocol for URL endpoint.
+You may or may not specify a protocol for URL endpoint.
 
-Elysia will appends the endpoints automatically as follows:
+Elysia will append the endpoints automatically as follows:
 1. If protocol is specified, use the URL directly
 2. If the URL is localhost and ENV is not production, use http
 3. Otherwise use https
 
-This also apply to Web Socket as well for determining between **ws://** or **wss://**.
+This also applies to Web Socket as well for determining between **ws://** or **wss://**.
 
 ---
 
 ### Elysia Instance
 If Elysia instance is passed, Eden Treaty will create a `Request` class and pass to `Elysia.handle` directly without creating a network request.
 
-This allows us to interact with Elysia server directly without request overhead, or the need start a server.
+This allows us to interact with Elysia server directly without request overhead, or the need to start a server.
 
 ```typescript
 import { Elysia } from 'elysia'
@@ -61,13 +61,13 @@ const app = new Elysia()
 const api = treaty(app)
 ```
 
-If an instance is passed, generic is not needed to be pass as Eden Treaty can infers the type from a parameter directly.
+If an instance is passed, generic is not needed to be passed as Eden Treaty can infer the type from a parameter directly.
 
-This patterns is recommended for performing unit tests, or creating a type-safe reverse proxy server or micro-services.
+This pattern is recommended for performing unit tests, or creating a type-safe reverse proxy server or micro-services.
 
 ## Options
-2nd optional parameters for Eden Treaty to customize fetch behavior, accepting parameters as follows:
-- [fetch](#fetch) - add default parameters to fetch intialization (RequestInit)
+2nd optional parameter for Eden Treaty to customize fetch behavior, accepting parameters as follows:
+- [fetch](#fetch) - add default parameters to fetch initialization (RequestInit)
 - [headers](#headers) - define default headers
 - [fetcher](#fetcher) - custom fetch function eg. Axios, unfetch
 - [onRequest](#onrequest) - Intercept and modify fetch request before firing
@@ -87,7 +87,7 @@ treaty<App>('localhost:3000', {
 })
 ```
 
-All parameters that passed to fetch, will be passed to fetcher, which is an equivalent to:
+All parameters that are passed to fetch will be passed to fetcher, which is equivalent to:
 ```typescript
 fetch('http://localhost:3000', {
     credentials: 'include'
@@ -114,7 +114,7 @@ fetch('localhost:3000', {
 })
 ```
 
-headers may accepts the following as parameters:
+headers may accept the following as parameters:
 - Object
 - Function
 
@@ -130,7 +130,7 @@ treaty<App>('localhost:3000', {
 ```
 
 ### Function
-You may specify a headers as a function to return custom headers based on condition
+You may specify headers as a function to return custom headers based on condition
 
 ```typescript
 treaty<App>('localhost:3000', {
@@ -151,7 +151,7 @@ headers function accepts 2 parameters:
 - options `RequestInit`: Parameters that passed through 2nd parameter of fetch
 
 ### Array
-You may define a headers function as an array if multiple conditions are need.
+You may define a headers function as an array if multiple conditions are needed.
 
 ```typescript
 treaty<App>('localhost:3000', {
@@ -172,7 +172,7 @@ Eden Treaty will **run all functions** even if the value is already returned.
 Eden Treaty will prioritize the order headers if duplicated as follows:
 1. Inline method - Passed in method function directly
 2. headers - Passed in `config.headers`
-  - If `config.headers` is array, parameters that come after will be prioritize
+  - If `config.headers` is array, parameters that come after will be prioritized
 3. fetch - Passed in `config.fetch.headers`
 
 For example, for the following example:
@@ -190,7 +190,7 @@ api.profile.get({
 })
 ```
 
-This will be results in:
+This will result in:
 ```typescript
 fetch('http://localhost:3000', {
     headers: {
diff --git a/docs/eden/treaty/response.md b/docs/eden/treaty/response.md
index 28b8dfea..77beca1c 100644
--- a/docs/eden/treaty/response.md
+++ b/docs/eden/treaty/response.md
@@ -7,11 +7,11 @@ head:
 
     - - meta
       - name: 'og:description'
-        content: Eden Treaty is an object-like representation of an Elysia server, providing an end-to-end type safety, and a significantly improved developer experience. With Eden, we can fetch an API from Elysia server fully type-safe without code generation.
+        content: Eden Treaty is an object-like representation of an Elysia server, providing end-to-end type safety and a significantly improved developer experience. With Eden, we can fetch an API from Elysia server fully type-safe without code generation.
 
     - - meta
       - name: 'og:description'
-        content: Eden Treaty is an object-like representation of an Elysia server, providing an end-to-end type safety, and a significantly improved developer experience. With Eden, we can fetch an API from Elysia server fully type-safe without code generation.
+        content: Eden Treaty is an object-like representation of an Elysia server, providing end-to-end type safety and a significantly improved developer experience. With Eden, we can fetch an API from Elysia server fully type-safe without code generation.
 ---
 
 # Response
@@ -70,7 +70,7 @@ const submit = async (name: string) => {
 By default, Elysia infers `error` and `response` types to TypeScript automatically, and Eden will be providing auto-completion and type narrowing for accurate behavior.
 
 ::: tip
-If the server responds with an HTTP status >= 300, then the value will be always be `null`, and `error` will have a returned value instead.
+If the server responds with an HTTP status >= 300, then the value will always be `null`, and `error` will have a returned value instead.
 
 Otherwise, response will be passed to `data`.
 :::
diff --git a/docs/eden/treaty/unit-test.md b/docs/eden/treaty/unit-test.md
index 95a7f8af..13b44b95 100644
--- a/docs/eden/treaty/unit-test.md
+++ b/docs/eden/treaty/unit-test.md
@@ -7,17 +7,17 @@ head:
 
     - - meta
       - name: 'og:description'
-        content: Eden Treaty is an object-like representation of an Elysia server, providing an end-to-end type safety, and a significantly improved developer experience. With Eden, we can fetch an API from Elysia server fully type-safe without code generation.
+        content: Eden Treaty is an object-like representation of an Elysia server, providing end-to-end type safety and a significantly improved developer experience. With Eden, we can fetch an API from Elysia server fully type-safe without code generation.
 
     - - meta
       - name: 'og:description'
-        content: Eden Treaty is an object-like representation of an Elysia server, providing an end-to-end type safety, and a significantly improved developer experience. With Eden, we can fetch an API from Elysia server fully type-safe without code generation.
+        content: Eden Treaty is an object-like representation of an Elysia server, providing end-to-end type safety and a significantly improved developer experience. With Eden, we can fetch an API from Elysia server fully type-safe without code generation.
 ---
 
 # Unit Test
 According to [Eden Treaty config](/eden/treaty/config.html#urlorinstance) and [Unit Test](/patterns/unit-test), we may pass an Elysia instance to Eden Treaty directly to interact with Elysia server directly without sending a network request.
 
-We may use this patterns to create a unit test with end-to-end type safety and type-level test all at once.
+We may use this pattern to create a unit test with end-to-end type safety and type-level test all at once.
 
 ```typescript twoslash
 // test/index.test.ts
@@ -29,7 +29,7 @@ const app = new Elysia().get('/hello', 'hi')
 const api = treaty(app)
 
 describe('Elysia', () => {
-    it('return a response', async () => {
+    it('returns a response', async () => {
         const { data } = await api.hello.get()
 
         expect(data).toBe('hi')
@@ -40,7 +40,7 @@ describe('Elysia', () => {
 ```
 
 ## Type safety test
-To perform a type safety test, simply run **tsc** to test folders.
+To perform a type safety test, simply run **tsc** on test folders.
 
 ```bash
 tsc --noEmit test/**/*.ts
diff --git a/docs/essential/best-practice.md b/docs/essential/best-practice.md
index 84b179cc..84c0ebf3 100644
--- a/docs/essential/best-practice.md
+++ b/docs/essential/best-practice.md
@@ -7,26 +7,26 @@ head:
 
     - - meta
       - name: 'description'
-        content: Elysia is pattern agnostic framework, we leave the decision up to you and your team for coding patterns to use. However, we found that there are several who are using MVC pattern (Model-View-Controller) on Elysia, and found it's hard to decouple and handling with types. This page is a guide to use Elysia with MVC pattern.
+        content: Elysia is a pattern agnostic framework, we leave the decision up to you and your team for coding patterns to use. However, we found that there are several who are using MVC pattern (Model-View-Controller) on Elysia, and found it's hard to decouple and handle types. This page is a guide to use Elysia with MVC pattern.
 
     - - meta
       - property: 'og:description'
-        content: Elysia is pattern agnostic framework, we the decision up to you and your team for coding patterns to use. However, we found that there are several who are using MVC pattern (Model-View-Controller) on Elysia, and found it's hard to decouple and handling with types. This page is a guide to use Elysia with MVC pattern.
+        content: Elysia is a pattern agnostic framework, we leave the decision up to you and your team for coding patterns to use. However, we found that there are several who are using MVC pattern (Model-View-Controller) on Elysia, and found it's hard to decouple and handle types. This page is a guide to use Elysia with MVC pattern.
 ---
 
 # Best Practice
 
 Elysia is a pattern-agnostic framework, leaving the decision of which coding patterns to use up to you and your team.
 
-However, there are several concern from trying to adapt an MVC pattern [(Model-View-Controller)](https://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller) with Elysia, and found it's hard to decouple and handle types.
+However, there are several concerns from trying to adapt an MVC pattern [(Model-View-Controller)](https://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller) with Elysia, and we found it's hard to decouple and handle types.
 
-This page is a guide to on how to follows Elysia structure best practice combined with MVC pattern but can be adapted to any coding pattern you like.
+This page is a guide on how to follow Elysia structure best practices combined with MVC pattern but can be adapted to any coding pattern you like.
 
 ## Folder Structure
 
 Elysia is unopinionated about folder structure, leaving you to **decide** how to organize your code yourself.
 
-However, **if you doesn't have a specific structure in mind**, we recommended a feature-based folder structure. Where each feature has its own folder containing controllers, services, models.
+However, **if you don't have a specific structure in mind**, we recommend a feature-based folder structure. Where each feature has its own folder containing controllers, services, and models.
 
 ```
 | src
diff --git a/docs/essential/handler.md b/docs/essential/handler.md
index 60c4ed9d..39d8309c 100644
--- a/docs/essential/handler.md
+++ b/docs/essential/handler.md
@@ -7,11 +7,11 @@ head:
 
     - - meta
       - name: 'description'
-        content: handler is a function that responds to the request for each route. Accepting request information and returning a response to the client. Handler can be registered through Elysia.get / Elysia.post
+        content: A handler is a function that responds to the request for each route. Accepting request information and returning a response to the client. Handler can be registered through Elysia.get / Elysia.post
 
     - - meta
       - property: 'og:description'
-        content: handler is a function that responds to the request for each route. Accepting request information and returning a response to the client. Handler can be registered through Elysia.get / Elysia.post
+        content: A handler is a function that responds to the request for each route. Accepting request information and returning a response to the client. Handler can be registered through Elysia.get / Elysia.post
 ---
 
 <script setup>
@@ -87,11 +87,11 @@ const demo7 = new Elysia()
 
 # Handler
 
-Handler is a function that responds to the request for each route.
+A handler is a function that responds to the request for each route.
 
 Accepting request information and returning a response to the client.
 
-Altenatively, handler is also known as a **Controller** in other frameworks.
+Alternatively, a handler is also known as a **Controller** in other frameworks.
 
 ```typescript
 import { Elysia } from 'elysia'
@@ -102,7 +102,7 @@ new Elysia()
     .listen(3000)
 ```
 
-Handler maybe a literal value, and can be inlined.
+A handler may be a literal value, and can be inlined.
 
 ```typescript
 import { Elysia, file } from 'elysia'
@@ -113,19 +113,19 @@ new Elysia()
     .listen(3000)
 ```
 
-Using an inline value always returns the same value which is useful to optimize performance for static resource like file.
+Using an inline value always returns the same value which is useful to optimize performance for static resources like files.
 
 This allows Elysia to compile the response ahead of time to optimize performance.
 
 ::: tip
 Providing an inline value is not a cache.
 
-Static Resource value, headers and status can be mutate dynamically using lifecycle.
+Static resource values, headers and status can be mutated dynamically using lifecycle.
 :::
 
 ## Context
 
-**Context** contains a request information which unique for each request, and is not shared except for `store` <small>(global mutable state)</small>.
+**Context** contains request information which is unique for each request, and is not shared except for `store` <small>(global mutable state)</small>.
 
 ```typescript twoslash
 import { Elysia } from 'elysia'
@@ -204,10 +204,10 @@ new Elysia()
 
 <Playground :elysia="handler2" />
 
-It's recommend to use `status` inside main handler as it has better inference:
+It's recommended to use `status` inside the main handler as it has better inference:
 
 - allows TypeScript to check if a return value is correctly type to response schema
-- autocompletion for type narrowing base on status code
+- autocompletion for type narrowing based on status code
 - type narrowing for error handling using End-to-end type safety ([Eden](/eden/overview))
 
 ### set.status
@@ -251,7 +251,7 @@ new Elysia()
 ```
 
 ### set.headers
-Allowing us to append or delete a response headers represent as Object.
+Allowing us to append or delete response headers represented as an Object.
 
 ```typescript twoslash
 import { Elysia } from 'elysia'
diff --git a/docs/essential/life-cycle.md b/docs/essential/life-cycle.md
index 7b49fe51..431fb9f9 100644
--- a/docs/essential/life-cycle.md
+++ b/docs/essential/life-cycle.md
@@ -1,17 +1,17 @@
 ---
-title: Life Cycle - ElysiaJS
+title: Lifecycle - ElysiaJS
 head:
     - - meta
       - property: 'og:title'
-        content: Life Cycle - ElysiaJS
+        content: Lifecycle - ElysiaJS
 
     - - meta
       - name: 'description'
-        content: Lifecycle event is a concept for each stage of Elysia processing, "Life Cycle" or "Hook" is an event listener to intercept, and listen to those events cycling around. Hook allows you to transform data running through the data pipeline. With the hook, you can customize Elysia to its fullest potential.
+        content: Lifecycle event is a concept for each stage of Elysia processing, "Lifecycle" or "Hook" is an event listener to intercept, and listen to those events cycling around. Hook allows you to transform data running through the data pipeline. With the hook, you can customize Elysia to its fullest potential.
 
     - - meta
       - property: 'og:description'
-        content: Lifecycle event is a concept for each stage of Elysia processing, "Life Cycle" or "Hook" is an event listener to intercept, and listen to those events cycling around. Hook allows you to transform data running through the data pipeline. With the hook, you can customize Elysia to its fullest potential.
+        content: Lifecycle event is a concept for each stage of Elysia processing, "Lifecycle" or "Hook" is an event listener to intercept, and listen to those events cycling around. Hook allows you to transform data running through the data pipeline. With the hook, you can customize Elysia to its fullest potential.
 ---
 
 <script setup>
@@ -37,13 +37,13 @@ const demo = new Elysia()
 
 # Lifecycle
 
-Life Cycle allows us to intercept an important event at the predefined point allowing us to customize the behavior of our server as needed.
+Lifecycle events allow you to intercept important events at predefined points, allowing you to customize the behavior of your server as needed.
 
-Elysia's Life Cycle event can be illustrated as the following.
+Elysia's lifecycle can be illustrated as the following.
 ![Elysia Life Cycle Graph](/assets/lifecycle-chart.svg)
 > Click on image to enlarge
 
-Below are the request life cycle available in Elysia:
+Below are the request lifecycle events available in Elysia:
 
 <Deck>
     <Card title="Request" href="#request">
@@ -65,7 +65,7 @@ Below are the request life cycle available in Elysia:
         Map returned value into a response
     </Card>
     <Card title="On Error (Error Handling)" href="#on-error-error-handling">
-   		Handle error thrown in life-cycle
+   		Handle errors thrown in the life-cycle
     </Card>
     <Card title="After Response" href="#after-response">
         Executed after response sent to the client
@@ -85,13 +85,13 @@ Explicitly specifying that the response is HTML could be repetitive if there are
 
 This can lead to a lot of duplicated code just to specify the **"text/html"** **"Content-Type"**
 
-But what if after we send a response, we could detect that the response is an HTML string then append the header automatically?
+But what if after we send a response, we could detect that the response is an HTML string and then append the header automatically?
 
-That's when the concept of Life Cycle comes into play.
+That's when the concept of lifecycle comes into play.
 
 ## Hook
 
-We refer to each function that intercepts the life cycle event as **"hook"**, as the function hooks into the lifecycle event.
+We refer to each function that intercepts the lifecycle event as **"hook"**, as the function hooks into the lifecycle event.
 
 Hooks can be categorized into 2 types:
 
@@ -99,12 +99,12 @@ Hooks can be categorized into 2 types:
 2. Interceptor Hook: Execute on every route
 
 ::: tip
-The hook will accept the same Context as a handler, you can imagine adding a route handler but at a specific point.
+The hook will accept the same Context as a handler; you can imagine adding a route handler but at a specific point.
 :::
 
 ## Local Hook
 
-The local hook is executed on a specific route.
+A local hook is executed on a specific route.
 
 To use a local hook, you can inline hook into a route handler:
 
@@ -134,7 +134,7 @@ The response should be listed as follows:
 
 Register hook into every handler **of the current instance** that came after.
 
-To add an interceptor hook, you can use `.on` followed by a life cycle event in camelCase:
+To add an interceptor hook, you can use `.on` followed by a lifecycle event in camelCase:
 
 ```typescript
 import { Elysia } from 'elysia'
@@ -159,7 +159,7 @@ The response should be listed as follows:
 | /hi   | text/html; charset=utf8  |
 | /none | text/plain; charset=utf8 |
 
-Events from other plugins are also applied to the route so the order of code is important.
+Events from other plugins are also applied to the route, so the order of code is important.
 
 ::: tip
 The code above will only apply to the current instance, not applying to parent.
@@ -169,11 +169,11 @@ See [scope](/essential/plugin#scope) to find out why
 
 ## Order of code
 
-The order of Elysia's life-cycle code is very important.
+The order of Elysia's lifecycle code is very important.
 
-Because event will only apply to routes **after** it is registered.
+Because an event will only apply to routes **after** it is registered.
 
-If you put the onError before plugin, plugin will not inherit the onError event.
+If you put the `onError` before plugin, plugin will not inherit the `onError` event.
 
 ```typescript
 import { Elysia } from 'elysia'
@@ -221,9 +221,9 @@ The only exception is `onRequest` which is executed before the route handler so
 
 ## Request
 
-The first life-cycle event to get executed for every new request is recieved.
+The first lifecycle event to get executed for every new request is received.
 
-As `onRequest` is designed to provide only the most crucial context to reduce overhead, it is recommended to use in the following scenario:
+As `onRequest` is designed to provide only the most crucial context to reduce overhead, it is recommended to use in the following scenarios:
 
 - Caching
 - Rate Limiter / IP/Region Lock
@@ -232,7 +232,7 @@ As `onRequest` is designed to provide only the most crucial context to reduce ov
 
 #### Example
 
-Below is a pseudo code to enforce rate-limit on a certain IP address.
+Below is a pseudocode to enforce rate-limits on a certain IP address.
 
 ```typescript
 import { Elysia } from 'elysia'
@@ -246,11 +246,11 @@ new Elysia()
     .listen(3000)
 ```
 
-If a value is returned from `onRequest`, it will be used as the response and the rest of the life-cycle will be skipped.
+If a value is returned from `onRequest`, it will be used as the response and the rest of the lifecycle will be skipped.
 
 ### Pre Context
 
-Context's onRequest is typed as `PreContext`, a minimal representation of `Context` with the attribute on the following:
+Context's `onRequest` is typed as `PreContext`, a minimal representation of `Context` with the attribute on the following:
 request: `Request`
 
 - set: `Set`
@@ -286,7 +286,7 @@ new Elysia().onParse(({ request, contentType }) => {
 })
 ```
 
-The returned value will be assigned to Context.body. If not, Elysia will continue iterating through additional parser functions from **onParse** stack until either body is assigned or all parsers have been executed.
+The returned value will be assigned to `Context.body`. If not, Elysia will continue iterating through additional parser functions from **onParse** stack until either body is assigned or all parsers have been executed.
 
 ### Context
 
@@ -328,7 +328,7 @@ This allows Elysia to optimize body parser ahead of time, and reduce overhead in
 
 ### Explicit Parser
 
-However, in some scenario if Elysia fails to pick the correct body parser function, we 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, we can explicitly tell Elysia to use a certain function by specifying `type`.
 
 ```typescript
 import { Elysia } from 'elysia'
@@ -339,7 +339,7 @@ new Elysia().post('/', ({ body }) => body, {
 })
 ```
 
-Allowing us to control Elysia behavior for picking body parser function to fit our needs in a complex scenario.
+This allows us to control Elysia behavior for picking body parser function to fit our needs in a complex scenario.
 
 `type` may be one of the following:
 
@@ -431,7 +431,7 @@ new Elysia()
 
 Append new value to context directly **before validation**. It's stored in the same stack as **transform**.
 
-Unlike **state** and **decorate** that assigned value before the server started. **derive** assigns a property when each request happens. Allowing us to extract a piece of information into a property instead.
+Unlike **state** and **decorate** that assigned value before the server started. **derive** assigns a property when each request happens. This allows us to extract a piece of information into a property instead.
 
 ```typescript
 import { Elysia } from 'elysia'
@@ -453,7 +453,7 @@ Unlike **state**, and **decorate**. Properties which assigned by **derive** is u
 
 ### Queue
 
-`derive` and `transform` is stored in the same queue.
+`derive` and `transform` are stored in the same queue.
 
 ```typescript
 import { Elysia } from 'elysia'
diff --git a/docs/essential/route.md b/docs/essential/route.md
index 473ef553..ae80ee22 100644
--- a/docs/essential/route.md
+++ b/docs/essential/route.md
@@ -94,7 +94,7 @@ const demo13 = new Elysia()
 
 # Routing
 
-Web servers use the request's **path and HTTP method** to look up the correct resource, refers as **"routing"**.
+Web servers use the request's **path and HTTP method** to look up the correct resource, referred to as **"routing"**.
 
 We can define a route by calling a **method named after HTTP verbs**, passing a path and a function to execute when matched.
 
@@ -114,7 +114,7 @@ By default, web browsers will send a GET method when visiting a page.
 <Playground :elysia="demo1" />
 
 ::: tip
-Using an interactive browser above, hover on a blue highlight area to see difference result between each path
+Using the interactive browser above, hover on the blue highlight area to see different results between each path.
 :::
 
 ## Path type
@@ -202,7 +202,7 @@ Elysia will look up each request for [route](/essential/route) and response usin
 
 URLs can be both static and dynamic.
 
-Static paths are hardcoded strings that can be used to locate resources of the server, while dynamic paths match some part and captures the value to extract extra information.
+Static paths are hardcoded strings that can be used to locate resources on the server, while dynamic paths match some part and capture the value to extract extra information.
 
 For instance, we can extract the user ID from the pathname. For example:
 
@@ -217,7 +217,7 @@ new Elysia()
 
 <br>
 
-Here dynamic path is created with `/id/:id` which tells Elysia to match any path up until `/id`. What comes after that is then stored as **params** object.
+Here, a dynamic path is created with `/id/:id` which tells Elysia to match any path up until `/id`. What comes after that is then stored in the **params** object.
 
 <Playground
   :elysia="demo6"
diff --git a/docs/essential/structure.md b/docs/essential/structure.md
index 32cc6182..8721dad6 100644
--- a/docs/essential/structure.md
+++ b/docs/essential/structure.md
@@ -7,11 +7,11 @@ head:
 
     - - meta
       - name: 'description'
-        content: Elysia is pattern agnostic framework, we leave the decision up to you and your team for coding patterns to use. However, we found that there are several who are using MVC pattern (Model-View-Controller) on Elysia, and found it's hard to decouple and handling with types. This page is a guide to use Elysia with MVC pattern.
+        content: Elysia is a pattern agnostic framework, we leave the decision up to you and your team for coding patterns to use. However, we found that there are several who are using MVC pattern (Model-View-Controller) on Elysia, and found it's hard to decouple and handle types. This page is a guide to use Elysia with MVC pattern.
 
     - - meta
       - property: 'og:description'
-        content: Elysia is pattern agnostic framework, we the decision up to you and your team for coding patterns to use. However, we found that there are several who are using MVC pattern (Model-View-Controller) on Elysia, and found it's hard to decouple and handling with types. This page is a guide to use Elysia with MVC pattern.
+        content: Elysia is a pattern agnostic framework, we leave the decision up to you and your team for coding patterns to use. However, we found that there are several who are using MVC pattern (Model-View-Controller) on Elysia, and found it's hard to decouple and handle types. This page is a guide to use Elysia with MVC pattern.
 ---
 
 #### This page has been moved to [best practice](/essential/best-practice)
@@ -20,14 +20,14 @@ head:
 
 Elysia is a pattern-agnostic framework, leaving the decision of which coding patterns to use up to you and your team.
 
-However, there are several concern from trying to adapt an MVC pattern [(Model-View-Controller)](https://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller) with Elysia, and found it's hard to decouple and handle types.
+However, there are several concerns about trying to adapt an MVC pattern [(Model-View-Controller)](https://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller) with Elysia, and we found it's hard to decouple and handle types.
 
-This page is a guide to on how to follows Elysia structure best practice combined with MVC pattern but can be adapted to any coding pattern you like.
+This page is a guide on how to follow Elysia structure best practices combined with MVC pattern but can be adapted to any coding pattern you like.
 
 ## Method Chaining
 Elysia code should always use **method chaining**.
 
-As Elysia type system is complex, every methods in Elysia returns a new type reference.
+As Elysia's type system is complex, every method in Elysia returns a new type reference.
 
 **This is important** to ensure type integrity and inference.
 
@@ -66,9 +66,9 @@ We recommend to <u>**always use method chaining**</u> to provide an accurate typ
 
 Elysia does a lot to ensure type integrity, if you pass an entire `Context` type to a controller, these might be the problems:
 
-1. Elysia type is complex and heavily depends on plugin and multiple level of chaining.
-2. Hard to type, Elysia type could change at anytime, especially with decorators, and store
-3. Type casting may lead to a loss of type integrity or an inability to ensure consistency between types and runtime code.
+1. Elysia type is complex and heavily depends on plugin and multiple level of chaining
+2. Hard to type, Elysia type could change at any time, especially with decorators, and store
+3. Type casting may lead to a loss of type integrity or an inability to ensure consistency between types and runtime code
 4. This makes it more challenging for [Sucrose](/blog/elysia-10#sucrose) *(Elysia's "kind of" compiler)* to statically analyze your code
 
 ### ❌ Don't: Create a separate controller
@@ -87,10 +87,10 @@ new Elysia()
     .get('/', Controller.hi)
 ```
 
-By passing an entire `Controller.method` to Elysia is an equivalent of having 2 controllers passing data back and forth. It's against the design of framework and MVC pattern itself.
+Passing an entire `Controller.method` to Elysia is equivalent to having 2 controllers passing data back and forth. It's against the design of the framework and MVC pattern itself.
 
 ### ✅ Do: Use Elysia as a controller
-Instead treat an Elysia instance as a controller itself instead.
+Instead, treat an Elysia instance as a controller itself.
 ```typescript
 import { Elysia } from 'elysia'
 import { Service } from './service'
diff --git a/docs/essential/validation.md b/docs/essential/validation.md
index 3da35b8d..8baf462d 100644
--- a/docs/essential/validation.md
+++ b/docs/essential/validation.md
@@ -68,7 +68,7 @@ const demo4 = new Elysia()
 
 The purpose of creating an API server is to take an input and process it.
 
-JavaScript allows any data to be any type. Elysia provides a tool to validate data out of the box to ensure that the data is in the correct format.
+JavaScript allows any data to be of any type. Elysia provides a tool to validate data out of the box to ensure that the data is in the correct format.
 
 ```typescript twoslash
 import { Elysia, t } from 'elysia'
@@ -91,7 +91,7 @@ TypeBox is a very fast, lightweight, and type-safe runtime validation library fo
 We believe that validation should be handled by the framework natively, rather than relying on the user to set up a custom type for every project.
 
 ### TypeScript
-We can get a type definitions of every Elysia/TypeBox's type by accessing `static` property as follows:
+We can get type definitions of every Elysia/TypeBox's type by accessing the `static` property as follows:
 
 ```ts twoslash
 import { t } from 'elysia'
diff --git a/docs/index.md b/docs/index.md
index 95804d83..d2ffd3e2 100644
--- a/docs/index.md
+++ b/docs/index.md
@@ -9,11 +9,11 @@ head:
 
     - - meta
       - name: 'description'
-        content: Elysia is an ergonomic framework for Humans. With end-to-end type safety and great developer experience. Elysia is familiar, fast, and first class TypeScript support with well-thought integration between services whether it's tRPC, Swagger or WebSocket. Elysia got you covered, start building next generation TypeScript web servers today.
+        content: Elysia is an ergonomic framework for Humans. With end-to-end type safety and great developer experience. Elysia is familiar, fast, and has first-class TypeScript support with well-thought integration between services whether it's tRPC, Swagger or WebSocket. Elysia has got you covered, start building next generation TypeScript web servers today.
 
     - - meta
       - property: 'og:description'
-        content: Elysia is an ergonomic framework for Humans. With end-to-end type safety and great developer experience. Elysia is familiar, fast, and first class TypeScript support with well-thought integration between services whether it's tRPC, Swagger or WebSocket. Elysia got you covered, start building next generation TypeScript web servers today.
+        content: Elysia is an ergonomic framework for Humans. With end-to-end type safety and great developer experience. Elysia is familiar, fast, and has first-class TypeScript support with well-thought integration between services whether it's tRPC, Swagger or WebSocket. Elysia has got you covered, start building next generation TypeScript web servers today.
 ---
 
 <script setup>
diff --git a/docs/integrations/astro.md b/docs/integrations/astro.md
index aec01d70..a546ac12 100644
--- a/docs/integrations/astro.md
+++ b/docs/integrations/astro.md
@@ -54,12 +54,12 @@ export const POST = handle // [!code ++]
 
 Elysia will work normally as expected because of WinterCG compliance.
 
-We recommended running [Astro on Bun](https://docs.astro.build/en/recipes/bun) as Elysia is designed to be run on Bun
+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.
 
-However some plugins like **Elysia Static** may not work if you are running Astro on Node.
+However, some plugins like **Elysia Static** may not work if you are running Astro on Node.
 :::
 
 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.
diff --git a/docs/integrations/better-auth.md b/docs/integrations/better-auth.md
index 40c4c702..3b3e760f 100644
--- a/docs/integrations/better-auth.md
+++ b/docs/integrations/better-auth.md
@@ -20,7 +20,7 @@ Better Auth is framework-agnostic authentication (and authorization) framework f
 
 It provides a comprehensive set of features out of the box and includes a plugin ecosystem that simplifies adding advanced functionalities.
 
-We recommended going through [Better Auth basic setup](https://www.better-auth.com/docs/installation) before going through this page.
+We recommend going through the [Better Auth basic setup](https://www.better-auth.com/docs/installation) before going through this page.
 
 Our basic setup will look like this:
 
@@ -56,7 +56,7 @@ Then we can access Better Auth with `http://localhost:3000/api/auth`.
 
 ### Custom endpoint
 
-We recommended setting a prefix path for when using [mount](/patterns/mount.html).
+We recommend setting a prefix path when using [mount](/patterns/mount.html).
 
 ```ts [index.ts]
 import { Elysia } from 'elysia'
diff --git a/docs/integrations/expo.md b/docs/integrations/expo.md
index 57422cc4..36961906 100644
--- a/docs/integrations/expo.md
+++ b/docs/integrations/expo.md
@@ -72,7 +72,7 @@ export const GET = app.handle
 export const POST = app.handle
 ```
 
-This will ensure that Elysia routing will work properly in any location you place in.
+This will ensure that Elysia routing will work properly in any location you place it in.
 
 ## Deployment
 You can either directly use API route using Elysia and deploy as normal Elysia app normally if need or using [experimental Expo server runtime](https://docs.expo.dev/router/reference/api-routes/#deployment).
diff --git a/docs/integrations/nextjs.md b/docs/integrations/nextjs.md
index 3b878773..17742d27 100644
--- a/docs/integrations/nextjs.md
+++ b/docs/integrations/nextjs.md
@@ -7,16 +7,16 @@ head:
 
     - - meta
       - name: 'description'
-        content: With Nextjs App Router, you can run Elysia on Nextjs route. 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 WinterCG compliance.
 
     - - meta
       - property: 'og:description'
-        content: With Nextjs App Router, you can run Elysia on Nextjs route. 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 WinterCG compliance.
 ---
 
-# Integration with Nextjs
+# Integration with Next.js
 
-With Nextjs App Router, we can run Elysia on Nextjs route.
+With Next.js App Router, we can run Elysia on Next.js routes.
 
 1. Create **api/[[...slugs]]/route.ts** inside app router
 2. In **route.ts**, create or import an existing Elysia server
@@ -38,13 +38,13 @@ export const GET = app.handle // [!code ++]
 export const POST = app.handle // [!code ++]
 ```
 
-Elysia will work normally as expected because of WinterCG compliance, however, some plugins like **Elysia Static** may not work if you are running Nextjs on Node.
+Elysia will work normally as expected because of WinterCG compliance, however, some plugins like **Elysia Static** may not work if you are running Next.js on Node.
 
-You can treat the Elysia server as a normal Nextjs API route.
+You can treat the Elysia server as a normal Next.js API route.
 
 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](https://elysiajs.com/eden/overview.html) with both client-side and server action
 
-Please refer to [Nextjs Route Handlers](https://nextjs.org/docs/app/building-your-application/routing/route-handlers#static-route-handlers) for more information.
+Please refer to [Next.js Route Handlers](https://nextjs.org/docs/app/building-your-application/routing/route-handlers#static-route-handlers) for more information.
 
 ## Prefix
 
diff --git a/docs/integrations/openapi.md b/docs/integrations/openapi.md
index 96c58f5e..4a602fe9 100644
--- a/docs/integrations/openapi.md
+++ b/docs/integrations/openapi.md
@@ -33,14 +33,14 @@ const app = new Elysia()
     .use(swagger())
 ```
 
-By default, Elysia use OpenAPI V3 schema and [Scalar UI](http://scalar.com) by default
+By default, Elysia uses OpenAPI V3 schema and [Scalar UI](http://scalar.com)
 
 For Swagger plugin configuration, see the [Swagger plugin page](/plugins/swagger).
 
 ## Route definitions
 We add route information by providing a schema type.
 
-However, sometime defining a type only isn't clear what the route might work. You can use `schema.detail` fields to explictly define what the route is all about.
+However, sometimes defining only a type does not make it clear what the route might do. You can use `schema.detail` fields to explicitly define what the route is all about.
 
 ```typescript
 import { Elysia, t } from 'elysia'
@@ -58,7 +58,7 @@ new Elysia()
                 })
             },
             { // [!code ++]
-                description: 'Expected an username and password' // [!code ++]
+                description: 'Expected a username and password' // [!code ++]
             } // [!code ++]
         ),
         detail: { // [!code ++]
@@ -75,9 +75,9 @@ Detail is then passed to Swagger to put the description to Swagger route.
 ### detail
 `detail` extends the [OpenAPI Operation Object](https://swagger.io/specification#operation-object)
 
-The detail field is an object that can be use to describe information about the route for API documentation.
+The detail field is an object that can be used to describe information about the route for API documentation.
 
-Which may contains the following fields:
+It may contain the following fields:
 
 ### tags
 An array of tags for the operation. Tags can be used for logical grouping of operations by resources or any other qualifier.
@@ -116,7 +116,7 @@ new Elysia()
                 password: t.String()
             },
             {
-                description: 'Expected an username and password'
+                description: 'Expected a username and password'
             }
         ),
         detail: { // [!code ++]
diff --git a/docs/integrations/opentelemetry.md b/docs/integrations/opentelemetry.md
index 96486386..e5ce9293 100644
--- a/docs/integrations/opentelemetry.md
+++ b/docs/integrations/opentelemetry.md
@@ -34,7 +34,7 @@ new Elysia().use(
 
 ![jaeger showing collected trace automatically](/blog/elysia-11/jaeger.webp)
 
-Elysia OpenTelemetry will **collect span of any library compatible OpenTelemetry standard**, and will apply parent and child span automatically.
+Elysia OpenTelemetry will **collect span of any library compatible with OpenTelemetry standard**, and will apply parent and child span automatically.
 
 In the code above, we apply `Prisma` to trace how long each query took.
 
diff --git a/docs/integrations/react-email.md b/docs/integrations/react-email.md
index e62d6292..517d08a5 100644
--- a/docs/integrations/react-email.md
+++ b/docs/integrations/react-email.md
@@ -72,7 +72,7 @@ export default function OTPEmail({ otp }: { otp: number }) {
                         This code is valid for 10 minutes
                     </Text>
                     <Text className="text-gray-600 text-xs">
-                        Thank you joining us
+                        Thank you for joining us
                     </Text>
                 </Section>
             </Section>
diff --git a/docs/key-concept.md b/docs/key-concept.md
index 07b9203a..c090995c 100644
--- a/docs/key-concept.md
+++ b/docs/key-concept.md
@@ -21,7 +21,7 @@ Although Elysia is a simple library, it has some key concepts that you need to u
 This page covers most important concepts of Elysia that you should know.
 
 ::: tip
-We __highly recommend__ you to read this page before learn more about Elysia.
+We __highly recommend__ you to read this page before learning more about Elysia.
 :::
 
 ## Everything is a component
diff --git a/docs/migrate/from-express.md b/docs/migrate/from-express.md
index 1df127d7..3aced689 100644
--- a/docs/migrate/from-express.md
+++ b/docs/migrate/from-express.md
@@ -13,11 +13,11 @@ head:
 
     - - meta
       - name: 'description'
-        content: This guide is for Express users who want to see a differences from Express including syntax, and how to migrate your application from Express to Elysia by example.
+        content: This guide is for Express users who want to see the differences from Express including syntax, and how to migrate your application from Express to Elysia by example.
 
     - - meta
       - property: 'og:description'
-        content: This guide is for Express users who want to see a differences from Express including syntax, and how to migrate your application from Express to Elysia by example.
+        content: This guide is for Express users who want to see the differences from Express including syntax, and how to migrate your application from Express to Elysia by example.
 ---
 
 <script setup>
@@ -30,11 +30,11 @@ import Benchmark from '../components/fern/benchmark-express.vue'
 
 # From Express to Elysia
 
-This guide is for Express users who want to see a differences from Express including syntax, and how to migrate your application from Express to Elysia by example.
+This guide is for Express users who want to see the differences from Express including syntax, and how to migrate your application from Express to Elysia by example.
 
 **Express** is a popular web framework for Node.js, and widely used for building web applications and APIs. It is known for its simplicity and flexibility.
 
-**Elysia** is an ergonomic web framework for Bun, Node.js, and runtime that support Web Standard API. Designed to be ergonomic and developer-friendly with a focus on **sounds type safety** and performance.
+**Elysia** is an ergonomic web framework for Bun, Node.js, and runtimes that support Web Standard API. Designed to be ergonomic and developer-friendly with a focus on **sound type safety** and performance.
 
 ## Performance
 Elysia has significant performance improvements over Express thanks to native Bun implementation, and static code analysis.
@@ -43,7 +43,7 @@ Elysia has significant performance improvements over Express thanks to native Bu
 
 ## Routing
 
-Express and Elysia has similar routing syntax, using `app.get()` and `app.post()` methods to define routes and similar path parameters syntax.
+Express and Elysia have similar routing syntax, using `app.get()` and `app.post()` methods to define routes and similar path parameter syntax.
 
 <Compare>
 
diff --git a/docs/migrate/from-fastify.md b/docs/migrate/from-fastify.md
index 0fa43ac5..c2742e28 100644
--- a/docs/migrate/from-fastify.md
+++ b/docs/migrate/from-fastify.md
@@ -13,7 +13,7 @@ head:
 
     - - meta
       - name: 'description'
-        content: This guide is for Fastify users who want to see a differences from Fastify including syntax, and how to migrate your application from Fastify to Elysia by example.
+        content: This guide is for Fastify users who want to see the differences from Fastify including syntax, and how to migrate your application from Fastify to Elysia by example.
 
     - - meta
       - property: 'og:description'
@@ -34,7 +34,7 @@ This guide is for Fastify users who want to see a differences from Fastify inclu
 
 **Fastify** is a fast and low overhead web framework for Node.js, designed to be simple and easy to use. It is built on top of the HTTP module and provides a set of features that make it easy to build web applications.
 
-**Elysia** is an ergonomic web framework for Bun, Node.js, and runtime that support Web Standard API. Designed to be ergonomic and developer-friendly with a focus on **sounds type safety** and performance.
+**Elysia** is an ergonomic web framework for Bun, Node.js, and runtime that supports Web Standard API. Designed to be ergonomic and developer-friendly with a focus on **sound type safety** and performance.
 
 ## Performance
 Elysia has significant performance improvements over Fastify thanks to native Bun implementation, and static code analysis.
diff --git a/docs/migrate/from-hono.md b/docs/migrate/from-hono.md
index d1841d76..ffc9f1c9 100644
--- a/docs/migrate/from-hono.md
+++ b/docs/migrate/from-hono.md
@@ -13,7 +13,7 @@ head:
 
     - - meta
       - name: 'description'
-        content: This guide is for Hono users who want to see a differences from Elysia including syntax, and how to migrate your application from Hono to Elysia by example.
+        content: This guide is for Hono users who want to see the differences from Elysia including syntax, and how to migrate your application from Hono to Elysia by example.
 
     - - meta
       - property: 'og:description'
@@ -34,9 +34,9 @@ This guide is for Hono users who want to see a differences from Elysia including
 
 **Hono** is a fast and lightweight built on Web Standard. It has broad compatibility with multiple runtime like Deno, Bun, Cloudflare Workers, and Node.js.
 
-**Elysia** is an ergonomic web framework. Designed to be ergonomic and developer-friendly with a focus on **sounds type safety** and performance.
+**Elysia** is an ergonomic web framework. Designed to be ergonomic and developer-friendly with a focus on **sound type safety** and performance.
 
-Both frameworks are built on top of Web Standard API, and has slight different syntax. Hono offers more compatability with multiple runtimes while Elysia focus on specific set of runtimes.
+Both frameworks are built on top of Web Standard API, and have slightly different syntax. Hono offers more compatibility with multiple runtimes while Elysia focuses on a specific set of runtimes.
 
 ## Performance
 Elysia has significant performance improvements over Hono thanks to static code analysis.
diff --git a/docs/patterns/configuration.md b/docs/patterns/configuration.md
index c719bfe3..394dc949 100644
--- a/docs/patterns/configuration.md
+++ b/docs/patterns/configuration.md
@@ -162,7 +162,7 @@ new Elysia({
 })
 ```
 
-When unknown properties that is not specified in schema is found on either input and output, how should Elysia handle the field?
+When unknown properties that are not specified in schema are found on either input and output, how should Elysia handle the field?
 
 Options - @default `true`
 
@@ -176,7 +176,7 @@ Options - @default `true`
 
 ###### Since 1.0.0
 
-Whether should Elysia should [precompile all routes](/blog/elysia-10.html#improved-startup-time) a head of time before starting the server.
+Whether Elysia should [precompile all routes](/blog/elysia-10.html#improved-startup-time) ahead of time before starting the server.
 
 ```ts twoslash
 import { Elysia } from 'elysia'
diff --git a/docs/patterns/cookie.md b/docs/patterns/cookie.md
index 9470c92a..a36019c0 100644
--- a/docs/patterns/cookie.md
+++ b/docs/patterns/cookie.md
@@ -7,11 +7,11 @@ head:
 
   - - meta
     - name: 'description'
-      content: Reactive Cookie take a more modern approach like signal to handle cookie with an ergonomic API. There's no 'getCookie', 'setCookie', everything is just a cookie object. When you want to use cookie, you just extract the name and value directly.
+      content: Reactive Cookie takes a more modern approach like signals to handle cookies with an ergonomic API. There's no 'getCookie', 'setCookie', everything is just a cookie object. When you want to use cookies, you just extract the name and value directly.
 
   - - meta
     - property: 'og:description'
-      content: Reactive Cookie take a more modern approach like signal to handle cookie with an ergonomic API. There's no 'getCookie', 'setCookie', everything is just a cookie object. When you want to use cookie, you just extract the name and value directly.
+      content: Reactive Cookie takes a more modern approach like signals to handle cookies with an ergonomic API. There's no 'getCookie', 'setCookie', everything is just a cookie object. When you want to use cookies, you just extract the name and value directly.
 ---
 
 # Cookie
@@ -31,10 +31,10 @@ new Elysia()
     })
 ```
 
-By default, Reactive Cookie can encode/decode type of object automatically allowing us to treat cookie as an object without worrying about the encoding/decoding. **It just works**.
+By default, Reactive Cookie can encode/decode object types automatically allowing us to treat cookies as objects without worrying about the encoding/decoding. **It just works**.
 
 ## Reactivity
-The Elysia cookie is reactive. This means that when you change the cookie value, the cookie will be updated automatically based on approach like signal.
+The Elysia cookie is reactive. This means that when you change the cookie value, the cookie will be updated automatically based on an approach like signals.
 
 A single source of truth for handling cookies is provided by Elysia cookies, which have the ability to automatically set headers and sync cookie values.
 
diff --git a/docs/patterns/deploy.md b/docs/patterns/deploy.md
index fc3c8bd5..556ad9b6 100644
--- a/docs/patterns/deploy.md
+++ b/docs/patterns/deploy.md
@@ -18,9 +18,9 @@ head:
 This page is a guide on how to deploy Elysia to production.
 
 ## Compile to binary
-We recommended running a build command before deploying to production as it could potentially reduce memory usage and file size significantly.
+We recommend running a build command before deploying to production as it could potentially reduce memory usage and file size significantly.
 
-We recommended compile Elysia into a single binary using the command as follows:
+We recommend compiling Elysia into a single binary using the command as follows:
 ```bash
 bun build \
 	--compile \
@@ -33,7 +33,7 @@ bun build \
 
 This will generate a portable binary `server` which we can run to start our server.
 
-Compiling server to binary usually significantly reduce memory usage by 2-3x compared to development environment.
+Compiling server to binary usually significantly reduces memory usage by 2-3x compared to development environment.
 
 This command is a bit long, so let's break it down:
 1. `--compile` - Compile TypeScript to binary
@@ -43,7 +43,7 @@ This command is a bit long, so let's break it down:
 5. `--outfile server` - Output the binary as `server`
 6. `./src/index.ts` - The entry file of our server (codebase)
 
-To start our server, simly run the binary.
+To start our server, simply run the binary.
 ```bash
 ./server
 ```
@@ -57,7 +57,7 @@ Bun does have `--minify` flag that will minify the binary.
 
 However if we are using [OpenTelemetry](/plugins/opentelemetry), it's going to reduce a function name to a single character.
 
-This make tracing harder than it should as OpenTelemetry rely on a function name.
+This makes tracing harder than it should as OpenTelemetry relies on a function name.
 
 However, if you're not using OpenTelemetry, you may opt in for `--minify` instead
 ```bash
@@ -70,7 +70,7 @@ bun build \
 ```
 
 ### Permission
-Some Linux distro might not be able to run the binary, we suggest enable executable permission to a binary if you're on Linux:
+Some Linux distros might not be able to run the binary, we suggest enabling executable permission to a binary if you're on Linux:
 ```bash
 chmod +x ./server
 
@@ -82,7 +82,7 @@ If you're trying to deploy a binary to your server but unable to run with random
 
 It means that the machine you're running on **doesn't support AVX2**.
 
-Unfortunately, Bun require machine that has an `AVX2` hardware support.
+Unfortunately, Bun requires a machine that has `AVX2` hardware support.
 
 There's no workaround as far as we know.
 
diff --git a/docs/patterns/macro.md b/docs/patterns/macro.md
index ebb66f27..0fdd1083 100644
--- a/docs/patterns/macro.md
+++ b/docs/patterns/macro.md
@@ -76,7 +76,7 @@ const app = new Elysia()
     })
 ```
 
-**macro** shine when a logic is more complex than accepting a new function, for example creating an authorization layer for each route.
+**macro** shines when a logic is more complex than accepting a new function, for example creating an authorization layer for each route.
 
 ```typescript twoslash
 // @filename: auth.ts
diff --git a/docs/patterns/mount.md b/docs/patterns/mount.md
index 00558bb8..60aa4e99 100644
--- a/docs/patterns/mount.md
+++ b/docs/patterns/mount.md
@@ -7,11 +7,11 @@ head:
 
   - - meta
     - name: 'description'
-      content: Applying WinterCG interplopable code to run with Elysia or vice-versa.
+      content: Applying WinterCG interoperable code to run with Elysia or vice-versa.
 
   - - meta
     - property: 'og:description'
-      content: Applying WinterCG interplopable code to run with Elysia or vice-versa.
+      content: Applying WinterCG interoperable code to run with Elysia or vice-versa.
 ---
 
 # Mount
diff --git a/docs/patterns/trace.md b/docs/patterns/trace.md
index 164356a7..e8cd3dc0 100644
--- a/docs/patterns/trace.md
+++ b/docs/patterns/trace.md
@@ -7,11 +7,11 @@ head:
 
     - - meta
       - name: 'description'
-        content: Trace is an API to measure the performance of your server. Allowing us to interact with the duration span of each life-cycle events and measure the performance of each function to identify performance bottlenecks of the server.
+        content: Trace is an API to measure the performance of your server. It allows you to interact with the duration span of each life-cycle event and measure the performance of each function to identify performance bottlenecks of the server.
 
     - - meta
       - name: 'og:description'
-        content: Trace is an API to measure the performance of your server. Allowing us to interact with the duration span of each life-cycle events and measure the performance of each function to identify performance bottlenecks of the server.
+        content: Trace is an API to measure the performance of your server. It allows you to interact with the duration span of each life-cycle event and measure the performance of each function to identify performance bottlenecks of the server.
 ---
 
 # Trace
@@ -20,7 +20,7 @@ Performance is an important aspect for Elysia.
 
 We don't want to be fast for benchmarking purposes, we want you to have a real fast server in real-world scenario.
 
-There are many factors that can slow down our app - and it's hard to identify them, but **trace** can helps solve that problem by injecting start and stop code to each life-cycle.
+There are many factors that can slow down our app - and it's hard to identify them, but **trace** can help solve that problem by injecting start and stop code to each life-cycle.
 
 Trace allows us to inject code to before and after of each life-cycle event, block and interact with the execution of the function.
 
@@ -29,7 +29,7 @@ Trace use a callback listener to ensure that callback function is finished befor
 
 To use `trace`, you need to call `trace` method on the Elysia instance, and pass a callback function that will be executed for each life-cycle event.
 
-You may listen to each lifecycle by adding `on` prefix follows by life-cycle name, for example `onHandle` to listen to `handle` event.
+You may listen to each lifecycle by adding `on` prefix followed by the lifecycle name, for example `onHandle` to listen to the `handle` event.
 
 ```ts twoslash
 import { Elysia } from 'elysia'
@@ -51,7 +51,7 @@ Please refer to [Life Cycle Events](/essential/life-cycle#events) for more infor
 ![Elysia Life Cycle](/assets/lifecycle-chart.svg)
 
 ## Children
-Every events except `handle` have a children, which is an array of events that are executed inside for each life-cycle event.
+Every event except `handle` has children, which is an array of events that are executed inside for each lifecycle event.
 
 You can use `onEvent` to listen to each child event in order
 
diff --git a/docs/patterns/websocket.md b/docs/patterns/websocket.md
index 8dfc9b39..d4a0b2bb 100644
--- a/docs/patterns/websocket.md
+++ b/docs/patterns/websocket.md
@@ -18,11 +18,11 @@ head:
 
 WebSocket is a realtime protocol for communication between your client and server.
 
-Unlike HTTP where our client repeatedly asking the website for information and waiting for a reply each time, WebSocket sets up a direct line where our client and server can send messages back and forth directly, making the conversation quicker and smoother without having to start over each message.
+Unlike HTTP where our client repeatedly asks the website for information and waits for a reply each time, WebSocket sets up a direct line where our client and server can send messages back and forth directly, making the conversation quicker and smoother without having to start over with each message.
 
 SocketIO is a popular library for WebSocket, but it is not the only one. Elysia uses [uWebSocket](https://github.com/uNetworking/uWebSockets) which Bun uses under the hood with the same API.
 
-To use websocket, simply call `Elysia.ws()`:
+To use WebSocket, simply call `Elysia.ws()`:
 
 ```typescript
 import { Elysia } from 'elysia'
@@ -38,7 +38,7 @@ new Elysia()
 
 ## WebSocket message validation:
 
-Same as normal route, WebSockets also accepts a **schema** object to strictly type and validate requests.
+Same as normal routes, WebSockets also accept a **schema** object to strictly type and validate requests.
 
 ```typescript
 import { Elysia, t } from 'elysia'
diff --git a/docs/plugins/cron.md b/docs/plugins/cron.md
index 31bf4f3d..912daec9 100644
--- a/docs/plugins/cron.md
+++ b/docs/plugins/cron.md
@@ -16,7 +16,7 @@ head:
 
 # Cron Plugin
 
-This plugin adds support for running cronjob in the Elysia server.
+This plugin adds support for running cronjobs in the Elysia server.
 
 Install with:
 
diff --git a/docs/plugins/jwt.md b/docs/plugins/jwt.md
index ac435d4a..f64e07d2 100644
--- a/docs/plugins/jwt.md
+++ b/docs/plugins/jwt.md
@@ -15,7 +15,7 @@ head:
 ---
 
 # JWT Plugin
-This plugin adds support for using JWT in Elysia handler
+This plugin adds support for using JWT in Elysia handlers.
 
 Install with:
 ```bash
diff --git a/docs/plugins/overview.md b/docs/plugins/overview.md
index 6dae5a95..429ce845 100644
--- a/docs/plugins/overview.md
+++ b/docs/plugins/overview.md
@@ -44,13 +44,13 @@ This is to ensure developers end up with a performant web server they intend to
 
 ## Community plugins:
 
--   [Create ElysiaJS](https://github.com/kravetsone/create-elysiajs) - scaffolding your Elysia project with the environment with easy (help with ORM, Linters and Plugins)!
+-   [Create ElysiaJS](https://github.com/kravetsone/create-elysiajs) - scaffold your Elysia project with the environment easily (help with ORM, Linters and Plugins)!
 -   [Lucia Auth](https://github.com/pilcrowOnPaper/lucia) - authentication, simple and clean
 -   [Elysia Clerk](https://github.com/wobsoriano/elysia-clerk) - unofficial Clerk authentication plugin
 -   [Elysia Polyfills](https://github.com/bogeychan/elysia-polyfills) - run Elysia ecosystem on Node.js and Deno
--   [Vite server](https://github.com/kravetsone/elysia-vite-server) - plugin which start and decorate [`vite`](https://vitejs.dev/) dev server in `development` and in `production` mode serve static (if it needed)
+-   [Vite server](https://github.com/kravetsone/elysia-vite-server) - plugin which starts and decorates [`vite`](https://vitejs.dev/) dev server in `development` and in `production` mode serves static files (if needed)
 -   [Vite](https://github.com/timnghg/elysia-vite) - serve entry HTML file with Vite's scripts injected
--   [Nuxt](https://github.com/trylovetom/elysiajs-nuxt) - easily integrate elysia with nuxt!
+-   [Nuxt](https://github.com/trylovetom/elysiajs-nuxt) - easily integrate Elysia with Nuxt!
 -   [Remix](https://github.com/kravetsone/elysia-remix) - use [Remix](https://remix.run/) with `HMR` support (powered by [`vite`](https://vitejs.dev/))! Close a really long-standing plugin request [#12](https://github.com/elysiajs/elysia/issues/12)
 -   [Sync](https://github.com/johnny-woodtke/elysiajs-sync) - a lightweight offline-first data synchronization framework powered by [Dexie.js](https://dexie.org/)
 -   [Connect middleware](https://github.com/kravetsone/elysia-connect-middleware) - plugin which allows you to use [`express`](https://www.npmjs.com/package/express)/[`connect`](https://www.npmjs.com/package/connect) middleware directly in Elysia!
diff --git a/docs/quick-start.md b/docs/quick-start.md
index a89281ec..def6d618 100644
--- a/docs/quick-start.md
+++ b/docs/quick-start.md
@@ -7,11 +7,11 @@ head:
 
     - - meta
       - name: 'description'
-        content: Elysia is a library built for Bun and the only prerequisite. To start, bootstrap a new project with "bun create elysia hi-elysia" and start the development server with "bun dev". This is all it needs to do a quick start or get started with ElysiaJS.
+        content: Elysia is a library built for Bun and the only prerequisite. To start, bootstrap a new project with "bun create elysia hi-elysia" and start the development server with "bun dev". This is all you need to do a quick start or get started with ElysiaJS.
 
     - - meta
       - property: 'og:description'
-        content: Elysia is a library built for Bun and the only prerequisite. To start, bootstrap a new project with "bun create elysia hi-elysia" and start the development server with "bun dev". This is all it needs to do a quick start or get started with ElysiaJS.
+        content: Elysia is a library built for Bun and the only prerequisite. To start, bootstrap a new project with "bun create elysia hi-elysia" and start the development server with "bun dev". This is all you need to do a quick start or get started with ElysiaJS.
 ---
 
 <script setup>
diff --git a/docs/tutorial.md b/docs/tutorial.md
index 8f006b13..ecf74951 100644
--- a/docs/tutorial.md
+++ b/docs/tutorial.md
@@ -10,11 +10,11 @@ head:
 
     - - meta
       - name: 'description'
-        content: Elysia is a library built for Bun and the only prerequisite. To start, bootstrap a new project with "bun create elysia hi-elysia" and start the development server with "bun dev". This is all it needs to do a quick start or get started with ElysiaJS.
+        content: Elysia is a library built for Bun and the only prerequisite. To start, bootstrap a new project with "bun create elysia hi-elysia" and start the development server with "bun dev". This is all you need to do a quick start or get started with ElysiaJS.
 
     - - meta
       - property: 'og:description'
-        content: Elysia is a library built for Bun and the only prerequisite. To start, bootstrap a new project with "bun create elysia hi-elysia" and start the development server with "bun dev". This is all it needs to do a quick start or get started with ElysiaJS.
+        content: Elysia is a library built for Bun and the only prerequisite. To start, bootstrap a new project with "bun create elysia hi-elysia" and start the development server with "bun dev". This is all you need to do a quick start or get started with ElysiaJS.
 ---
 
 # Elysia Tutorial
@@ -23,7 +23,7 @@ We will be building a small CRUD note-taking API server.
 
 There's no database or other "production ready" features. This tutorial is going to only focus on Elysia feature and how to use Elysia only.
 
-We expected it to take around 15-20 minutes if you follow along.
+We expect it to take around 15-20 minutes if you follow along.
 
 ---
 
@@ -45,7 +45,7 @@ If you have used other popular frameworks like Express, Fastify, or Hono, you wi
 
 ### Not a fan of tutorial?
 
-If you prefers to a more try-it-yourself approach, you can skip this tutorial and go straight to the [key concept](/key-concept) page to get a good understanding of how Elysia works.
+If you prefer a more try-it-yourself approach, you can skip this tutorial and go straight to the [key concept](/key-concept) page to get a good understanding of how Elysia works.
 
 <script setup>
 import Card from './components/nearl/card.vue'
@@ -60,7 +60,7 @@ import Deck from './components/nearl/card-deck.vue'
 
 ### llms.txt
 
-Alternatively, you can download <a href="/llms.txt" download>llms.txt</a> or <a href="/llms-full.txt" download>llms-full.txt</a> and feeds it to your favorite LLMs like ChatGPT, Claude or Gemini to get a more interactive experience.
+Alternatively, you can download <a href="/llms.txt" download>llms.txt</a> or <a href="/llms-full.txt" download>llms-full.txt</a> and feed it to your favorite LLMs like ChatGPT, Claude or Gemini to get a more interactive experience.
 
 <Deck>
     <Card title="llms.txt" href="/llms.txt" download>