diff --git a/conf/web.xml b/conf/web.xml
index 08a32c2dcafc..9c95b04d03a9 100644
--- a/conf/web.xml
+++ b/conf/web.xml
@@ -114,11 +114,11 @@
   <!--                       listings is enabled? [true]                    -->
   <!--                                                                      -->
   <!--   allowPartialPut     Should the server treat an HTTP PUT request    -->
-  <!--                       with a Range header as a partial PUT? Note     -->
-  <!--                       that while RFC 7233 clarified that Range       -->
-  <!--                       headers only valid for GET requests, RFC 9110  -->
-  <!--                       (which obsoletes RFC 7233) now allows partial  -->
-  <!--                       puts. [true]                                   -->
+  <!--                       with a Content-Range header as a partial PUT?  -->
+  <!--                       Note that while RFC 7231 clarified that such a -->
+  <!--                       PUT with a Content-Range header field is a bad -->
+  <!--                       request, RFC 9110 (which obsoletes RFC 7231)   -->
+  <!--                       now allows partial PUT. [true]                 -->
   <!--                                                                      -->
   <!--   directoryRedirectStatusCode                                        -->
   <!--                       Status code to use for directory redirects.    -->
diff --git a/webapps/docs/default-servlet.xml b/webapps/docs/default-servlet.xml
index 8b906081c9bb..8616351af629 100644
--- a/webapps/docs/default-servlet.xml
+++ b/webapps/docs/default-servlet.xml
@@ -209,10 +209,10 @@ Tomcat.</p>
         Should the server list all directories before all files. [false]
   </property>
   <property name="allowPartialPut">
-        Should the server treat an HTTP PUT request with a Range header as a
-        partial PUT? Note that while RFC 7233 clarified that Range headers only
-        valid for GET requests, RFC 9110 (which obsoletes RFC 7233) now allows
-        partial puts. [true]
+        Should the server treat an HTTP PUT request with a Content-Range header
+        as a partial PUT? Note that while RFC 7231 clarified that such a PUT
+        with a Content-Range header field is a bad request, RFC 9110
+        (which obsoletes RFC 7231) now allows partial PUT. [true]
   </property>
   <property name="directoryRedirectStatusCode">
         When a directory redirect (trailing slash missing) is made, use this as