From f365e68706099acbb4b83b87d06f8182bf84ebb1 Mon Sep 17 00:00:00 2001
From: Theagainmen <24569139+Theagainmen@users.noreply.github.com>
Date: Mon, 1 Nov 2021 23:07:16 +0100
Subject: [PATCH] [docs] Update RateLimit value [small]

## Summary
Fix very small mistake in docs, that might confuse people. Let me know if this is the correct value now, there is still another 3100 in there, which I think makes sense there and is correct.

## Quick changelog
Changed the `rateLimit` 3100 value to 200, to match the 200ms and thus 0.2s delay.
---
 docs/exchanges.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/exchanges.md b/docs/exchanges.md
index badaa484a..d00c88d8e 100644
--- a/docs/exchanges.md
+++ b/docs/exchanges.md
@@ -41,12 +41,12 @@ In case of problems related to rate-limits (usually DDOS Exceptions in your logs
     "ccxt_config": {"enableRateLimit": true},
     "ccxt_async_config": {
         "enableRateLimit": true,
-        "rateLimit": 3100
+        "rateLimit": 200
     },
 ```
 
 This configuration enables kraken, as well as rate-limiting to avoid bans from the exchange.
-`"rateLimit": 3100` defines a wait-event of 0.2s between each call. This can also be completely disabled by setting `"enableRateLimit"` to false.
+`"rateLimit": 200` defines a wait-event of 0.2s between each call. This can also be completely disabled by setting `"enableRateLimit"` to false.
 
 !!! Note
     Optimal settings for rate-limiting depend on the exchange and the size of the whitelist, so an ideal parameter will vary on many other settings.