Merge pull request #97 from Sk0voroda/issue-84

Issue-84: fix plugin page in docs

Author: SaltyAom

docs/concept/plugin.md

@@ -1,23 +1,25 @@
 ---
 title: Plugin - ElysiaJS
 head:
-  - - meta
-    - property: 'og:title'
-      content: Plugin - ElysiaJS
+    - - meta
+      - property: 'og:title'
+        content: Plugin - ElysiaJS
 
-  - - meta
-    - name: 'description'
-      content: A plugin is a way to decouple logic into smaller parts, defining reusable components across the server. Plugin can be registered by using `use` method, registering a plugin will combine types between plugin and current instance, and the scope of hooks and schema get merged as well.
+    - - meta
+      - name: 'description'
+        content: A plugin is a way to decouple logic into smaller parts, defining reusable components across the server. Plugin can register by using `use`, registering a plugin will combine types between plugin and current instance, and the scope of hooks, and schema get merged too.
 
-  - - meta
-    - property: 'og:description'
-      content: A plugin is a way to decouple logic into smaller parts, defining reusable components across the server. Plugin can be registered by using `use` method, registering a plugin will combine types between plugin and current instance, and the scope of hooks and schema get merged as well.
+    - - meta
+      - property: 'og:description'
+        content: A plugin is a way to decouple logic into smaller parts, defining reusable components across the server. Plugin can register by using `use`, registering a plugin will combine types between plugin and current instance, and the scope of hooks, and schema get merged too.
 ---
 
 # Plugin
+
 A plugin is a way to decouple logic into smaller parts, defining reusable components across the server.
 
 Defining a plugin is as simple as defining a new Elysia instance:
+
 ```typescript
 import { Elysia } from 'elysia'
 
@@ -36,77 +38,79 @@ Plugin can be registered by using `use` method.
 Registering a plugin will combine types between plugin and current instance, and the scope of hooks and schema get merged as well.
 
 ## Separate file
-Using plugin pattern, you can separate your logic into a separate file.
+Using plugin pattern, you can define decouple your logic into a separate file.
+
 ```ts
 // plugin.ts
-export const plugin = new Elysia()
-    .get('/from-plugin', () => 'Hi')
+export const plugin = new Elysia().get('/from-plugin', () => 'Hi')
 
 // main.ts
 import { plugin } from './plugin'
 
-const app = new Elysia()
-    .use(plugin)
-    .listen(8080)
+const app = new Elysia().use(plugin).listen(8080)
 ```
 
 ## Functional callback
+
 You can also define a function callback to inline the plugin.
 
 ```ts
 // plugin.ts
-export const plugin = (app: Elysia) => app
-    .get('/from-plugin', () => 'Hi')
+export const plugin = (app: Elysia) => app.get('/from-plugin', () => 'Hi')
 
 // main.ts
 import { plugin } from './plugin'
 
-const app = new Elysia()
-    .use(plugin)
-    .listen(8080)
+const app = new Elysia().use(plugin).listen(8080)
 ```
 
 Functional callback will allow user to access main instance values like routes schema, store.
 
 ## Config
+
 You can customize plugin by creating function to return callback which accepts Elysia.
 
 ```typescript
 import { Elysia } from 'elysia'
 
-const plugin = <const Prefix>({
-    prefix = '/v1'
-}: { prefix: Prefix }) => new Elysia({ prefix })
-    .get(`/hi`, () => 'Hi')
+const plugin = <const Prefix>({ prefix = '/v1' }: { prefix: Prefix }) =>
+    new Elysia({ prefix }).get(`/hi`, () => 'Hi')
 
 const app = new Elysia()
-    .use(plugin({
-        prefix: '/v2'
-    }))
+    .use(
+        plugin({
+            prefix: '/v2'
+        })
+    )
     .listen(8080)
 ```
 
 Config type will be inferred into `use`, generating auto completion and type strict as intend.
 
 ## Plugin deduplication
+
 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
 import { Elysia } from 'elysia'
 
-const plugin = (config) => new Elysia({
-    name: 'my-plugin',
-    seed: config
-})
-    .get(`/${config.prefix}/hi`, () => 'Hi')
+const plugin = (config) =>
+    new Elysia({
+        name: 'my-plugin',
+        seed: config
+    }).get(`${config.prefix}/hi`, () => 'Hi')
 
 const app = new Elysia()
-    .use(plugin({
-        prefix: '/v2'
-    }))
+    .use(
+        plugin({
+            prefix: '/v2'
+        })
+    )
     .listen(8080)
 ```
 
 ## Official plugins
+
 You can find pre-built plugins for Elysia at [plugins](/plugins/overview).