From e80d893e69fa6698857d694826589cddcf5eb451 Mon Sep 17 00:00:00 2001
From: Lea <12768489+lemora@users.noreply.github.com>
Date: Fri, 6 Oct 2023 12:21:50 +0200
Subject: [PATCH] book: pinmananger, describe new default unpins/time

---
 docs/TheBook/src/main/markdown/config-pinmanager.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/TheBook/src/main/markdown/config-pinmanager.md b/docs/TheBook/src/main/markdown/config-pinmanager.md
index 3abc985a7fd..6bacc2b4536 100644
--- a/docs/TheBook/src/main/markdown/config-pinmanager.md
+++ b/docs/TheBook/src/main/markdown/config-pinmanager.md
@@ -32,10 +32,10 @@ state `PINNED` once the attempt is successful.
 
 When a pin either has a finite lifetime that has expired or is directly requested to be removed, it
 is put into state `READY_TO_UNPIN`. An 'unpinning' background task runs regularly (default every
-minute), which directly removes all pins in state `READY_TO_UNPIN` that don't require pool contact,
-then selects a certain number of pins (default 200) in state `READY_TO_UNPIN` for which the
-corresponding pool needs to be contacted and attempts to remove them as well. During unpinning the
-pins are in state `UNPINNING`.
+minute), which directly removes all pins in state `READY_TO_UNPIN` that don't require pool contact
+(regular pin expiry), then selects a certain number of pins (default 2000) in state `READY_TO_UNPIN`
+for which the corresponding pool needs to be contacted (manually triggered, premature expiry) and
+attempts to remove them as well. During unpinning the pins are in state `UNPINNING`.
 
 On success, the pin is deleted from the pool in question as well as the database, on failure the pin
 is put into state `FAILED_TO_UNPIN`. Another background process regularly (default every 2h) resets