Intro wording updates

conneg-by-ap/index.html

@@ -56,8 +56,8 @@ <h2>Introduction</h2>
       [[VOCAB-DATA-CUBE]] and [[VOCAB-DCAT]]. Furthermore, the [[VOCAB-DCAT]] representation might conform to the
       [[DCAT-AP]] profile, the [[GeoDCAT-AP]] profile and perhaps also an organisation-specific profile "MyOrgDCATProfile".
       These "narrower" profiles constrains various elements of the dataset's description above and beyond the "broader", more general, specification or profile that they profile.
-      A request for information about this dataset description's possible forms may
-      ask for the list of the profiles to representations of it are available, or may ask specifically for a representation adhering to one profile, for example
+      A request for information about this dataset description's possible representations may
+      ask for the list of profiles to which conformant representations of it are available, or may ask specifically for a representation conforming to one profile, for example
       [[GeoDCAT-AP]]. When no profile or an unsupported profile is requested, a server returns default content,
       that is, content conforming to the default profile supported by the server.
     </p>
@@ -66,13 +66,13 @@ <h2>Introduction</h2>
       other methods for providing instructions to a server. One of potentially many mechanisms is URI Query String
       Arguments (<abbr title="Query String Arguments">QSAs</abbr>). QSAs are
       useful for humans and machines for situations where negotiation via HTTP is not practical, such
-      as when manually entering requests into web browsers. This specification provides guidance for both HTTP and non-HTTP methods
-      of content negotiation and ensures they all adhere to a single functional specification, ensuring their functional equivalency.
+      as when manually entering requests into web browsers. This specification provides an abstract model
+      of content negotiation by profile and presents guidance on the use of two specific methods, HTTP &amp; QSA, that both conform to the abstract model meaning they are.
     </p>
     <p>
       While this specification only describes HTTP and QSA methods for content negotiation by profile, it is expected
       that implementers will want to implement functionally equivalent methods for other environments, some of which may
-      not yet be realized; future environments.
+      not yet be realized; future environments. Implementers may add additional functions/features to their implementations for other environments as long as they ensure their implementation conforms to this specification's abstract model, as the HTTP and QSA methods do.
     </p>
     <!--
     <p>