From bdee48e6173abc126f93fa82e4c5391ce7fd3e01 Mon Sep 17 00:00:00 2001 From: haimingZZ Date: Tue, 22 Sep 2026 16:46:57 +0800 Subject: [PATCH] docs(vue): fix typo 'loosing' -> 'losing' in v5 migration guide MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Correct the spelling of 'losing' in the v5 migration guide for the Vue adapter. 'Loosing' means 'to release/unfasten', while 'losing' means 'to be deprived of' — the latter is the intended meaning here. --- docs/framework/vue/guides/migrating-to-v5.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/framework/vue/guides/migrating-to-v5.md b/docs/framework/vue/guides/migrating-to-v5.md index ab15ce4eccf..34191595f5d 100644 --- a/docs/framework/vue/guides/migrating-to-v5.md +++ b/docs/framework/vue/guides/migrating-to-v5.md @@ -13,7 +13,7 @@ ref: docs/framework/react/guides/migrating-to-v5.md To fix compatibility with Vue 2, `useQueries` composable now returns `queries` array wrapped in `ref`. Previously `reactive` was returned which led to multiple problems: -- User could spread return value loosing reactivity. +- User could spread return value losing reactivity. - `readonly` wrapper used for return value was breaking Vue 2 reactivity detection mechanism. This was a silent issue in Vue 2.6, but appeared as error in Vue 2.7. - Vue 2 does not support arrays as a root value of `reactive`.