From efbaf327906e2420f33bd8136e1927d927a5cb65 Mon Sep 17 00:00:00 2001
From: crcarreras <139771860+crcarreras@users.noreply.github.com>
Date: Wed, 28 Feb 2024 13:23:58 -0500
Subject: [PATCH] Update choosing-an-engine.md

Removed a line referencing join indexes, which are no longer supported.
---
 docs/Overview/choosing-an-engine.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/Overview/choosing-an-engine.md b/docs/Overview/choosing-an-engine.md
index 56016131..2c8f6f28 100644
--- a/docs/Overview/choosing-an-engine.md
+++ b/docs/Overview/choosing-an-engine.md
@@ -74,7 +74,7 @@ Queries that perform complex aggregations and multiple joins are likely to place
 
 #### Queries with joins benefit from increased RAM
 
-Queries joining multiple tables can be memory intensive, with large data sets cached in RAM during join operations. Try increasing the engine specification with more RAM per node. Aim for the memory of each node to be enough to contain all the join indexes fully in memory. Next, add nodes for additional RAM when running large and complex joins.
+Queries joining multiple tables can be memory intensive, with large data sets cached in RAM during join operations. Try increasing the engine specification with more RAM per node. Next, add nodes for additional RAM when running large and complex joins.
 
 #### Aggregation queries benefit from increased CPU