From 2921b0ead05342c0d1578b50ef84c01d876f0444 Mon Sep 17 00:00:00 2001
From: Skillz4Killz <23035000+Skillz4Killz@users.noreply.github.com>
Date: Wed, 30 Mar 2022 22:59:51 +0000
Subject: [PATCH] fix: update docs on spawnShardDelay

---
 site/docs/big-bot-guide/gateway.md | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/site/docs/big-bot-guide/gateway.md b/site/docs/big-bot-guide/gateway.md
index a3e8693e4..84bafb68d 100644
--- a/site/docs/big-bot-guide/gateway.md
+++ b/site/docs/big-bot-guide/gateway.md
@@ -166,8 +166,7 @@ If your bot is going to be run on one process, you can re-use the data that disc
 - `reshard`: Whether or not to automatically reshard the bot when necessary with zero downtime deployment strategy.
   Default: true.
 - `reshardPercentage`: The % of servers to trigger a reshard. Default: 80%.
-- `spawnShardDelay`: The delay in milliseconds to wait before spawning next shard. OPTIMAL IS ABOVE 2500. YOU DON"T WANT
-  TO HIT THE RATE LIMIT!!! This is mainly if you are changing internals a lot and need to modify this behavior.
+- `spawnShardDelay`: The delay in milliseconds to wait before spawning next shard.
 - `useOptimalLargeBotSharding`: Whether or not the resharder should automatically switch to LARGE BOT SHARDING when you
   are above 100K servers.
 - `shardsPerCluster`: The amount of shards to load per worker. Discussed in detail below.