From e2abb8a0f8fb973d4ff81f2791cdf4d3e70445e9 Mon Sep 17 00:00:00 2001
From: Boongranii <102457140+bbjbc@users.noreply.github.com>
Date: Wed, 29 Jan 2025 18:55:55 +0900
Subject: [PATCH] docs: modifying typos in guide document (#287)

---
 docs/guide/introduction.md | 2 +-
 docs/guide/using-mdx.md    | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/guide/introduction.md b/docs/guide/introduction.md
index e699288..b27a132 100644
--- 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
index 6d2c73c..5a52ab6 100644
--- 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.