touched up the conversion to TS, see phetsims/scenery-phet#726 and #160

js/ISoundPlayer.ts

@@ -1,9 +1,9 @@
 // Copyright 2022, University of Colorado Boulder
 
 /**
- * SoundPlayer is a "definition" type, based off of PaintDef.js, that defines a type that is used in the tambo sound
- * library but is not actually a base class.  This is similar to the idea of an "interface" in Java.  A SoundPlayer type
- * is a sound generator that has just the most basic methods for playing a sound.
+ * SoundPlayer is a "definition" type, initially based off of PaintDef.js, that defines a type that is used in the tambo
+ * sound library but is not actually a base class.  This is similar to the idea of an "interface" in Java.  A
+ * SoundPlayer type is a sound generator that has just the most basic methods for playing a sound.
  *
  * @author John Blanco (PhET Interactive Simulations)
  */

js/phetAudioContext.ts

@@ -1,7 +1,8 @@
 // Copyright 2018-2022, University of Colorado Boulder
 
 /**
- * phetAudioContext is a singleton instance of a Web Audio context that is used for all Web Audio interaction
+ * `phetAudioContext` is a singleton instance of a Web Audio context that is used for all Web Audio interaction within
+ * a sim.
  *
  * @author John Blanco
  */

js/sound-generators/SoundGenerator.ts

@@ -1,7 +1,8 @@
 // Copyright 2018-2022, University of Colorado Boulder
 
 /**
- * abstract base class for Web Audio based sound producing element that work in conjunction with the soundManager
+ * SoundGenerator is an abstract base class for Web-Audio-based sound-producing elements that work in conjunction with
+ * the soundManager to produces sounds.
  *
  * @author John Blanco (PhET Interactive Simulations)
  */

js/sound-generators/ValueChangeSoundGenerator.ts

@@ -6,8 +6,9 @@
  *
  * Because the sounds should only be produced when direct interactions from the user change a value, and not in other
  * situations (e.g. a reset), this class does not monitor a Property.  Instead, it provides methods that can be used to
- * evaluate changes in value and potentially play sounds, and it is the client's responsibility to know the situations
- * in which these methods should be called.
+ * evaluate changes in a value and potentially play sounds, and it is the client's responsibility to know the situations
+ * in which these methods should be called.  Often these methods will be called in drag handlers and other code that
+ * handles user input.
  *
  * @author John Blanco (PhET Interactive Simulations)
  */