typos
This commit is contained in:
parent
a9a252fda9
commit
839fb8e19b
@ -1,6 +1,6 @@
|
||||
## Debugger
|
||||
|
||||
V8 comes with an extensive debugger which is accessable out-of-process via a
|
||||
V8 comes with an extensive debugger which is accessible out-of-process via a
|
||||
simple [TCP protocol](http://code.google.com/p/v8/wiki/DebuggerProtocol).
|
||||
Node has a built-in client for this debugger. To use this, start Node with the
|
||||
`debug` argument; a prompt will appear:
|
||||
|
@ -33,7 +33,7 @@ AAAA (IPv6) record.
|
||||
The callback has arguments `(err, address, family)`. The `address` argument
|
||||
is a string representation of a IP v4 or v6 address. The `family` argument
|
||||
is either the integer 4 or 6 and denotes the family of `address` (not
|
||||
neccessarily the value initially passed to `lookup`).
|
||||
necessarily the value initially passed to `lookup`).
|
||||
|
||||
|
||||
### dns.resolve(domain, rrtype='A', callback)
|
||||
|
@ -267,7 +267,7 @@ implicit/mutable headers will be calculated and call this function for you.
|
||||
### response.statusCode
|
||||
|
||||
When using implicit headers (not calling `response.writeHead()` explicitly), this property
|
||||
controlls the status code that will be send to the client when the headers get
|
||||
controls the status code that will be send to the client when the headers get
|
||||
flushed.
|
||||
|
||||
Example:
|
||||
@ -368,7 +368,7 @@ Options:
|
||||
|
||||
- `host`: A domain name or IP address of the server to issue the request to.
|
||||
- `port`: Port of remote server.
|
||||
- `method`: A string specifing the HTTP request method. Possible values:
|
||||
- `method`: A string specifying the HTTP request method. Possible values:
|
||||
`'GET'` (default), `'POST'`, `'PUT'`, and `'DELETE'`.
|
||||
- `path`: Request path. Should include query string and fragments if any.
|
||||
E.G. `'/index.html?page=12'`
|
||||
@ -424,7 +424,7 @@ There are a few special headers that should be noted.
|
||||
## http.get(options, callback)
|
||||
|
||||
Since most requests are GET requests without bodies, Node provides this
|
||||
convience method. The only difference between this method and `http.request()` is
|
||||
convenience method. The only difference between this method and `http.request()` is
|
||||
that it sets the method to GET and calls `req.end()` automatically.
|
||||
|
||||
Example:
|
||||
@ -474,7 +474,7 @@ By default set to 5. Determines how many concurrent sockets the agent can have o
|
||||
|
||||
### agent.sockets
|
||||
|
||||
An array of sockets currently inuse by the Agent. Do not modify.
|
||||
An array of sockets currently in use by the Agent. Do not modify.
|
||||
|
||||
### agent.queue
|
||||
|
||||
|
@ -95,7 +95,7 @@ First, `/node_modules` is never appended to a folder already ending in
|
||||
`/node_modules`.
|
||||
|
||||
Second, if the file calling `require()` is already inside a `node_modules`
|
||||
heirarchy, then the top-most `node_modules` folder is treated as the
|
||||
hierarchy, then the top-most `node_modules` folder is treated as the
|
||||
root of the search tree.
|
||||
|
||||
For example, if the file at
|
||||
|
@ -170,7 +170,7 @@ socket is established. If there is a problem connecting, the `'connect'`
|
||||
event will not be emitted, the `'error'` event will be emitted with
|
||||
the exception.
|
||||
|
||||
The `callback` paramenter will be added as an listener for the 'connect'
|
||||
The `callback` parameter will be added as an listener for the 'connect'
|
||||
event.
|
||||
|
||||
|
||||
|
@ -47,7 +47,7 @@ support this functionality; all others will simply never emit this event.
|
||||
### stream.readable
|
||||
|
||||
A boolean that is `true` by default, but turns `false` after an `'error'`
|
||||
occured, the stream came to an `'end'`, or `destroy()` was called.
|
||||
occurred, the stream came to an `'end'`, or `destroy()` was called.
|
||||
|
||||
### stream.setEncoding(encoding)
|
||||
Makes the data event emit a string instead of a `Buffer`. `encoding` can be
|
||||
|
@ -112,7 +112,7 @@ handshaked. The argument is a duplex instance of `stream.Stream`. It has all
|
||||
the common stream methods and events.
|
||||
|
||||
`cleartextStream.authorized` is a boolean value which indicates if the
|
||||
client has verified by one of the supplied cerificate authorities for the
|
||||
client has verified by one of the supplied certificate authorities for the
|
||||
server. If `cleartextStream.authorized` is false, then
|
||||
`cleartextStream.authorizationError` is set to describe how authorization
|
||||
failed. Implied but worth mentioning: depending on the settings of the TLS
|
||||
|
@ -34,7 +34,7 @@ terminal.
|
||||
|
||||
### tty.setRawMode(mode)
|
||||
|
||||
`mode` should be `true` or `false`. This sets the properies of the current
|
||||
`mode` should be `true` or `false`. This sets the properties of the current
|
||||
process's stdin fd to act either as a raw device or default.
|
||||
|
||||
|
||||
|
@ -31,7 +31,7 @@
|
||||
<code>Stream.prototype.pipe()</code> method. Functionality was
|
||||
enhanced and API simplified.
|
||||
|
||||
<li>Simplier HTTP client API with connection pools.
|
||||
<li>Simpler HTTP client API with connection pools.
|
||||
|
||||
<li> Cheaper <code>Buffer</code> allocation. Node uses
|
||||
<code>Buffer</code> objects in many places - it was noticed that they
|
||||
|
Loading…
x
Reference in New Issue
Block a user