X-Git-Url: https://git.immae.eu/?a=blobdiff_plain;f=support%2Fdoc%2Fredundancy.md;h=00442fd8515ce1a2a96752dac3226ee8c4e4e5b5;hb=bb5d90e62f631af3c899fbe586485e64938a5927;hp=62c6365a99ceff52b5b8f49abea401414a7feb1c;hpb=e5565833f62b97f62ea75eba5b479963ae78b873;p=github%2FChocobozzz%2FPeerTube.git

diff --git a/support/doc/redundancy.md b/support/doc/redundancy.md
index 62c6365a9..00442fd85 100644
--- a/support/doc/redundancy.md
+++ b/support/doc/redundancy.md
@@ -7,6 +7,12 @@ A PeerTube instance can cache other PeerTube videos to improve bandwidth of popu
 The instance administrator can choose between multiple redundancy strategies (cache trending videos or recently uploaded videos etc), set their maximum size and the minimum duplication lifetime.
 Then, they choose the instances they want to cache in `Manage follows -> Following` admin table.
 
+<p align="center">
+
+<img src="user/redundancy.png" alt="Redundancy" />
+
+</p>
+
 Videos are kept in the cache for at least `min_lifetime`, and then evicted when the cache is full.
 
 When PeerTube chooses a video to duplicate, it imports all the resolution files (to avoid consistency issues) using their magnet URI and put them in the `storage.videos` directory.
@@ -43,4 +49,4 @@ See the `/api/v1/server/stats` endpoint. For example:
     }
   ]
 }
-```
\ No newline at end of file
+```