Add debugging information for nacl_io library.

native_client_sdk/src/doc/devguide/coding/nacl_io.rst

Index: native_client_sdk/src/doc/devguide/coding/nacl_io.rst
diff --git a/native_client_sdk/src/doc/devguide/coding/nacl_io.rst b/native_client_sdk/src/doc/devguide/coding/nacl_io.rst
index 7d5b721ffb471e8f39333d01898aec0f847bece0..2dca215a46548a5c849448e4a16232d38b4e66dd 100644
--- a/native_client_sdk/src/doc/devguide/coding/nacl_io.rst
+++ b/native_client_sdk/src/doc/devguide/coding/nacl_io.rst
@@ -19,17 +19,20 @@ compiled and used in a Native Client module. The library is included as part
 of Native Client SDK and is implemented in on top of Pepper API.
 
 Since Native Client modules cannot access the host machine's file system
-directly, nacl_io provides several alternative filesystem types which
-can be used by the application. For example, the Chrome browser supports the
-`HTML5 File System API
-<http://www.html5rocks.com/en/tutorials/file/filesystem/>`_ which provides
-access to a protected area of the local file system. This filesystem can
-be accessed by an HTML page using JavaScript commands, and also by a Native
-Client module using the Pepper :doc:`File IO API <file-io>`. With nacl_io
-a Native Client application can mount an HTML5 filesystem and access it via
-standard POSIX I/O function such as ``fopen``, ``fseek``, ``fread``,
-``fwrite``, and ``fclose``, or their low level UNIX counterparts ``open``,
-``lseek``, ``read``, ``write`` and ``close``.
+directly, nacl_io provides several alternative filesystem types which can be
+used by the application. For example, the Chrome browser supports the `HTML5
+File System API <http://www.html5rocks.com/en/tutorials/file/filesystem/>`_
+which provides access to a protected area of the local file system. This
+filesystem can be accessed by an HTML page using JavaScript commands, and also
+by a Native Client module using the Pepper :doc:`File IO API <file-io>`.
+
+With nacl_io a Native Client application can mount an HTML5 filesystem and
+access it via standard POSIX I/O function such as ``fopen``, ``fseek``,
+``fread``, ``fwrite``, and ``fclose``, or their low level UNIX counterparts
+``open``, ``lseek``, ``read``, ``write`` and ``close``. Unlike most input/output
+for nacl_io, logging writes directly to the ``stderr`` stream of the NaCl

[Sam Clegg, 2014/10/01 21:52:14]

, internal logging and error reporting writes directly...

[jpmedley, 2014/10/07 17:01:42]

Done.

+process. It deliberately bypasses the standard library functions implemented in
+nacl_io to avoid circular calls to itself.

[Sam Clegg, 2014/10/01 21:52:14]

Perhaps put this in sub-sub-section called "Logging and Error Reporting" (or
maybe just in its own paragraph at the end).

The flow from this paragraph to the next is (IMHO) otherwise a little
interrupted.

[jpmedley, 2014/10/07 17:01:42]

Done.

 
 As well as the HTML5 file system, nacl_io provides several other file system
 types which are described in the table below:
@@ -212,7 +215,7 @@ below. Notice that it does not contain any PPAPI calls and looks like
     return 0;
   }
 
-Reference information
+Reference Information
 =====================
 
 The example discussed here is included in the SDK in the directory