aboutsummaryrefslogtreecommitdiff
path: root/doc/api/crypto.markdown
diff options
context:
space:
mode:
Diffstat (limited to 'doc/api/crypto.markdown')
-rw-r--r--doc/api/crypto.markdown4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/api/crypto.markdown b/doc/api/crypto.markdown
index dd31ae7ac3..46d1e5f3b0 100644
--- a/doc/api/crypto.markdown
+++ b/doc/api/crypto.markdown
@@ -601,7 +601,7 @@ called. Multiple calls will cause an error to be thrown.
Updates the hash content with the given `data`, the encoding of which
is given in `input_encoding` and can be `'utf8'`, `'ascii'` or
`'binary'`. If `encoding` is not provided, and the `data` is a string, an
-encoding of `'binary'` is enforced. If `data` is a [`Buffer`][] then
+encoding of `'utf8'` is enforced. If `data` is a [`Buffer`][] then
`input_encoding` is ignored.
This can be called many times with new data as it is streamed.
@@ -811,7 +811,7 @@ or [buffers][`Buffer`]. The default value is `'buffer'`, which makes methods
default to [`Buffer`][] objects.
The `crypto.DEFAULT_ENCODING` mechanism is provided for backwards compatibility
-with legacy programs that expect `'binary'` to be the default encoding.
+with legacy programs that expect `'utf8'` to be the default encoding.
New applications should expect the default to be `'buffer'`. This property may
become deprecated in a future Node.js release.