prefer IO Type to TypeIO, phetsims/tandem#219

js/Action.js

@@ -56,7 +56,7 @@ class Action extends PhetioObject {
       // phet-io - see PhetioObject.js for doc
       tandem: Tandem.OPTIONAL,
 
-      // {function(IOType[]):IOType} - The non parameterized TypeIO. Override this to create a subtype of ActionIO as
+      // {function(IOType[]):IOType} - The non parameterized IOType. Override this to create a subtype of ActionIO as
       // the phetioType instead of a parameterized ActionIO Type.
       phetioOuterType: Action.ActionIO,
       phetioState: false,

js/Emitter.js

@@ -134,7 +134,7 @@ const cache = {};
  *
  * Providing validators to instrumented Emitters:
  * Instrumented Emitters should have their `validators` for each argument passed via EmitterIO (the phetioType).
- * To provide validators, there are two methods. First, by default each TypeIO has its own
+ * To provide validators, there are two methods. First, by default each IOType has its own
  * validator that will be used. So specifying an argument object like `{ type: NumberIO }` will automatically use
  * `NumberIO.validator` as the validator. This can be overridden with the `validator` key (second option), like
  * { type: NumberIO, validator: { isValidValue: v=> typeof v === 'number' &&  v < 5 } }`

js/ValidatorDef.js

@@ -72,7 +72,7 @@ const VALIDATOR_KEYS = [
   // valueType is `Array`.
   'arrayElementType',
 
-  // {function(new: IOType)} - A TypeIO used to specify the public typing for PhET-iO. Each TypeIO must have a
+  // {IOType} - A IOType used to specify the public typing for PhET-iO. Each IOType must have a
   // `validator` key specified that can be used for validation. See IOType for an example.
   'phetioType'
 ];