From eb65ca16b029d55a1af6baef2b07463944e5d79a Mon Sep 17 00:00:00 2001
From: Manoj M J <mmj@gitlab.com>
Date: Thu, 30 Nov 2023 14:42:59 +0000
Subject: [PATCH] Update understanding_explain_plans.md

---
 doc/development/database/understanding_explain_plans.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/development/database/understanding_explain_plans.md b/doc/development/database/understanding_explain_plans.md
index 00522cb1feeb..22c52c047451 100644
--- a/doc/development/database/understanding_explain_plans.md
+++ b/doc/development/database/understanding_explain_plans.md
@@ -571,8 +571,8 @@ what if we slightly change the purpose of it? What if instead of retrieving all
 projects with `visibility_level` 0 or 20, we retrieve those that a user
 interacted with somehow?
 
-Fortunately, GitLab has an answer for this, and it's a table called
-`user_interacted_projects`. This table has the following schema:
+Prior to GitLab 16.7, GitLab used a table named `user_interacted_projects` to track user interactions with projects.
+This table had the following schema:
 
 ```sql
 Table "public.user_interacted_projects"
-- 
GitLab