From 612612767425797e211e694c2f105bdc554b503e Mon Sep 17 00:00:00 2001 From: Rich Harris Date: Tue, 24 Feb 2026 21:16:20 -0500 Subject: [PATCH] Update documentation/docs/97-best-practices/10-best-practices.md Co-authored-by: ComputerGuy <63362464+Ocean-OS@users.noreply.github.com> --- documentation/docs/97-best-practices/10-best-practices.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/docs/97-best-practices/10-best-practices.md b/documentation/docs/97-best-practices/10-best-practices.md index fc79458c9c..a006c76729 100644 --- a/documentation/docs/97-best-practices/10-best-practices.md +++ b/documentation/docs/97-best-practices/10-best-practices.md @@ -160,7 +160,7 @@ If a component uses CSS variables in his styling you can automatically pass them In Svelte 4 stores were THE way to allow interactivity outside of a `.svelte` file. In Svelte 5 that changed and you can now use a `.svelte.{ts|js}` file with universal reactivity. -When possible prefer to use universal reactivity instead of creating a store. Some projects might have stores already in use consider that when writing a new utility. +When possible, prefer to use universal reactivity instead of stores. If you're writing a utility that may be used across multiple projects, keep in mind that some projects may still use stores, and try to make your utilities backwards-compatible. ## Context