From 9345f38352b44c65be9518257710660e0e0e0694 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Matej=20=C4=8Cern=C3=BD?= <matej.cern@gmail.com>
Date: Sat, 22 Nov 2025 21:32:39 +0100
Subject: [PATCH] docs: remove "computed" from composable usage restrictions

---
 src/guide/reusability/composables.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/guide/reusability/composables.md b/src/guide/reusability/composables.md
index 09155f8465..c68edfbf1e 100644
--- a/src/guide/reusability/composables.md
+++ b/src/guide/reusability/composables.md
@@ -302,7 +302,7 @@ These restrictions are important because these are the contexts where Vue is abl
 
 1. Lifecycle hooks can be registered to it.
 
-2. Computed properties and watchers can be linked to it, so that they can be disposed when the instance is unmounted to prevent memory leaks.
+2. Watchers can be linked to it, so that they can be disposed when the instance is unmounted to prevent memory leaks.
 
 :::tip
 `<script setup>` is the only place where you can call composables **after** using `await`. The compiler automatically restores the active instance context for you after the async operation.