Fix a couple of doc comment references - and many spelling mistakes

sdk/lib/isolate/isolate.dart

 // Copyright (c) 2012, the Dart project authors.  Please see the AUTHORS file
 // for details. All rights reserved. Use of this source code is governed by a
 // BSD-style license that can be found in the LICENSE file.
 
 /**
  * Concurrent programming using _isolates_:
  * independent workers that are similar to threads
  * but don't share memory,
  * communicating only via messages.
  *
@@ skipping 189 matching lines @@
    *
    * Usually the initial [message] contains a [SendPort] so
    * that the spawner and spawnee can communicate with each other.
    *
    * If the [paused] parameter is set to `true`,
    * the isolate will start up in a paused state,
    * just before calling the [entryPoint] function with the [message],
    * as if by an initial call of `isolate.pause(isolate.pauseCapability)`.
    * To resume the isolate, call `isolate.resume(isolate.pauseCapability)`.
    *
-   * If the [errorAreFatal], [onExit] and/or [onError] parameters are provided,
+   * If the [errorsAreFatal], [onExit] and/or [onError] parameters are provided,
    * the isolate will act as if, respectively, [setErrorsFatal],
    * [addOnExitListener] and [addErrorListener] were called with the
    * corresponding parameter and was processed before the isolate starts
    * running.
    *
    * If [errorsAreFatal] is omitted, the platform may choose a default behavior
    * or inherit the current isolate's behavior.
    *
    * You can also call the [setErrorsFatal], [addOnExitListener] and
    * [addErrorListener] methods on the returned isolate, but unless the
@@ skipping 24 matching lines @@
    * * `main(args, message)`
    *
    * When present, the parameter `args` is set to the provided [args] list.
    * When present, the parameter `message` is set to the initial [message].
    *
    * If the [paused] parameter is set to `true`,
    * the isolate will start up in a paused state,
    * as if by an initial call of `isolate.pause(isolate.pauseCapability)`.
    * To resume the isolate, call `isolate.resume(isolate.pauseCapability)`.
    *
-   * If the [errorAreFatal], [onExit] and/or [onError] parameters are provided,
+   * If the [errorsAreFatal], [onExit] and/or [onError] parameters are provided,
    * the isolate will act as if, respectively, [setErrorsFatal],
    * [addOnExitListener] and [addErrorListener] were called with the
    * corresponding parameter and was processed before the isolate starts
    * running.
    *
    * You can also call the [setErrorsFatal], [addOnExitListener] and
    * [addErrorListener] methods on the returned isolate, but unless the
    * isolate was started as [paused], it may already have terminated
    * before those methods can complete.
    *
@@ skipping 143 matching lines @@
   /**
    * Stops listening for exit messages from the isolate.
    *
    * Requests for the isolate to not send exit messages on [responsePort].
    * If the isolate isn't expecting to send exit messages on [responsePort],
    * because the port hasn't been added using [addOnExitListener],
    * or because it has already been removed, the request is ignored.
    *
    * If the same port has been passed via [addOnExitListener] more than once,
    * only one call to `removeOnExitListener` is needed to stop it from receiving
-   * exit messagees.
+   * exit messages.
    *
    * Closing the receive port that is associated with the [responsePort] does
    * not stop the isolate from sending uncaught errors, they are just going to
    * be lost.
    *
    * An exit message may still be sent if the isolate terminates
    * before this request is received and processed.
    */
   external void removeOnExitListener(SendPort responsePort);
 
@@ skipping 96 matching lines @@
   /**
    * Stops listening for uncaught errors from the isolate.
    *
    * Requests for the isolate to not send uncaught errors on [port].
    * If the isolate isn't expecting to send uncaught errors on [port],
    * because the port hasn't been added using [addErrorListener],
    * or because it has already been removed, the request is ignored.
    *
    * If the same port has been passed via [addErrorListener] more than once,
    * only one call to `removeErrorListener` is needed to stop it from receiving
-   * unaught errors.
+   * uncaught errors.
    *
    * Uncaught errors message may still be sent by the isolate
    * until this request is received and processed.
    */
   external void removeErrorListener(SendPort port);
 
   /**
    * Returns a broadcast stream of uncaught errors from the isolate.
    *
    * Each error is provided as an error event on the stream.
@@ skipping 174 matching lines @@
  * as the original error, but has no other features of the original error.
  */
 class RemoteError implements Error {
   final String _description;
   final StackTrace stackTrace;
   RemoteError(String description, String stackDescription)
       : _description = description,
         stackTrace = new StackTrace.fromString(stackDescription);
   String toString() => _description;
 }