Fix some small mistakes in the documentation of clearImmediate

diff --git a/README.md b/README.md
index 7e1d3ed89f85bd4f1d6842cbab9470c454f4469c..6c1218a691d641a3b9a24b5671536edd84844170 100644 (file)
--- a/README.md
+++ b/README.md
@@ -55,4 +55,4 @@ Immediates are processed every step after timeouts and intervals have been proce
 Registers a new interval that will execute once in the current or the next step, depending on when it is registered. If an immediate is registered while immediates are processing, it will be executed in the next step. However, if an interval is registered by a timeout or interval callback, the immediate _will_ process in the same step in which it was registered. `...` are the arguments passed to the `callback` function that is called when the immediate executes. `setImmediate` returns an unique numeric immediate ID that can be passed to `clearImmediate`. If `callback` is not a function, an error is raised when the immediate is executed.
 
 #### `clearImmediate(id)`
-This function takes an ID of an existing interval and cancels it, meaning it will not execute. If `id` is not numeric, not a valid immediate id or the associated interval has already executed or been cleared, `clearImmediate` does nothing. `id` may however not be `nil`. `clearImmediate` may be called on any immediate at any time, if immediates are currently processing the cleared immediate is removed from the list of immediates to process.
+This function takes an ID of an existing immediate and cancels it, meaning it will not execute. If `id` is not numeric, not a valid immediate id or the associated immediate has already executed or been cleared, `clearImmediate` does nothing. `id` may however not be `nil`. `clearImmediate` may be called on any immediate at any time, if immediates are currently processing the cleared immediate is removed from the list of immediates to process.