Heading adjustments, incompleteness notes

conneg-by-ap/index.html

@@ -470,7 +470,7 @@ <h3>Query String Arguments</h3>
         web browsers by humans and in other <em>client</em>/<em>server</em> situations to deliver extra information to a
         <em>server</em>.
       </p>
-      <h5>Key naming</h5>
+      <p><strong><em>Key naming</em></strong></p>
       <p>
         When content negotiation by profile is to take place using QSAs, the <em>request</em>s and <em>response</em>s
         of the <a href="#abstractmodel">Abstract Model</a> <a>MUST</a> be implemented however there is some flexibility
@@ -479,7 +479,7 @@ <h5>Key naming</h5>
         preference-ordered profiles or Media types respectively with profiles or Media Types indicated by either URI or
         token.
       </p>
-      <div class="note" title="Current use of Media type tokens">
+      <div class="note" title="Current use of tokens for negotiation by Media Type">
         <p>
           Currently, the convention in HTTP content negotiation by media type uses tokens for Media Types, such as
           <code>text/html</code> or <code>application/ld+json</code> with the tokens registered at
@@ -496,7 +496,7 @@ <h5>Key naming</h5>
           for Media Types based on the IANA register's tokens.
         </p>
       </div>
-      <h5>Resource URI</h5>
+      <p><strong><em>Resource URI</em></strong></p>
       <p>
         Resource URIs for which QSA-based profile negotiation is taking place <a>MUST NOT</a>, themselves be QSA values
         of other resource URIs in any QSA-based realisation. Such mechanics may be used but must be transparent to the
@@ -552,8 +552,9 @@ <h4>list profiles</h4>
       </section>
       <section id="getresourcebyprofileqsa">
         <h4>get resource by profile</h4>
+        <div class="issue" title="To be completed"></div>
 
-        <h5>Expressing profile preference</h5>
+        <p><strong><em>Expressing profile preference</em></strong></p>
         <p>
           A <em>server</em> implementing <em>profile</em> listing for <em>resource</em>s <a>SHOULD</a> allow the
           requester to indicate preferences. This <a>SHOULD</a> be done by allowing the QSA indicating the desired
@@ -566,7 +567,7 @@ <h5>Expressing profile preference</h5>
         </pre>
         <p>
           It <a>MAY</a> be possible to use any any combination of profile URIs or tokens for this (e.g. <code>aaa</code>,
-          <code>http://example.org/profile-x</code>,<code>bbb</code> however, in this situation, profile URIs containing
+          <code>http://example.org/profile-x</code>,<code>bbb</code>) however, in this situation, profile URIs containing
           commas must escape them.
         </p>
         <p>
@@ -579,8 +580,8 @@ <h5>Expressing profile preference</h5>
       </section>
       <section id="listprofilestokensqsa">
         <h4>list profiles tokens</h4>
+        <div class="issue" title="To be completed"></div>
       </section>
-      <div class="issue" data-number="463"></div>
       <div class="issue" data-number="516"></div>
     </section>
     <section id="rest">