DOCS-13533-maxValidateMemoryUsageMB-update (#1902) (#1911)

jason-price-mongodb · jason-price-mongodb · web-flow · commit aa0aa56f970e · 2022-09-28T11:36:35.000-07:00
Co-authored-by: jason-price-mongodb &lt;jshfjghsdfgjsdjh@aolsdjfhkjsdhfkjsdf.com&gt;

Co-authored-by: jason-price-mongodb &lt;jshfjghsdfgjsdjh@aolsdjfhkjsdhfkjsdf.com&gt;
diff --git a/source/reference/parameters.txt b/source/reference/parameters.txt
@@ -393,7 +393,7 @@ Authentication Parameters
 
 .. parameter:: maxValidateMemoryUsageMB
 
-   .. versionadded:: 5.0
+   *New in version 5.0 and 4.4.7*
 
    *Default*: 200
 
diff --git a/source/release-notes/5.0.txt b/source/release-notes/5.0.txt
@@ -1063,9 +1063,9 @@ Starting in MongoDB 5.0, the :dbcommand:`validate` command and
 ``maxValidateMemoryUsageMB`` Server Parameter
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Starting in MongoDB 5.0, the :dbcommand:`setParameter` command has a new
-:parameter:`maxValidateMemoryUsageMB` parameter, which sets the maximum
-memory usage for the :dbcommand:`validate` command.
+Starting in MongoDB 5.0 (and 4.4.7), the :dbcommand:`setParameter`
+command has a new :parameter:`maxValidateMemoryUsageMB` parameter, which
+sets the maximum memory usage for the :dbcommand:`validate` command.
 
 ``findChunksOnConfigTimeoutMS`` Server Parameter
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
