--- a/Sphinx/source/faq/features.rst	Mon Dec 11 14:24:59 2023 +0100
+++ b/Sphinx/source/faq/features.rst	Mon Dec 18 09:47:49 2023 +0100
@@ -33,7 +33,7 @@
 Recycling/Protection
 --------------------
 
-Because of its focus on low-end computers, Orthanc implements **disk
+Because of its focus on low-end computers, Orthanc may implement **disk
 space recycling**: The patient that has been stored for the longest
 time inside Orthanc can be automatically deleted when the disk space
 used by Orthanc grows above a threshold, or when the number of stored
@@ -47,6 +47,12 @@
 file <configuration>`.  Setting both these values to 0 will disable 
 recycling.
 
+Starting with version 1.11.2, Orthanc also implements another **rejection**
+behaviour when the ``MaximumStorageSize`` or ``MaximumPatientCount`` is 
+reached.  In this case, patients are not recycled but Orthanc rejects new incoming
+data.  Check the ``MaximumStorageMode`` option in the :ref:`Orthanc configuration
+file <configuration>`.
+
 It is possible to prevent important data from being automatically
 recycled. This mechanism is called **protection**. Each patient can be
 individually protected against recycling by using the
@@ -60,11 +66,11 @@
 study/series that is part of the same patient might lead to a loss in
 consistency with respect to the medical history of this patient.
 
-Starting with version 1.11.2, Orthanc also implements another **rejection**
-behaviour when the ``MaximumStorageSize`` or ``MaximumPatientCount`` is 
-reached.  In this case, patients are not recycled but Orthanc rejects new incoming
-data.  Check the ``MaximumStorageMode`` option in the :ref:`Orthanc configuration
-file <configuration>`.
+To protect/unprotect a patient, one must call the ``/patients/../protected`` route:: 
+
+$ curl -X PUT http://localhost:8042/patients/0946fcb6-cf12ab43-bad958c1-bf057ad5-0fc6f54c/protected -d "1"
+$ curl -X PUT http://localhost:8042/patients/0946fcb6-cf12ab43-bad958c1-bf057ad5-0fc6f54c/protected -d "0"
+
 
 .. _compression: