edits as per @rob-metalinkage's comment

conneg-by-ap/index.html

@@ -10,7 +10,7 @@
   <section id="abstract">
     <h2>Abstract</h2>
     <p>
-      This document describes how Internet clients may negotiate for content provided by servers based on the 
+      This document describes how Internet clients may negotiate for content provided by servers based on the
 +     <em>profile</em> to which the content conforms. This is distinct from negotiating by Media Type or Language: a <em>profile</em> may
       specify the content of information returned, which may be a subset of the information the responding server has about the requested resource, and may be structured in a specific way to meet interoperability requirements of a community of practice.
     </p>
@@ -55,10 +55,10 @@ <h2>Introduction</h2>
       For example, a catalog may offer choices of representations of a dataset's description that conform to different information models, perhaps [[VOID]],
       [[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 further constrain various elements of the dataset's description beyond the more general specification or profile of which they are a profile.
-+      A request for information about possible representations of this dataset's description may
-+      ask for the list of conformant profiles that are available for the dataset, or may ask specifically for a representation conforming to one specific profile, for example
-+      [[GeoDCAT-AP]]. When no profile or an unsupported profile is requested, a server returns default content conforming to the default profile supported by the server.
+      These narrower profiles further constrain various elements of the dataset's description beyond the more general specification of which they are a profile.
+      A request for information about possible representations of this dataset's description may
+      ask for the list of available profiles that are available for the dataset, or may ask specifically for a representation conforming to one specific profile, for example
+      [[GeoDCAT-AP]]. When no profile or an unsupported profile is requested, a server returns default content conforming to the default profile supported by the server.
     </p>
     <p>
       When selecting a content negotiation mechanism, an Internet client may use the HTTP protocol, but it may also use
@@ -102,7 +102,7 @@ <h2>Introduction</h2>
       <a href="#functional-profiles">Section 7</a> and
       <a href="#testsuites">Section 8</a>.
     </p>
-    <p class="note">Specifications and Profiles to which the content of resource representations may conform will embody their own definitions of conformance, which are out of scope for this specification.</p>
+    <p class="note">Specifications and Profiles to which the content of resource representations may conform will embody their own notions of conformance, which are out of scope for this specification.</p>
   </section>
   <section id="definitions">
     <h2>Definitions</h2>
@@ -795,7 +795,7 @@ <h3>Conformance to Functional Profiles</h3>
       <p>
         If a system wishes to show conformance to this specification, conformance to at least one functional profile of
         it, such as those listed <a href="#fig-table-profiles"></a> MUST be indicated. <a href="#fig-table-profiles"></a>
-        is not an exhaustive list of functional profiles of this specification and users MAY instead make other or additional 
+        is not an exhaustive list of functional profiles of this specification and users MAY instead make other or additional
         functional profiles for their environments, as described in the previous section.
       </p>
       <p>
@@ -1262,7 +1262,7 @@ <h4>QSA Functional Profile description</h4>
         <div class="note">
           Conformance of a system to any one, or perhaps multiple, of these functional profiles may be demonstrated as per
           <a href="#conformancetoprofiles"></a>. Note that it is not required that a system, perhaps a server, indicate
-          conformance to one or more of the functional profiles described in this specification since not all systems will 
+          conformance to one or more of the functional profiles described in this specification since not all systems will
           do so. Systems may also show conformance to
           functional profiles in multiple ways, such as with annotated entries in a services catalogue.
         </div>