Skip to content

Commit 1585d4c

Browse files
authored
docs: correct grammar, spelling
Minor adjustments which make the mount.md docs page more concise and readable.
1 parent 4b5dcd5 commit 1585d4c

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

docs/patterns/mount.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -15,13 +15,13 @@ head:
1515
---
1616

1717
# Mount
18-
WinterCG is a standard for web-interoperable runtimes supports by Cloudflare, Deno, Vercel Edge Runtime, Netlify Function and various more, allowing web server to runs interoperable across runtime, which use Web Standard definitions like `Fetch`, `Request`, and `Response`.
18+
WinterCG is a standard for web-interoperable runtimes. Supported by Cloudflare, Deno, Vercel Edge Runtime, Netlify Function, and various others, it allows web servers to run interoperably across runtimes that use Web Standard definitions like `Fetch`, `Request`, and `Response`.
1919

20-
Elysia is WinterCG compliance as we are optimized to Bun but also openly support other runtime if possible.
20+
Elysia is WinterCG compliant. We are optimized to run on Bun but also openly support other runtimes if possible.
2121

22-
In theory, this allows any framework or code that is WinterCG compliance to be run together, allowing framework like Elysia, Hono, Remix, Itty Router to runs together in a simple function.
22+
In theory, this allows any framework or code that is WinterCG compliant to be run together, allowing frameworks like Elysia, Hono, Remix, Itty Router to run together in a simple function.
2323

24-
By this, we implemented the same logic for Elysia by introducing `.mount` method to runs any framework or code that is WinterCG compliant.
24+
Adhering to this, we implemented the same logic for Elysia by introducing `.mount` method to run with any framework or code that is WinterCG compliant.
2525

2626
## Mount
2727
To use `.mount`, [simply pass a `fetch` function](https://twitter.com/saltyAom/status/1684786233594290176):
@@ -38,7 +38,7 @@ A **fetch** function is a function that accepts a Web Standard Request and retur
3838
type fetch = (request: RequestLike) => Response
3939
```
4040
41-
By default, this declaration are used by:
41+
By default, this declaration is used by:
4242
- Bun
4343
- Deno
4444
- Vercel Edge Runtime
@@ -47,9 +47,9 @@ By default, this declaration are used by:
4747
- Remix Function Handler
4848
- etc.
4949
50-
Which means you can run all of the above code to interlop with Elysia all in a single server, or re-used and existing functions all in one deployment, no need to set up a Reverse Proxy for handling multiple servers.
50+
This allows you to execute all the aforementioned code in a single server environment, making it possible to interact seamlessly with Elysia. You can also reuse existing functions within a single deployment, eliminating the need for a reverse proxy to manage multiple servers.
5151
52-
If the framework also support a **.mount** function, you can deeply nested a framework that support it infinitely.
52+
If the framework also supports a **.mount** function, you can deeply nest a framework that supports it.
5353
```ts
5454
const elysia = new Elysia()
5555
.get('/Hello from Elysia inside Hono inside Elysia')
@@ -65,7 +65,7 @@ const main = new Elysia()
6565
```
6666

6767
## Reusing Elysia
68-
You can even re-use multiple existing Elysia project in your server.
68+
Moreover, you can re-use multiple existing Elysia projects on your server.
6969

7070
```ts
7171
import A from 'project-a/elysia'
@@ -80,4 +80,4 @@ new Elysia()
8080

8181
If an instance passed to `mount` is an Elysia instance, it will be resolved with `use` automatically, providing type-safety and support for Eden by default.
8282

83-
This made the possiblility of interlopable framework and runtime, into a reality.
83+
This makes the possibility of an interoperable framework and runtime a reality.

0 commit comments

Comments
 (0)