Merge pull request #76 from arungurung/patch-1

fix: typo

Author: SaltyAom

docs/concept/explicit-body.md

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

docs/concept/guard.md

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

docs/concept/plugin.md

@@ -89,7 +89,7 @@ const app = new Elysia()
 Config type will be inferred into `use`, generating auto completion and type strict as intend.
 
 ## Plugin deduplication
-By default, Elysia will registered any plugin and handle type definitions which when using multiple times will results in a multiple duplication of setting value or routes.
+By default, Elysia will register any plugin and handle type definitions which when using multiple times will results in a multiple duplication of setting value or routes.
 
 This can be fixed by providing name and optional seeds to help Elysia identify instance duplication:
 ```ts

docs/concept/schema.md

@@ -25,7 +25,7 @@ The schema consists of:
 - params - validate path parameters.
 - header - validate request's headers.
 - response - validate response type.
-- detail - Explicitly define what can route does, see ([creating documentation](/patterns/creating-documentation)) for more explanation.
+- detail - Explicitly define what a route can do, see ([creating documentation](/patterns/creating-documentation)) for more explanation.
 
 Schema is defined as:
 - Locally: in a handler