From 676dd0d664e9ee59f2008b518eb12795e3fe9d85 Mon Sep 17 00:00:00 2001
From: Matthias <xmatthias@outlook.com>
Date: Sun, 20 Dec 2020 11:22:15 +0100
Subject: [PATCH] Improve documentation

---
 docs/stoploss.md          | 1 +
 docs/strategy-advanced.md | 2 ++
 2 files changed, 3 insertions(+)

diff --git a/docs/stoploss.md b/docs/stoploss.md
index 1e21fc50d..671e643b0 100644
--- a/docs/stoploss.md
+++ b/docs/stoploss.md
@@ -78,6 +78,7 @@ At this stage the bot contains the following stoploss support modes:
 2. Trailing stop loss.
 3. Trailing stop loss, custom positive loss.
 4. Trailing stop loss only once the trade has reached a certain offset.
+5. [Custom stoploss function](strategy-advanced.md#custom-stoploss)
 
 ### Static Stop Loss
 
diff --git a/docs/strategy-advanced.md b/docs/strategy-advanced.md
index bb455ff9f..4833fbade 100644
--- a/docs/strategy-advanced.md
+++ b/docs/strategy-advanced.md
@@ -29,6 +29,8 @@ E.g. `current_profit = 0.05` (5% profit) - stoploss returns `0.02` - then you "l
         return 0.04
 ```
 
+Stoploss on exchange works similar to trailing_stop, and the stoploss on exchange is updated as configured in `stoploss_on_exchange_interval` ([More details about stoploss on exchange](stoploss.md#stop-loss-on-exchange-freqtrade)).
+
 !!! Note "Use of dates"
     All time-based calculations should be done based on `current_time` - using `datetime.now()` or `datetime.utcnow()` is discouraged, as this will break backtesting support.