diff --git a/docs/backtesting.md b/docs/backtesting.md
index f666c5b49..543422fee 100644
--- a/docs/backtesting.md
+++ b/docs/backtesting.md
@@ -3,7 +3,7 @@
 This page explains how to validate your strategy performance by using
 Backtesting.
 
-## Getting data for backtesting / hyperopt
+## Getting data for backtesting and hyperopt
 
 To download backtesting data (candles / OHLCV), we recommend using the `freqtrade download-data` command.
 
diff --git a/docs/bot-usage.md b/docs/bot-usage.md
index 31c5812ad..2873f5e8f 100644
--- a/docs/bot-usage.md
+++ b/docs/bot-usage.md
@@ -184,19 +184,11 @@ optional arguments:
                         result.json)
 ```
 
-### How to use **--refresh-pairs-cached** parameter?
+### Getting historic data for backtesting
 
-The first time your run Backtesting, it will take the pairs you have
-set in your config file and download data from the Exchange.
-
-If for any reason you want to update your data set, you use
-`--refresh-pairs-cached` to force Backtesting to update the data it has.
-
-!!! Note
-    Use it only if you want to update your data set. You will not be able to come back to the previous version.
-
-To test your strategy with latest data, we recommend continuing using
-the parameter `-l` or `--live`.
+The first time your run Backtesting, you will need to download some historic data first.
+This can be accomplished by using `freqtrade download-data`.  
+Check the corresponding [help page section](backtesting.md#Getting-data-for-backtesting-and-hyperopt) for more details
 
 ## Hyperopt commands