The servlet and all filters involved in an async request must have async
* support enabled using the Servlet API or by adding an
- * {@code true} element to servlet and filter
+ * {@code true} element to servlet and filter
* declarations in {@code web.xml}.
*
* @author Rossen Stoyanchev
diff --git a/src/asciidoc/web-mvc.adoc b/src/asciidoc/web-mvc.adoc
index 2b42dcfca1..02c2143154 100644
--- a/src/asciidoc/web-mvc.adoc
+++ b/src/asciidoc/web-mvc.adoc
@@ -2541,7 +2541,7 @@ For applications configured with a `web.xml` be sure to update to version 3.0:
----
Asynchronous support must be enabled on the `DispatcherServlet` through the
-`true` web.xml sub-element. Additionally
+`true` sub-element in `web.xml`. Additionally
any `Filter` that participates in asyncrequest processing must be configured
to support the ASYNC dispatcher type. It should be safe to enable the ASYNC
dispatcher type for all filters provided with the Spring Framework since they
@@ -2703,7 +2703,7 @@ the example below:
-
+
----
[source,java,indent=0]
@@ -3331,7 +3331,7 @@ Spring MVC also provides a mechanism for building links to controller methods. F
public String getBooking(@PathVariable Long booking) {
// ...
-
+ }
}
----
@@ -3502,7 +3502,7 @@ maximum age. Find below an example of defining a `CookieLocaleResolver`.
-
+
----
diff --git a/src/asciidoc/web-view.adoc b/src/asciidoc/web-view.adoc
index e1e27134c0..a52bb9352c 100644
--- a/src/asciidoc/web-view.adoc
+++ b/src/asciidoc/web-view.adoc
@@ -1255,6 +1255,7 @@ The HTML would look like:
+
----