Editing pass

src/main/asciidoctor/index.adoc

@@ -1,5 +1,5 @@
 = Spring Web Services Reference Documentation
-Arjen Poutsma, Rick Evans, Tareq Abed Rabbo, Greg Turnquist
+Arjen Poutsma, Rick Evans, Tareq Abed Rabbo, Greg Turnquist, Jay Bryant
 :doctype: book
 :revnumber: {version}
 :revdate: {localdate}
@@ -8,7 +8,7 @@ Arjen Poutsma, Rick Evans, Tareq Abed Rabbo, Greg Turnquist
 :source-highlighter: prettify
 :sectnumlevels: 3
 
-(C) 2005-2017 The original authors.
+(C) 2005-2020 The original authors.
 
 NOTE: Copies of this document may be made for your own use and for distribution to others, provided that you do not charge any fee for such copies and further provided that each copy contains this Copyright Notice, whether distributed in print or electronically.
 
@@ -21,29 +21,34 @@ include::preface.adoc[leveloffset=+1]
 = I. Introduction
 :sectnums:
 
-This first part of the reference documentation <<what-is-spring-ws,is an overview>> of Spring Web Services and the underlying concepts. Spring-WS is then introduced, and <<why-contract-first,the concepts>> behind contract-first Web service development are explained.
+This first part of the reference documentation <<what-is-spring-ws,is an overview>> of Spring Web Services and the underlying concepts. Spring-WS is then introduced, and <<why-contract-first,the concepts>> behind contract-first web service development are explained.
 
 include::what-is-spring-ws.adoc[leveloffset=+1]
+
 include::why-contract-first.adoc[leveloffset=+1]
+
 include::tutorial.adoc[leveloffset=+1]
 
 :sectnums!:
 = II. Reference
 :sectnums:
 
-This part of the reference documentation details the various components that comprise Spring Web Services. This includes <<common,a chapter>> that discusses the parts common to both client- and server-side WS, a chapter devoted to the specifics of <<server,writing server-side Web services>>, a chapter about using Web services on <<client,the client-side>>, and a chapters on using <<security,WS-Security>>.
+This part of the reference documentation details the various components that comprise Spring Web Services. This includes <<common,a chapter>> that discusses the parts common to both client- and server-side WS, a chapter devoted to the specifics of <<server,writing server-side web services>>, a chapter about using web services on <<client,the client-side>>, and a chapter on using <<security,WS-Security>>.
 
 include::common.adoc[leveloffset=+1]
+
 include::server.adoc[leveloffset=+1]
+
 include::client.adoc[leveloffset=+1]
+
 include::security.adoc[leveloffset=+1]
 
 :sectnums!:
 [[resources]]
 = III. Other Resources
 :sectnums:
 
-In addition to this reference documentation, there exist a number of other resources that may help you learn how to use Spring Web Services. These additional, third-party resources are enumerated in this section.
+In addition to this reference documentation, a number of other resources may help you learn how to use Spring Web Services. These additional, third-party resources are enumerated in this section.
 
 :sectnums!:
 

src/main/asciidoctor/preface.adoc

@@ -2,7 +2,6 @@
 [[overview]]
 = Preface
 
-In the current age of Service Oriented Architectures, more and more people are using Web Services to connect previously unconnected systems. Initially, Web services were considered to be just another way to do a Remote Procedure Call (RPC). Over time however, people found out that there is a big difference between RPCs and Web services. Especially when interoperability with other platforms is important, it is often better to send encapsulated XML documents, containing all the data necessary to process the request. Conceptually, XML-based Web services are better off being compared to message queues rather than remoting solutions. Overall, XML should be considered the platform-neutral representation of data, the  *interlingua* of SOA. When developing or using Web services, the focus should be on this XML, and not on Java.
-
-Spring Web Services focuses on creating these document-driven Web services. Spring Web Services facilitates contract-first SOAP service development, allowing for the creation of flexible web services using one of the many ways to manipulate XML payloads. Spring-WS provides a powerful <<server,message dispatching framework>>, a <<security,WS-Security>> solution that integrates with your existing application security solution, and a <<client,Client-side API>> that follows the familiar Spring template pattern.
+In the current age of Service Oriented Architectures, more and more people use web services to connect previously unconnected systems. Initially, web services were considered to be just another way to do a Remote Procedure Call (RPC). Over time, however, people found out that there is a big difference between RPCs and web services. Especially when interoperability with other platforms is important, it is often better to send encapsulated XML documents that contain all the data necessary to process the request. Conceptually, XML-based web services are better compared to message queues than to remoting solutions. Overall, XML should be considered the platform-neutral representation of data, the _common language_ of SOA. When developing or using web services, the focus should be on this XML and not on Java.
 
+Spring Web Services focuses on creating these document-driven web services. Spring Web Services facilitates contract-first SOAP service development, allowing for the creation of flexible web services by using one of the many ways to manipulate XML payloads. Spring-WS provides a powerful <<server,message dispatching framework>>, a <<security,WS-Security>> solution that integrates with your existing application security solution, and a <<client,Client-side API>> that follows the familiar Spring template pattern.