Improve docs for buffer.toString and buffer.copy

Improve documentation for buffer.toString and buffer.copy per issues #8859 and #8857.
+1. Ok, will work those edits up.
On Dec 17, 2014 3:28 PM, "Timothy J Fontaine" <notifications@github.com>
wrote:

> In doc/api/buffer.markdown
> <https://github.com/joyent/node/pull/8888#discussion-diff-22013800>:
>
> > @@ -187,12 +187,20 @@ The method will not write partial characters.
> >  * `start` Number, Optional, Default: 0
> >  * `end` Number, Optional, Default: `buffer.length`
> >
> > -Decodes and returns a string from buffer data encoded with `encoding`
> > -(defaults to `'utf8'`) beginning at `start` (defaults to `0`) and ending at
> > -`end` (defaults to `buffer.length`).
> > -
> > -See `buffer.write()` example, above.
> > +Decodes and returns a string from buffer data encoded using the specified
> > +character set encoding. If `encoding` is `undefined` or
> > +`null`, then `encoding` defaults to `'utf8'`. The `start` and `end`
> > +parameters default to `0` and `buffer.length` when not specified or
> > +passed as `undefined`/`NaN`.
>
> maybe change to "undefined or anything not parseable as a number",
> @trevnorris <https://github.com/trevnorris> is this true for v0.10 and is
> it a constraint we should tighten for v0.12? I'm not sure I can think of a
> valid reason to let invalid input go "ignored".
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/joyent/node/pull/8888/files#r22013800>.
>