From 2f51bdd1cefe252e5286802cccde66e5cda4cd6c Mon Sep 17 00:00:00 2001
From: Steve Song <5407809+SteveXiSong@users.noreply.github.com>
Date: Wed, 25 May 2022 12:39:37 -0700
Subject: [PATCH] [Docs] Remove confusing doc content in Colocation doc
 (#12655)

This content along with the doc was migrated from internal resources.
The original doc that it should be linked to is too casual to be public.
Removing this line of sentence will reduce confusion to the public
readers.

Test
Reviewed the rendered content in MD viewer.
---
 architecture/design/ysql-colocated-tables.md | 2 --
 1 file changed, 2 deletions(-)

diff --git a/architecture/design/ysql-colocated-tables.md b/architecture/design/ysql-colocated-tables.md
index 351b8764b657..4cd9673eb7dc 100644
--- a/architecture/design/ysql-colocated-tables.md
+++ b/architecture/design/ysql-colocated-tables.md
@@ -137,8 +137,6 @@ Today, there is one RocksDB created per tablet. This RocksDB only has data for a
 1. Use single RocksDB for the entire tablet (i.e. for all tables).
 1. Use multiple RocksDBs with one RocksDB per table.
 
-More analysis on this can be found here.
-
 We decided to use single RocksDB for entire tablet. This is because:
 
 * It enables us to leverage code that was written for postgres system tables. Today, all postgres system tables are colocated on a single tablet in master and uses a single RocksDB. We can leverage a lot of that code.