From 8186b7412eafa84b847efa77886eab432f356012 Mon Sep 17 00:00:00 2001 From: Bobbie Goede Date: Sat, 27 Apr 2024 03:05:29 +0200 Subject: [PATCH] docs: fix typos (#1825) --- docs/guide/advanced/format.md | 2 +- docs/guide/advanced/typescript.md | 6 +++--- docs/guide/advanced/wc.md | 2 +- docs/guide/essentials/started.md | 2 +- docs/guide/integrations/nuxt3.md | 2 +- 5 files changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/guide/advanced/format.md b/docs/guide/advanced/format.md index bb27d735a..6c5f2f2a1 100644 --- a/docs/guide/advanced/format.md +++ b/docs/guide/advanced/format.md @@ -51,7 +51,7 @@ export const messageCompiler: MessageCompiler = ( /** * for AST. * If you would like to support it, - * You need to transform locale mesages such as `json`, `yaml`, etc. with the bundle plugin. + * You need to transform locale messages such as `json`, `yaml`, etc. with the bundle plugin. */ onError && onError(new Error('not support for AST') as CompileError) return () => key diff --git a/docs/guide/advanced/typescript.md b/docs/guide/advanced/typescript.md index ce158505a..64eb7fd77 100644 --- a/docs/guide/advanced/typescript.md +++ b/docs/guide/advanced/typescript.md @@ -132,7 +132,7 @@ const { t, n } = useI18n<{ ``` @@ -191,7 +191,7 @@ define schema for global scope: import enUS from './en-US.json' -// define message schema as master mesage schema +// define message schema as master message schema export type MessageSchema = typeof enUS // define number format schema @@ -220,7 +220,7 @@ const { t, n } = useI18n<{ message: MessageSchema, number: NumberSchema }>({ ``` diff --git a/docs/guide/advanced/wc.md b/docs/guide/advanced/wc.md index 26af7708a..c148baf45 100644 --- a/docs/guide/advanced/wc.md +++ b/docs/guide/advanced/wc.md @@ -14,7 +14,7 @@ This will support the use of Vue I18n in Web Components starting with Vue I18n v There are a few things to keep in mind when using Vue I18n with Web Components. -## Make preparetion for Web Components to host the I18n instance +## Make preparation for Web Components to host the I18n instance Using `defineCustomElement`, which is supported since Vue 3.2, we can provide Vue components implemented in SFC as Web Components. This means that Vue components implemented using `useI18n` can be served as Web Components with i18n support. diff --git a/docs/guide/essentials/started.md b/docs/guide/essentials/started.md index 86bc53068..3762ea351 100644 --- a/docs/guide/essentials/started.md +++ b/docs/guide/essentials/started.md @@ -109,4 +109,4 @@ In Vue I18n v9 and later, the API offered by Vue I18n v8.x is called **Legacy AP The following sections will be explained using the Legacy API. -If you wuold like to use it in Composition API style and already understand Vue I18n, you can step to [here](../advanced/composition). +If you would like to use it in Composition API style and already understand Vue I18n, you can step to [here](../advanced/composition). diff --git a/docs/guide/integrations/nuxt3.md b/docs/guide/integrations/nuxt3.md index 40a3e466a..126269e11 100644 --- a/docs/guide/integrations/nuxt3.md +++ b/docs/guide/integrations/nuxt3.md @@ -206,7 +206,7 @@ touch locales/fr.json # for french touch locales/ja.json # for japanese ``` -Let's populate them with the follwing: +Let's populate them with the following: For english at `locales/en.json`: