docs: modifying typos in guide document (#287)

zce · Jan 29, 2025 · e2abb8a · e2abb8a
1 parent 0989791
commit e2abb8a
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/docs/guide/introduction.md b/docs/guide/introduction.md
@@ -111,7 +111,7 @@ Velite is framework agnostic, and out of the box support for React, Vue, Svelte,
 - image processing by [Sharp](https://sharp.pixelplumbing.com)
 - file watching by [Chokidar](https://github.com/paulmillr/chokidar)
 
-### Fast Rebuid
+### Fast Rebuild
 
 More then **1000** documents with **2000** assets, less then **8s** for cold start, less then **60ms** for hot rebuild.
 

diff --git a/docs/guide/using-mdx.md b/docs/guide/using-mdx.md
@@ -167,7 +167,7 @@ import { Callout } from '../components/callout'
 
 :::
 
-If Velite uses a bundler to comiple your MDX, the `Callout` component will be bundled into each MDX file, which will cause a lot of redundancy in the output code.
+If Velite uses a bundler to compile your MDX, the `Callout` component will be bundled into each MDX file, which will cause a lot of redundancy in the output code.
 
 Instead, simply use whatever components you want in your MDX files without a import.
-Original file line number
+Diff line change
@@ Expand Up / @@ -167,7 +167,7 @@ import { Callout } from '../components/callout' @@
     :::
-    If Velite uses a bundler to comiple your MDX, the `Callout` component will be bundled into each MDX file, which will cause a lot of redundancy in the output code.
+    If Velite uses a bundler to compile your MDX, the `Callout` component will be bundled into each MDX file, which will cause a lot of redundancy in the output code.
     Instead, simply use whatever components you want in your MDX files without a import.
@@ Expand Down @@