typo typo fixes fixes

From-SVN: r19601

4 files changed, 5 insertions, 5 deletions

diff --git a/libio/builtinbuf.h b/libio/builtinbuf.h
index 0e0c6e85a9e..3aa4c37a654 100644
--- a/libio/builtinbuf.h
+++ b/libio/builtinbuf.h
@@ -32,7 +32,7 @@ the executable file might be covered by the GNU General Public License. */
 #include <streambuf.h>
 
 #if !_IO_UNIFIED_JUMPTABLES
-// A builtinbuf a a streambuf where all the virtual operations
+// A builtinbuf is a streambuf where all the virtual operations
 // call the _IO_jump_t table.
 
 extern "C++" {
diff --git a/libio/fileops.c b/libio/fileops.c
index cfa97313d0d..c4406340704 100644
--- a/libio/fileops.c
+++ b/libio/fileops.c
@@ -256,7 +256,7 @@ _IO_do_write (fp, data, to_do)
     return 0;
   if (fp->_flags & _IO_IS_APPENDING)
     /* On a system without a proper O_APPEND implementation,
-       you would need to sys_seek(0, SEEK_END) here, but is
+       you would need to sys_seek(0, SEEK_END) here, but it
        is not needed nor desirable for Unix- or Posix-like systems.
        Instead, just indicate that offset (before and after) is
        unpredictable. */
diff --git a/libio/iostream.texi b/libio/iostream.texi
index 54ccced6e71..641cd7da22f 100644
--- a/libio/iostream.texi
+++ b/libio/iostream.texi
@@ -1595,7 +1595,7 @@ convenient, but it does cost some extra overhead.
 
 If you set things up to use the implementation of @code{stdio} provided
 with this library, then @code{cin}, @code{cout}, and @code{cerr} will be
-set up to to use @code{stdiobuf} objects, since you get their benefits
+set up to use @code{stdiobuf} objects, since you get their benefits
 for free.  @xref{Stdio,,C Input and Output}.
 
 @ignore
@@ -1624,7 +1624,7 @@ If @var{mode} is @samp{ios::in}, standard output from the program is sent
 to a pipe; you can read from the pipe by reading from the
 @code{procbuf}.  (This is similar to @w{@samp{popen(@var{command}, "r")}}.)
 
-If @var{mode} is @samp{ios::out}, output written written to the
+If @var{mode} is @samp{ios::out}, output written to the
 @code{procbuf} is written to a pipe; the program is set up to read its
 standard input from (the other end of) the pipe.  (This is similar to
 @w{@samp{popen(@var{command}, "w")}}.)
diff --git a/libio/streambuf.cc b/libio/streambuf.cc
index 6be926b2372..057d1e6e4ce 100644
--- a/libio/streambuf.cc
+++ b/libio/streambuf.cc
@@ -179,7 +179,7 @@ static _IO_FILE* _IO_sb_setbuf(_IO_FILE *fp, char *buf, _IO_ssize_t n)
    virtual function, so that C functions can access (potentially user-defined)
    streambuf-derived objects.
    Contrast the builtinbuf class, which does the converse:  Allow
-   C++ virtual calls to to be used on _IO_FILE objects that are builtin
+   C++ virtual calls to be used on _IO_FILE objects that are builtin
    (or defined by C code). */