From dda5e0f2bb971282c76dbc58b0e9858f95de394a Mon Sep 17 00:00:00 2001
From: Kaan <81116098+kaan650@users.noreply.github.com>
Date: Thu, 22 Oct 2026 15:10:40 +0300
Subject: [PATCH] Remove strict mode primitive output check from docs (#106)

Co-authored-by: centau <83140718+centau@users.noreply.github.com>
---
 docs/api/strict-mode.md | 9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)

diff --git a/docs/api/strict-mode.md b/docs/api/strict-mode.md
index 6f9ee80..6e29df3 100644
--- a/docs/api/strict-mode.md
+++ b/docs/api/strict-mode.md
@@ -16,11 +16,10 @@ Currently, strict mode will:
 
 1. Run reactive scopes twice when a source updates.
 2. Throw an error if yields occur where they are not allowed.
-3. Checks for `indexes()` and `values()` outputting primitive values.
-4. Checks for `values()` input having duplicate values.
-5. Checks for duplicate nested properties at same depth.
-6. Checks for destruction of an active scope.
-7. Better error reporting and stack traces.
+3. Checks for `values()` input having duplicate values.
+4. Checks for duplicate nested properties at same depth.
+5. Checks for destruction of an active scope.
+6. Better error reporting and stack traces.
 
 By rerunning reactive scopes twice each time they update, it helps ensure that
 computations are pure, and that any cleanup is done correctly.