Link Web Audio API to definition and add some punctuation

Michael Wilson · Michael Wilson · commit 308f2cb3b69d · 2023-10-05T11:45:51.000-07:00
diff --git a/index.html b/index.html
@@ -39,7 +39,7 @@
             key: "Implementation report:",
             data: [
               {
-                value: "No preliminary interoperability or implementation report exists",
+                value: "No preliminary interoperability or implementation report exists.",
               },
             ],
           },
@@ -100,9 +100,10 @@
       </p>
       <p>
         The Web MIDI API is also expected to be used in conjunction with other
-        APIs and elements of the web platform, notably the Web Audio API. This
-        API is also intended to be familiar to users of MIDI APIs on other
-        systems, such as Apple's CoreMIDI and Microsoft's Windows MIDI API.
+        APIs and elements of the web platform, notably the <a>Web Audio
+        API</a>. This API is also intended to be familiar to users of MIDI APIs
+        on other systems, such as Apple's CoreMIDI and Microsoft's Windows MIDI
+        API.
       </p>
     </section>
     <section id="sotd"></section>
@@ -934,7 +935,7 @@ <h2 id="MIDIPort">
               "MIDIPort.onstatechange">statechange</a> at the {{MIDIPort}}, and
               <a data-lt="MIDIAccess.onstatechange">statechange</a> at the
               {{MIDIAccess}}, using {{MIDIConnectionEvent}}  with the {{MIDIConnectionEvent/port}} attribute set
-              to |port|
+              to |port|.
             </p>
           </li>
         </ol>
@@ -1433,12 +1434,12 @@ <h2>
           mapped against these features:
         </p>
         <ol>
-          <li>Receiving short messages. This is the most attractive scenario
-          for Web MIDI, as it enables getting input from keyboards, drum pads,
-          guitars, wind controllers, DJ/controllerist controllers, and more,
-          and use those messages as input to control instruments and features
-          in the Web Audio API as well as other control scenarios (MIDI is the
-          protocol of choice for the multi-billion-dollar music production
+          <li>Receiving short messages. This is the most attractive scenario for
+          Web MIDI, as it enables getting input from keyboards, drum pads,
+          guitars, wind controllers, DJ/controllerist controllers, and more, and
+          use those messages as input to control instruments and features in
+          the <a>Web Audio API</a> as well as other control scenarios (MIDI is
+          the protocol of choice for the multi-billion-dollar music production
           industry for getting physical controllers like knobs and buttons
           attached to your computer, both in pro/prosumer audio and media
           applications as well as consumer applications like Garageband.)
