From 7301ba35176237af05325e3b3e6863c9aed17e52 Mon Sep 17 00:00:00 2001
From: Nick Ao <32089264+nickxlao919@users.noreply.github.com>
Date: Mon, 20 Sep 2021 18:34:11 +0800
Subject: [PATCH] docs(README): fix typo in the README of vite-plugin-vue-i18n
 (#45)

---
 packages/vite-plugin-vue-i18n/README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/packages/vite-plugin-vue-i18n/README.md b/packages/vite-plugin-vue-i18n/README.md
index e455280..c4b6de1 100644
--- a/packages/vite-plugin-vue-i18n/README.md
+++ b/packages/vite-plugin-vue-i18n/README.md
@@ -218,7 +218,7 @@ vite-plugin-vue-i18n will automatically select and bundle Vue I18n build accordi
 
 About details, See the [here](https://vue-i18n.intlify.dev/guide/advanced/optimization.html#improve-performance-and-reduce-bundle-size-with-runtime-build-only)
 
-### For `petite-vue-ei18n`
+### For `petite-vue-i18n`
 
 vite-plugin-vue-i18n will automatically select and bundle `petite-vue-i18n` build according to the following vite behavior:
 
@@ -423,7 +423,7 @@ About details, See the below section
 - **Type:** `boolean`
 - **Default:** `false`
 
-  Whether to use the imporot name of `petite-vue-i18n` with the same import name as vue-i18n (`import { xxx } from ‘vue-i18n’`).
+  Whether to use the import name of `petite-vue-i18n` with the same import name as vue-i18n (`import { xxx } from 'vue-i18n'`).
 
   This option allows a smooth migration from `petite-vue-i18n` to `vue-i18n` and allows progressive enhacement.