Meta: tidy up formatting

index.html

@@ -115,10 +115,10 @@ <h2>
         Push messaging is best suited to occasions where there is not already an active
         communications channel established between the <a>user agent</a> and the web application.
         Sending <a>push messages</a> requires considerably more resources when compared with more
-        direct methods of communication such as the [[Fetch|Fetch API]] or [[WebSockets]].
-        <a>Push messages</a> usually have higher latency than direct communications and they can
-        also be subject to restrictions on use. Most <a>push services</a> limit the size and
-        quantity of <a>push messages</a> that can be sent.
+        direct methods of communication such as the [[Fetch|Fetch API]] or [[WebSockets]]. <a>Push
+        messages</a> usually have higher latency than direct communications and they can also be
+        subject to restrictions on use. Most <a>push services</a> limit the size and quantity of
+        <a>push messages</a> that can be sent.
       </p>
     </section>
     <section>
@@ -229,8 +229,8 @@ <h2>
           </li>
           <li>When the <a>push subscription</a> request has completed successfully:
             <ol>
-              <li>Set |subscription|'s {{PushSubscription/endpoint}} attribute to the
-              <a>push subscription</a>'s <a>push endpoint</a>.
+              <li>Set |subscription|'s {{PushSubscription/endpoint}} attribute to the <a>push
+              subscription</a>'s <a>push endpoint</a>.
               </li>
               <li>If provided by the <a>push subscription</a>, set |subscription|'s
               {{PushSubscription/expirationTime}}.