small into wording change for FP naming consistency

connegp/index.html

@@ -69,7 +69,7 @@ <h2>Introduction</h2>
       of content negotiation by profile and presents guidance on the use of two specific methods that conform to the abstract model, HTTP and QSA.
     </p>
     <p>
-       The HTTP and QSA methods are defined as <em>Functional Profiles</em> of the Abstract Model.
+       The HTTP Header and URL QSA methods are defined as <em>Functional Profiles</em> of the Abstract Model.
       While this specification only describes these two Functional Profiles, it is expected
       that implementers will want to implement Functional Profiles of the Abstract Model for other environments, including environments that may be realized in the future.
     </p>
@@ -78,8 +78,8 @@ <h2>Introduction</h2>
       they define implements the Abstract Model's functions and can deliver alternate representation information as per the Alternate Representations Data Model.
     </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
+      While this specification only describes HTTP methods for content negotiation by profile via the HTTP Header and URL QSA Functional Profiles, it is expected
+      that implementers will want to implement functionally equivalent profiles for other environments, some of which may
       be not yet realized future environments.
     </p>
     <!--