diff options
author | Matthias Lang <[email protected]> | 2010-03-15 07:46:50 +0100 |
---|---|---|
committer | Björn Gustavsson <[email protected]> | 2010-03-16 10:55:56 +0100 |
commit | bfd9a4f396d144199cb57376e6928701cf0dc931 (patch) | |
tree | 246a66e1bf48d1a2c9838390a68d87d4f155a74f /lib/stdlib/doc/src/io_protocol.xml | |
parent | 76ff26a3c209408c962a6115bf3426b2a55bd68a (diff) | |
download | otp-bfd9a4f396d144199cb57376e6928701cf0dc931.tar.gz otp-bfd9a4f396d144199cb57376e6928701cf0dc931.tar.bz2 otp-bfd9a4f396d144199cb57376e6928701cf0dc931.zip |
Change all incorrect occurrences of it's to its
The documentation (*.xml) in the otp tree has a common grammatical
problem, "it's" and "its" are often interchanged. That is annoying
for some readers.
This commit consists entirely of "it's" -> "its" changes. I went
through every .xml file in the tree. If there are any remaining
bugs of this type, it's because I missed them, not because I
didn't look.
Diffstat (limited to 'lib/stdlib/doc/src/io_protocol.xml')
-rw-r--r-- | lib/stdlib/doc/src/io_protocol.xml | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/lib/stdlib/doc/src/io_protocol.xml b/lib/stdlib/doc/src/io_protocol.xml index 201787f7b5..b52e862a5c 100644 --- a/lib/stdlib/doc/src/io_protocol.xml +++ b/lib/stdlib/doc/src/io_protocol.xml @@ -195,7 +195,7 @@ latin1, Module, Function, Args} respectively. </p> below).</p> <p>The function will be called with the data the io_server finds on - it's device, returning {done, Result, RestChars} when enough data is + its device, returning {done, Result, RestChars} when enough data is read (in which case Result is sent to the client and RestChars are kept in the io_server as a buffer for subsequent input) or {more, Continuation}, indicating that more characters are needed to @@ -741,7 +741,7 @@ optimize anything however. It is important though that the returned data is of the right type depending on the options set, so we convert the lists to binaries in the correct encoding <em>if possible</em> before returning. The function supplied in the get_until request may, -as it's final result return anything, so only functions actually +as its final result return anything, so only functions actually returning lists can get them converted to binaries. If the request contained the encoding tag unicode, the lists can contain all unicode codepoints and the binaries should be in UTF-8, if the encoding tag |