From f6a8e36bf8108abf2e0e90fa8ea1b9ea2ed020f8 Mon Sep 17 00:00:00 2001
From: Magnuti <43852515+Magnuti@users.noreply.github.com>
Date: Thu, 3 Jul 2025 01:28:18 +0200
Subject: [PATCH] docs: fix documentation for seed file (#36805)

Fix documentation for seed file
---
 .../content/guides/local-development/seeding-your-database.mdx  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/apps/docs/content/guides/local-development/seeding-your-database.mdx b/apps/docs/content/guides/local-development/seeding-your-database.mdx
index 0a62b619d1a..4426ea1f7f8 100644
--- a/apps/docs/content/guides/local-development/seeding-your-database.mdx
+++ b/apps/docs/content/guides/local-development/seeding-your-database.mdx
@@ -11,7 +11,7 @@ Seeding is the process of populating a database with initial data, typically use
 
 ## Using seed files
 
-Seed files are executed every time you run `supabase start` or `supabase db reset`. Seeding occurs _after_ all database migrations have been completed. As a best practice, only include data insertions in your seed files, and avoid adding schema statements.
+Seed files are executed the first time you run `supabase start` and every time you run `supabase db reset`. Seeding occurs _after_ all database migrations have been completed. As a best practice, only include data insertions in your seed files, and avoid adding schema statements.
 
 By default, if no specific configuration is provided, the system will look for a seed file matching the pattern `supabase/seed.sql`. This maintains backward compatibility with earlier versions, where the seed file was placed in the `supabase` folder.