Update README files

git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@3609 42af7a65-404d-4744-a932-0658087f49c3

1 files changed, 4 insertions, 3 deletions

diff --git a/nuttx/Documentation/NuttxPortingGuide.html b/nuttx/Documentation/NuttxPortingGuide.html
index 1ff52940b..00368df0e 100644
--- a/nuttx/Documentation/NuttxPortingGuide.html
+++ b/nuttx/Documentation/NuttxPortingGuide.html
@@ -3417,9 +3417,10 @@ build
     <code>CONFIG_STDIO_LINEBUFFER</code>:
     If standard C buffered I/O is enabled (<code>CONFIG_STDIO_BUFFER_SIZE</code> > 0),
     then this option may be added to force automatic, line-oriented flushing the output buffer
-    for <code>printf()</code> >, <code>fprintf()</code> >, and <code>vfprintf()</code> >.
-    When a newline character is encountered in the format string, the output buffer will be flushed.
-    This (slightly) increases the NuttX footprint but supports the kind of behavior that people expect for printf.
+    for <code>putc()</code>, <code>fputc()</code>, <code>putchar()</code>, <code>puts()</code>, <code>fputs()</code>,
+    <code>printf()</code>, <code>fprintf()</code>, and <code>vfprintf()</code>.
+    When a newline character is encountered in the output string, the output buffer will be flushed.
+    This (slightly) increases the NuttX footprint but supports the kind of behavior that people expect for <code>printf()</code>.
   <li>
     <code>CONFIG_NUNGET_CHARS</code>: Number of characters that can be
     buffered by ungetc() (Only if CONFIG_NFILE_STREAMS > 0)