More edits to conneg-by-p document

conneg-by-ap/index.html

@@ -60,20 +60,19 @@ <h1>Introduction</h1>
       Dublin Core Terms profile. When a non-existent or unsupported profile is requested, a server returns default content.
     </p>
     <p>
-      When selecting content negotiation mechanics, an Internet client may use the HTTP protocol but it may also use
+      When selecting a content negotiation mechanism, an Internet client may use the HTTP protocol but it may also use
       other methods for providing instructions to a server, such as URI Query String Arguments (QSAs). QSAs are long
-      established as useful for humans and machines and in situations where negotiation via HTTP is not practical, such
-      as when manually entering requests into web browsers. This document also provides guidance for non-HTTP methods
-      of content negotiation and ensures they and the HTTP methods all adhere to a single functional specification
-      which thus ensures their functional equivalency.
+      established as useful for humans and machines for situations where negotiation via HTTP is not practical, such
+      as when manually entering requests into web browsers. This document also provides guidance for both HTTP and non-HTTP methods
+      of content negotiation and ensures they all adhere to a single functional specification, and thus their functional equivalency.
     </p>
     <section id="compliance">
       <h3>Compliance with this Document</h3>
       <p>
         For the purpose of compliance, the normative sections of this document are
         <a href="#definitions">Section 2</a>,
         <a href="#abstractmodel">Section 5</a>,
-        <a href="#realisations">Section 6</a>,
+        <a href="#realisations">Section 6</a>, and
         <a href="#testsuites">Section 7</a>.
       </p>
     </section>
@@ -147,19 +146,19 @@ <h2>Motivation</h2>
     <p>
       In many cases, there are several ways to describe a resource within the scope of a single Media Type.
       For instance, XML documents, while conforming to the <code>text/xml</code> Media Type, may adhere to one of
-      several DTDs or XML Schemas. RDF documents, with a choice of Media Type serialisations such as
+      several DTDs or XML Schemas. RDF documents, with a choice of Media Type serializations such as
       <code>text/turtle</code>, <code>application/rdf+xml</code> and others, have a very large number of vocabularies
-      (classes and properties) available use for their content's information model. When a client initiates a request
-      for an Internet resource, e.g., an HTTP GET to retrieve or a PUT to create or replace a resource, neither the
-      client nor the server have yet had any standardised way to exchange information on how the transmitted resource
+      (classes and properties) available to use for their content's information model. When a client initiates a request
+      for an Internet resource, e.g., an HTTP GET to retrieve a resource or an HTTP PUT to create or replace a resource, neither the
+      client nor the server have yet had any standardized way to exchange information on how the transmitted resource
       will be structured precisely according to DTDs, XML Schema, vocabularies or other standards, specifications or
-      <em>profiles</em>. When using non-HTTP content negotiation other methods, such as URIs with Query String
-      Arguments, no universal or standardised method for doing this has been established although there are multiple
+      <em>profiles</em>. When using non-HTTP content negotiation, other methods, such as URIs with Query String
+      Arguments, no universal or standardized method for doing this has been established although there are multiple
       specific ways this has been implemented previously, such as the OAI-PMH protocol [[OAI-PMH]].
     </p>
     <p>
       This document describes content negotiation based on profiles using HTTP protocol by introducing new headers and
-      non-HTTP methods, such as via QSAs by introducing a general QSA Application Programming Interface (API).
+      non-HTTP methods, such as via QSAs, by introducing a general QSA Application Programming Interface (API).
     </p>
     <div class="issue" data-number="379"></div>
   </section>