diff --git a/framework-docs/modules/ROOT/pages/web/webmvc/mvc-ann-rest-exceptions.adoc b/framework-docs/modules/ROOT/pages/web/webmvc/mvc-ann-rest-exceptions.adoc
index 66bfbc0e76..5dc7aac21d 100644
--- a/framework-docs/modules/ROOT/pages/web/webmvc/mvc-ann-rest-exceptions.adoc
+++ b/framework-docs/modules/ROOT/pages/web/webmvc/mvc-ann-rest-exceptions.adoc
@@ -74,14 +74,13 @@ It is a common requirement to customize and internationalize error response deta
 It is also good practice to customize the problem details for Spring MVC exceptions
 to avoid revealing implementation details. This section describes the support for that.
 
-An `ErrorResponse` exposes message codes for "type", "title", and "detail", as well as
-message code arguments for the "detail" field. `ResponseEntityExceptionHandler` resolves
+An `ErrorResponse` exposes message codes for "type" and "title". `ResponseEntityExceptionHandler` resolves
 these through a xref:core/beans/context-introduction.adoc#context-functionality-messagesource[MessageSource]
 and updates the corresponding `ProblemDetail` fields accordingly.
 
 The default strategy for message codes follows the pattern:
 
-`problemDetail.[type|title|detail].[fully qualified exception class name]`
+`problemDetail.[type|title].[fully qualified exception class name]`
 
 An `ErrorResponse` may expose more than one message code, typically adding a suffix
 to the default message code. The table below lists message codes, and arguments for