📘 doc: release 1.3.0

Author: SaltyAom

docs/blog/elysia-11.md

@@ -218,8 +218,7 @@ Elysia 1.1 now normalize data before it's being processed.
 To ensure that data is consistent and safe, Elysia will try to coerce data into an exact data shape defined in schema, removing additional fields, and normalizing data into a consistent format.
 
 For example if you have a schema like this:
-```typescript twoslash
-// @errors: 2353
+```typescript
 import { Elysia, t } from 'elysia'
 import { treaty } from '@elysiajs/eden'
 

docs/eden/installation.md

@@ -76,7 +76,7 @@ import type { App } from './server' // [!code ++]
 const client = treaty<App>('localhost:3000') // [!code ++]
 
 // response: Hi Elysia
-const { data: index } = await client.index.get()
+const { data: index } = await client.get()
 
 // response: 1895
 const { data: id } = await client.id({ id: 1895 }).get()

docs/eden/overview.md

@@ -101,7 +101,7 @@ app.
 
 
 // Call [GET] at '/'
-const { data } = await app.index.get()
+const { data } = await app.get()
 
 // Call [PUT] at '/nendoroid/:id'
 const { data: nendoroid, error } = await app.nendoroid({ id: 1895 }).put({

docs/eden/treaty/overview.md

@@ -88,15 +88,15 @@ Eden Treaty turns an Elysia server into a tree-like file system that can be acce
 
 | Path         | Treaty       |
 | ------------ | ------------ |
-| /            | .index       |
+| /            |              |
 | /hi          | .hi          |
 | /deep/nested | .deep.nested |
 
 Combined with the HTTP method, we can interact with the Elysia server.
 
 | Path         | Method | Treaty              |
 | ------------ | ------ | ------------------- |
-| /            | GET    | .index.get()        |
+| /            | GET    | .get()              |
 | /hi          | GET    | .hi.get()           |
 | /deep/nested | GET    | .deep.nested.get()  |
 | /deep/nested | POST   | .deep.nested.post() |