docs: correct grammatical errors

DaxServer · DaxServer · commit 716b6b4ee14d · 2025-06-26T14:23:34.000+02:00
diff --git 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/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/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'
diff --git a/docs/essential/life-cycle.md b/docs/essential/life-cycle.md
@@ -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.
+Life Cycle allows us to intercept important events at predefined points, allowing us to customize the behavior of our server as needed.
 
 Elysia's Life Cycle event 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 life cycles available in Elysia:
 
 <Deck>
     <Card title="Request" href="#request">
diff --git a/docs/essential/validation.md b/docs/essential/validation.md
@@ -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
@@ -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/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
@@ -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 about 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'
@@ -77,7 +77,7 @@ Detail is then passed to Swagger to put the description to Swagger route.
 
 The detail field is an object that can be use 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.
diff --git 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
@@ -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/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/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/overview.md b/docs/plugins/overview.md
diff --git a/docs/quick-start.md b/docs/quick-start.md
diff --git a/docs/tutorial.md b/docs/tutorial.md
