From 00004160a1230892197041f5628e7b1545bd8146 Mon Sep 17 00:00:00 2001 From: Kyle Robinson Young Date: Fri, 8 Aug 2014 10:49:24 -0700 Subject: [PATCH] doc: typo fixes on stream, tls and http Reviewed-by: Trevor Norris --- doc/api/http.markdown | 2 +- doc/api/stream.markdown | 2 +- doc/api/tls.markdown | 7 ++++--- 3 files changed, 6 insertions(+), 5 deletions(-) diff --git a/doc/api/http.markdown b/doc/api/http.markdown index 932b80e4be..c0a8730ca9 100644 --- a/doc/api/http.markdown +++ b/doc/api/http.markdown @@ -849,7 +849,7 @@ the client should send the request body. Flush the request headers. -For effiency reasons, node.js normally buffers the request headers until you +For efficiency reasons, node.js normally buffers the request headers until you call `request.end()` or write the first chunk of request data. It then tries hard to pack the request headers and data into a single TCP packet. diff --git a/doc/api/stream.markdown b/doc/api/stream.markdown index e9f6e2c502..2f399a77aa 100644 --- a/doc/api/stream.markdown +++ b/doc/api/stream.markdown @@ -971,7 +971,7 @@ function SourceWrapper(options) { self._source.readStop(); }; - // When the source ends, we push the EOF-signalling `null` chunk + // When the source ends, we push the EOF-signaling `null` chunk this._source.onend = function() { self.push(null); }; diff --git a/doc/api/tls.markdown b/doc/api/tls.markdown index c74f564ffe..a8539d2f9b 100644 --- a/doc/api/tls.markdown +++ b/doc/api/tls.markdown @@ -154,7 +154,7 @@ automatically set as a listener for the [secureConnection][] event. The `RC4` is used as a fallback for clients that speak on older version of the TLS protocol. `RC4` has in recent years come under suspicion and should be considered compromised for anything that is truly sensitive. - It is speculated that state-level actors posess the ability to break it. + It is speculated that state-level actors possess the ability to break it. **NOTE**: Previous revisions of this section suggested `AES256-SHA` as an acceptable cipher. Unfortunately, `AES256-SHA` is a CBC cipher and therefore @@ -573,8 +573,9 @@ Typical flow: 5. Client validates the response and either destroys socket or performs a handshake. -NOTE: `issuer` could be null, if certficiate is self-signed or if issuer is not -in the root certificates list. (You could provide an issuer via `ca` option.) +NOTE: `issuer` could be null, if the certificate is self-signed or if the issuer +is not in the root certificates list. (You could provide an issuer via `ca` +option.) NOTE: adding this event listener will have an effect only on connections established after addition of event listener.