Address #1857: Fix typos and phrasing. (#1859)

* Address #1857: Fix typos and phrasing.

This first part covers everthing up to and including seciong 1.1.7.

* Aargh!  Fix typo!

index.bs

@@ -236,7 +236,7 @@ The API supports these primary features:
 * [[#ModularRouting|Modular routing]] for simple or complex
 	mixing/effect architectures, including [[#mixer-gain-structure|multiple sends and submixes]].
 
-* High dynamic range, using 32bits floats for internal processing.
+* High dynamic range, using 32-bit floats for internal processing.
 
 * [[#AudioParam|Sample-accurate scheduled sound playback]]
 	with low [[#latency|latency]] for musical applications
@@ -254,7 +254,7 @@ The API supports these primary features:
 	{{MediaElementAudioSourceNode|media element}}.
 
 * Processing live audio input using a {{MediaStreamTrackAudioSourceNode|MediaStream}} from
-	getUserMedia().
+	[[mediacapture-streams#dom-mediadevices-getusermedia|getUserMedia()]].
 
 * Integration with WebRTC
 	* Processing audio received from a remote peer using a
@@ -295,7 +295,7 @@ The API supports these primary features:
 
 * Dynamics compression for overall control and sweetening of the mix
 
-* Efficient [[#analysernode|real-time time-domain and frequency analysis / music visualizer support]].
+* Efficient [[#analysernode|real-time time-domain and frequency-domain analysis / music visualizer support]].
 
 * Efficient biquad filters for lowpass, highpass, and other common filters.
 
@@ -1177,7 +1177,7 @@ Methods</h4>
 
 					1.Let <var>buffer</var> be an
 						{{AudioBuffer}} containing the final result
-						(after possibly sample-rate conversion).
+						(after possibly performing sample-rate conversion).
 
 					2. Resolve <var>promise</var> with <var>buffer</var>.
 
@@ -7807,7 +7807,7 @@ whose <code>kind</code> is <code>"audio"</code>. This [[mediacapture-streams#med
 created when the node is created and is accessible via the
 {{MediaStreamAudioDestinationNode/stream}} attribute. This stream can be used in a similar way
 as a [[mediacapture-streams#mediastream|MediaStream]] obtained via
-<code>getUserMedia()</code>, and can, for example, be sent to a
+[[mediacapture-streams#dom-mediadevices-getusermedia|getUserMedia()]], and can, for example, be sent to a
 remote peer using the <code>RTCPeerConnection</code> (described in
 [[!webrtc]]) <code>addStream()</code> method.
 
@@ -12112,7 +12112,7 @@ to Consider</a>
 	No. Credit card information and the like is not used in Web Audio.
 	It is possible to use Web Audio to process or analyze voice data,
 	which might be a privacy concern, but access to the user's
-	microphone is permission-based via getUserMedia.
+	microphone is permission-based via [[mediacapture-streams#dom-mediadevices-getusermedia|getUserMedia()]].
 
 3. Does this specification introduce new state for an origin that
 	persists across browsing sessions?
@@ -12188,8 +12188,7 @@ to Consider</a>
 	document, but it will involve gaining access to the client
 	machine's audio input or microphone. This will require asking the
 	user for permission in an appropriate way, probably via the
-	<a href="https://w3c.github.io/mediacapture-main/#dom-mediadevices-getusermedia">
-	getUserMedia() API</a>.
+	[[mediacapture-streams#dom-mediadevices-getusermedia|getUserMedia() API]].
 
 9. Does this specification allow an origin access to aspects of a
 	user’s local computing environment?