Client-ATS protocol cleanup

Signed-off-by: Ulf Bjorkengren <[email protected]>

spec/VISSv2_Core.html

@@ -1094,7 +1094,7 @@ <h2>Inquiry Access Token Request</h2>
           This request can be issued by the client after a session handle has been received in a response to an initial access token request.<br>
           The request shall contain at least the parameter below:
           <ul>
-            <li><a>Session handle</a>: The handle logically links the request to a previously issued initial access token request.</li>
+            <li>Session handle: The handle logically links the request to a previously issued initial access token request.</li>
           </ul> 
           </p>
         </section>
@@ -1141,7 +1141,7 @@ <h2>Access Token Response To Initial Access Token Request</h2>
           <h2>Access Token Response To Inquiry Access Token Request</h2>
           <p>
           There are three different responses possible to an inquiry access token request.<br>
-          In the case that there is still no consent reply availablefrom the ECF, the response is identical to the response to the initial access token response, see above.<b>
+          In the case that there is still no consent reply availablefrom the ECF, the response is identical to the response to the initial access token response, see above.<br>
           In the case that there is a negative consent reply from the ECF, the response shall contain the parameter:
           <ul>
             <li>Consent status: The consent reply was negative, so consent status is set to NO.</li>