From e62a80797b744d9068890a134e98a7445fad44be Mon Sep 17 00:00:00 2001
From: Rich Harris <rich.harris@vercel.com>
Date: Thu, 31 Oct 2024 16:09:05 -0400
Subject: [PATCH] remove comment

---
 documentation/docs/06-runtime/01-stores.md | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/documentation/docs/06-runtime/01-stores.md b/documentation/docs/06-runtime/01-stores.md
index 92282a8574..efaff6e99f 100644
--- a/documentation/docs/06-runtime/01-stores.md
+++ b/documentation/docs/06-runtime/01-stores.md
@@ -2,10 +2,6 @@
 title: Stores
 ---
 
-<!-- - how to use
-- how to write
-- TODO should the details for the store methods belong to the reference section? -->
-
 > [!NOTE] Prior to the introduction of runes, stores were the primary state management mechanism for anything that couldn't be expressed as component state or props. With runes — which can be used in [`.svelte.js/ts`](svelte-js-files) files as well as in components — stores are rarely necessary, though you will still sometimes encounter them when using Svelte.
 
 A _store_ is an object that allows reactive access to a value via a simple [_store contract_](#Store-contract). The [`svelte/store`](../svelte-store) module contains minimal store implementations that fulfil this contract.