From a8e85173642fa4a5652aa9a97069bd7611f98405 Mon Sep 17 00:00:00 2001 From: froggleston Date: Tue, 15 Oct 2024 00:11:16 +0100 Subject: [PATCH] Minor typo --- docs/freqtrade-101.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/freqtrade-101.md b/docs/freqtrade-101.md index 1cc035dc8..55e888fab 100644 --- a/docs/freqtrade-101.md +++ b/docs/freqtrade-101.md @@ -128,7 +128,7 @@ Therefore a strategy should be tested to verify that it is going to work as inte Freqtrade has two testing modes: - **backtesting**: using historical data that you [download from an exchange](data-download.md), backtesting is a quick way to assess performance of a strategy. However, it can be very easy to distort results so a strategy will look a lot more profitable than it really is. Check the [backtesting documentation](backtesting.md) for more information. -- **dry run**: often referred to as `forward testing`, dry runs use real time data from the exchange. However, any signals that would result in trades are tracked as normal by Freqtrade, but do not have any trades opened on the exchange itself. Forward testing runs in real time, so whilst it takes longer to get results it is a much more reliable indicator of **potential** performance then backtesting. +- **dry run**: often referred to as `forward testing`, dry runs use real time data from the exchange. However, any signals that would result in trades are tracked as normal by Freqtrade, but do not have any trades opened on the exchange itself. Forward testing runs in real time, so whilst it takes longer to get results it is a much more reliable indicator of **potential** performance than backtesting. Dry runs are enabled by setting `dry_run` to true in your [configuration](configuration.md#using-dry-run-mode).