Polish "Clarify conventions for custom error pages in WebFlux"

See gh-34534

spring-boot-project/spring-boot-docs/src/docs/asciidoc/web/reactive.adoc

@@ -141,10 +141,10 @@ include::code:MyExceptionHandlingController[]
 
 [[web.reactive.webflux.error-handling.error-pages]]
 ===== Custom Error Pages
-If you want to display a custom HTML error page for a given status code, you can add views that resolve from "error/*", for example by adding files to an `/error` directory.
+If you want to display a custom HTML error page for a given status code, you can add views that resolve from `error/*`, for example by adding files to a `/error` directory.
 Error pages can either be static HTML (that is, added under any of the static resource directories) or built with templates.
-The name of the file should be the exact status code or a series mask, or "error" for a fallback if nothing else matches.
+The name of the file should be the exact status code, a status code series mask, or `error` for a default if nothing else matches.
-Note the difference with MVC where "error" is the name of the default error `View`, whereas here it is "error/error".
+Note that the path to the default error view is `error/error`, whereas with Spring MVC the default error view is `error`.
 
 For example, to map `404` to a static HTML file, your directory structure would be as follows: