diff --git a/src/asciidoc/web-mvc.adoc b/src/asciidoc/web-mvc.adoc index a08426d3a7..de8db0851e 100644 --- a/src/asciidoc/web-mvc.adoc +++ b/src/asciidoc/web-mvc.adoc @@ -37,7 +37,7 @@ add advice to final methods. In Spring Web MVC you can use any object as a command or form-backing object; you do not need to implement a framework-specific interface or base class. Spring's data binding is highly flexible: for example, it treats type mismatches as validation errors that can be -evaluated by the application, not as system errors. Thus you need not duplicate your +evaluated by the application, not as system errors. Thus you do not need to duplicate your business objects' properties as simple, untyped strings in your form objects simply to handle invalid submissions, or to convert the Strings properly. Instead, it is often preferable to bind directly to your business objects. diff --git a/src/asciidoc/web.adoc b/src/asciidoc/web.adoc index debdaa66f5..e6388258e7 100644 --- a/src/asciidoc/web.adoc +++ b/src/asciidoc/web.adoc @@ -9,7 +9,7 @@ for WebSocket-style messaging in web applications. Spring Framework's own web framework, <>, is covered in the first couple of chapters. Subsequent chapters are concerned with Spring Framework's -integration with other web technologies, such as <> and. +integration with other web technologies, such as <>. Following that is coverage of Spring Framework's MVC <>.