Fix typos/grammar in method-chaining.md

Author: tcaruth

docs/patterns/method-chaining.md

@@ -17,7 +17,7 @@ head:
 # Method Chaining
 Elysia heavily **encourages the use of method chaining**.
 
-Because Elysia's type system is complex, method usually introduce a new type to the instance.
+Because Elysia's type system is complex, methods usually introduce a new type to the instance.
 
 Using method chaining will help save that new type reference.
 
@@ -31,9 +31,9 @@ const app = new Elysia()
 ```
 Using this, `state` now returns new `ElysiaInstance` type, introducing `build` into store and replace the current one.
 
-Method chaining now save that new type and pass it to `get`, which is why `get` now have type access of `build`.
+Method chaining now saves that new type and passes it to `get`, which is why `get` now has type access of `build`.
 
-Without using method chaning, Elysia doesn't save the new type when introduced, leading to no type inference.
+Without using method chaining, Elysia doesn't save the new type when introduced, leading to no type inference.
 ```typescript
 const app = new Elysia()
 
@@ -45,4 +45,4 @@ app.get('/', ({ store: { build } }) => build)
 app.listen(3000)
 ```
 
-That's why Elysia encourage use of method chaining, not only that it reduce redundant usage of `app.` prefix, but also have better type inference.
+That's why Elysia encourage use of method chaining, not only that it reduces redundant usage of the `app.` prefix, but also to provide better type inference.