[Osr-101] rev 16656 - public/osr-101/trunk

[thomas at wyona.com]

Author: thomas
Date: 2006-08-16 18:36:03 +0200 (Wed, 16 Aug 2006)
New Revision: 16656

Modified:
   public/osr-101/trunk/osr-101.xhtml
Log:
Reformulated a bit.


Modified: public/osr-101/trunk/osr-101.xhtml
===================================================================
--- public/osr-101/trunk/osr-101.xhtml	2006-08-16 16:33:20 UTC (rev 16655)
+++ public/osr-101/trunk/osr-101.xhtml	2006-08-16 16:36:03 UTC (rev 16656)
@@ -79,10 +79,10 @@
 Neutron is typically used over HTTP. However, any other transport protocol can be used to establish a Neutron request/response chain or to retrieve Neutron configuration directives.
 </p>
 <p>
-CMS vendors usually implement their own frontend components for the operations listed above and/or implement a public API for third party component integration. Neutron is ment to be a standard that leverages  integration and reuse of third party components such as editing applications or standalone clients targeted at offline operation into existing content management systems.  
+CMS vendors usually implement their own frontend components for the operations listed above and/or implement a public API for third party component integration. Neutron is ment to be a standard that leverages  integration and reuse of third party components such as editing applications or standalone clients targeted at offline operation into existing content management solutions.  
 </p>
 <p>
-Neutron focuses on xml-based systems by providing a comprehensive set of instructions for dealing with xml-based resources. However, usage of xml-based resources is not required. Neutron also covers transactions of binary or whatever formatted data while being extensible enough for integrators to deal with data formats of their choice. 
+Neutron focuses on xml-based systems by providing a comprehensive set of instructions for dealing with xml-based resources. However, usage of xml-based resources is not required. Neutron also covers transactions of binary or whatever formatted data while being extensible enough for integrators to deal with the data formats of their choice. 
 </p>
 <p>
 For examples and usage patterns see Appendix I (Examples).