--- a/xml/en/docs/http/ngx_http_scgi_module.xml	Wed Feb 14 20:05:46 2024 +0300
+++ b/xml/en/docs/http/ngx_http_scgi_module.xml	Wed Feb 14 20:05:49 2024 +0300
@@ -10,7 +10,7 @@
 <module name="Module ngx_http_scgi_module"
         link="/en/docs/http/ngx_http_scgi_module.html"
         lang="en"
-        rev="41">
+        rev="42">
 
 <section id="summary">
 
@@ -383,11 +383,7 @@
     [<literal>manager_threshold</literal>=<value>time</value>]
     [<literal>loader_files</literal>=<value>number</value>]
     [<literal>loader_sleep</literal>=<value>time</value>]
-    [<literal>loader_threshold</literal>=<value>time</value>]
-    [<literal>purger</literal>=<literal>on</literal>|<literal>off</literal>]
-    [<literal>purger_files</literal>=<value>number</value>]
-    [<literal>purger_sleep</literal>=<value>time</value>]
-    [<literal>purger_threshold</literal>=<value>time</value>]</syntax>
+    [<literal>loader_threshold</literal>=<value>time</value>]</syntax>
 <default/>
 <context>http</context>
 
@@ -433,15 +429,6 @@
 in a shared memory zone, whose <value>name</value> and <value>size</value>
 are configured by the <literal>keys_zone</literal> parameter.
 One megabyte zone can store about 8 thousand keys.
-<note>
-As part of
-<commercial_version>commercial subscription</commercial_version>,
-the shared memory zone also stores extended
-cache <link doc="ngx_http_api_module.xml" id="http_caches_">information</link>,
-thus, it is required to specify a larger zone size for the same number of keys.
-For example,
-one megabyte zone can store about 4 thousand keys.
-</note>
 </para>
 
 <para>
@@ -485,56 +472,6 @@
 </para>
 
 <para>
-Additionally,
-the following parameters are available as part of our
-<commercial_version>commercial subscription</commercial_version>:
-</para>
-
-<para>
-<list type="tag">
-
-<tag-name id="purger">
-<literal>purger</literal>=<literal>on</literal>|<literal>off</literal>
-</tag-name>
-<tag-desc>
-Instructs whether cache entries that match a
-<link id="scgi_cache_purge">wildcard key</link>
-will be removed from the disk by the cache purger (1.7.12).
-Setting the parameter to <literal>on</literal>
-(default is <literal>off</literal>)
-will activate the “cache purger” process that
-permanently iterates through all cache entries
-and deletes the entries that match the wildcard key.
-</tag-desc>
-
-<tag-name id="purger_files">
-<literal>purger_files</literal>=<value>number</value>
-</tag-name>
-<tag-desc>
-Sets the number of items that will be scanned during one iteration (1.7.12).
-By default, <literal>purger_files</literal> is set to 10.
-</tag-desc>
-
-<tag-name id="purger_threshold">
-<literal>purger_threshold</literal>=<value>number</value>
-</tag-name>
-<tag-desc>
-Sets the duration of one iteration (1.7.12).
-By default, <literal>purger_threshold</literal> is set to 50 milliseconds.
-</tag-desc>
-
-<tag-name id="purger_sleep">
-<literal>purger_sleep</literal>=<value>number</value>
-</tag-name>
-<tag-desc>
-Sets a pause between iterations (1.7.12).
-By default, <literal>purger_sleep</literal> is set to 50 milliseconds.
-</tag-desc>
-
-</list>
-</para>
-
-<para>
 <note>
 In versions 1.7.3, 1.7.7, and 1.11.10 cache header format has been changed.
 Previously cached responses will be considered invalid
@@ -545,63 +482,6 @@
 </directive>
 
 
-<directive name="scgi_cache_purge">
-<syntax>string ...</syntax>
-<default/>
-<context>http</context>
-<context>server</context>
-<context>location</context>
-<appeared-in>1.5.7</appeared-in>
-
-<para>
-Defines conditions under which the request will be considered a cache
-purge request.
-If at least one value of the string parameters is not empty and is not equal
-to “0” then the cache entry with a corresponding
-<link id="scgi_cache_key">cache key</link> is removed.
-The result of successful operation is indicated by returning
-the <http-status code="204" text="No Content"/> response.
-</para>
-
-<para>
-If the <link id="scgi_cache_key">cache key</link> of a purge request ends
-with an asterisk (“<literal>*</literal>”), all cache entries matching the
-wildcard key will be removed from the cache.
-However, these entries will remain on the disk until they are deleted
-for either <link id="scgi_cache_path">inactivity</link>,
-or processed by the <link id="purger">cache purger</link> (1.7.12),
-or a client attempts to access them.
-</para>
-
-<para>
-Example configuration:
-<example>
-scgi_cache_path /data/nginx/cache keys_zone=cache_zone:10m;
-
-map $request_method $purge_method {
-    PURGE   1;
-    default 0;
-}
-
-server {
-    ...
-    location / {
-        scgi_pass        backend;
-        scgi_cache       cache_zone;
-        scgi_cache_key   $uri;
-        scgi_cache_purge $purge_method;
-    }
-}
-</example>
-<note>
-This functionality is available as part of our
-<commercial_version>commercial subscription</commercial_version>.
-</note>
-</para>
-
-</directive>
-
-
 <directive name="scgi_cache_revalidate">
 <syntax><literal>on</literal> | <literal>off</literal></syntax>
 <default>off</default>