Merge branch 'main' into patch-1

Author: fecony

docs/essential/life-cycle.md

@@ -16,15 +16,15 @@ head:
 
 # Life Cycle
 
-Also knows as middleware with name in Express or Hook in Fastify.
+Also known as middleware with name in Express or Hook in Fastify.
 
 Imagine we want to return a text of HTML.
 
 We need to set **"Content-Type"** headers as **"text/html"** to for browser to render HTML.
 
-Explicitly specify that response is HTML could be repetitive if there are a lot of handlers, says ~200 endpoints.
+Explicitly specifying that response is HTML could be repetitive if there are a lot of handlers, says ~200 endpoints.
 
-We can see a duplicated code for just to specify that response is HTML.
+We can see a duplicated code for just specifying that response is HTML.
 
 But what if after we sent a response, we could detect if a response is an HTML string then append headers automatically?
 
@@ -46,7 +46,7 @@ Most of the events you are going to use are highlighted in the blue area but to
 Elysia does the following for every request:
 
 1. **Request**
-    - Notify new event is received, providing only the most minimal context to reduce overhead
+    - Notify when a new event is received, providing only the most minimal context to reduce overhead
     - Best for:
         - Caching
         - Analytics
@@ -87,15 +87,15 @@ These events are designed to help you decouple code into smaller reusable pieces
 
 ## Hook
 
-We refer to each function that intercepts the life cycle event as **"hook"**, as the function hook into the lifecycle event.
+We refer to each function that intercepts the life cycle event as **"hook"**, as the function hooks into the lifecycle event.
 
 Hooks can be categorized into 2 types:
 
 1. Local Hook: Execute on a specific route
 2. Interceptor Hook: Execute on every route
 
 ::: tip
-The hook will accept the same Context as a handler, you can imagine you 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
@@ -187,4 +187,4 @@ Console should log as the following:
 1
 2
 3
-```
+```

docs/patterns/cookie-signature.md

@@ -39,7 +39,7 @@ new Elysia()
                 name: t.String()
             })
         }, {
-            secret: 'Fischl von Luftschloss Narfidort',
+            secrets: 'Fischl von Luftschloss Narfidort',
             sign: ['profile']
         })
     })

docs/plugins/overview.md

@@ -80,6 +80,7 @@ This is to ensure developers end up with a performant web server they intend to
 -   [Elysia Flash Messages](https://github.com/gtramontina/elysia-flash-messages) - enable flash messages
 -   [Elysia AuthKit](https://github.com/gtramontina/elysia-authkit) - unnoficial [WorkOS' AuthKit](https://www.authkit.com/) authentication
 -   [Elysia Error Handler](https://github.com/gtramontina/elysia-error-handler) - simpler error handling
+-   [Elysia Drizzle Schema](https://github.com/Edsol/elysia-drizzle-schema) - Helps to use Drizzle ORM schema inside elysia swagger model.
 -   [Unify-Elysia](https://github.com/qlaffont/unify-elysia) - Unify error code for Elysia
 -   [Unify-Elysia-GQL](https://github.com/qlaffont/unify-elysia-gql) - Unify error code for Elysia GraphQL Server (Yoga & Apollo)
 -   [Elysia Auth Drizzle](https://github.com/qlaffont/elysia-auth-drizzle) - Library who handle authentification with JWT (Header/Cookie/QueryParam).