From edb5ac5856546fa07eac5f5d9792933fb3d78167 Mon Sep 17 00:00:00 2001
From: Vince Schramer <885196+scvnc@users.noreply.github.com>
Date: Sat, 14 Jan 2023 15:05:10 -0600
Subject: [PATCH] clarify restrictions on where composables can be invoked

I have seen some vue developers interpret this section as: when calling composables in a `<script setup>` or `setup()` context, you must call them synchronously. This is good, however feel like we may need to be clear that composables also should only be called in `<script setup>` or `setup()` regardless of whether they are a/synchronously called, and for the reasons described later in the section.

Composables should, in all cases, be called:

  1. in `<script setup>` or `setup()` hook
  2. synchronously
---
 src/guide/reusability/composables.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/guide/reusability/composables.md b/src/guide/reusability/composables.md
index 2cd53c2974..80f99de260 100644
--- a/src/guide/reusability/composables.md
+++ b/src/guide/reusability/composables.md
@@ -277,9 +277,9 @@ It is OK to perform side effects (e.g. adding DOM event listeners or fetching da
 
 ### Usage Restrictions {#usage-restrictions}
 
-Composables should only be called **synchronously** in `<script setup>` or the `setup()` hook. In some cases, you can also call them in lifecycle hooks like `onMounted()`.
+Composables should only be called in `<script setup>` or the `setup()` hook. They should also be called **synchronously** in these contexts. In some cases, you can also call them in lifecycle hooks like `onMounted()`.
 
-These are the contexts where Vue is able to determine the current active component instance. Access to an active component instance is necessary so that:
+These restrictions are important because these are the contexts where Vue is able to determine the current active component instance. Access to an active component instance is necessary so that:
 
 1. Lifecycle hooks can be registered to it.