From 33ad5d5d5fd9e5f0b27aa6a602f12f2c8bbbbd15 Mon Sep 17 00:00:00 2001
From: zkldi <20380519+zkldi@users.noreply.github.com>
Date: Tue, 20 Sep 2022 02:42:32 +0100
Subject: [PATCH] docs: update stale dbseeds info

---
 docs/docs/tachi-server/infrastructure/database-seeds.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/docs/tachi-server/infrastructure/database-seeds.md b/docs/docs/tachi-server/infrastructure/database-seeds.md
index 0f9d5d097..f24d5cefc 100644
--- a/docs/docs/tachi-server/infrastructure/database-seeds.md
+++ b/docs/docs/tachi-server/infrastructure/database-seeds.md
@@ -1,6 +1,6 @@
 # Database Seeds
 
-Tachi uses a separate git repository called the [Database Seeds](https://github.com/TNG-dev/Tachi/tree/staging/database-seeds) to maintain 'static' databases.
+Tachi tracks the contents of its songs and charts in something called the [Database Seeds](https://github.com/TNG-dev/Tachi/tree/staging/database-seeds).
 
 The databases in question aren't (normally) altered by the server code. We essentially overload git and its CI tools to version control parts of our database.
 
@@ -12,9 +12,9 @@ They also include all Folder Documents, Table Documents and BMS Course Documents
 
 ## Synchronisation
 
-When pushes are made to `develop` (the main branch), our running staging servers will automatically update to that new bit of data.
+When pushes are made to `staging` (the main branch), our running staging servers will automatically update to that new bit of data.
 
-When pushes are made to `production`, our running *production* servers will automatically update in the same way.
+When pushes are made to `release/2.X`, our running *production* servers will automatically update in the same way.
 
 ## Why bother?