1 files changed, 12 insertions, 12 deletions

diff --git a/mcs/class/referencesource/mscorlib/system/io/filestream.cs b/mcs/class/referencesource/mscorlib/system/io/filestream.cs
index 14aaf800073..38b86735241 100644
--- a/mcs/class/referencesource/mscorlib/system/io/filestream.cs
+++ b/mcs/class/referencesource/mscorlib/system/io/filestream.cs
@@ -7,7 +7,7 @@
 **
 ** Class:  FileStream
 ** 
-** <OWNER>Microsoft</OWNER>
+** <OWNER>[....]</OWNER>
 **
 **
 ** Purpose: Exposes a Stream around a file, with full 
@@ -39,11 +39,11 @@ using System.Diagnostics.Tracing;
 
 /*
  * FileStream supports different modes of accessing the disk - async mode
- * and sync mode.  They are two completely different codepaths in the
- * sync & async methods (ie, Read/Write vs. BeginRead/BeginWrite).  File
- * handles in NT can be opened in only sync or overlapped (async) mode,
+ * and [....] mode.  They are two completely different codepaths in the
+ * [....] & async methods (ie, Read/Write vs. BeginRead/BeginWrite).  File
+ * handles in NT can be opened in only [....] or overlapped (async) mode,
  * and we have to deal with this pain.  Stream has implementations of
- * the sync methods in terms of the async ones, so we'll
+ * the [....] methods in terms of the async ones, so we'll
  * call through to our base class to get those methods when necessary.
  *
  * Also buffering is added into FileStream as well. Folded in the
@@ -1224,7 +1224,7 @@ namespace System.IO {
 
                 Contract.Assert((_readPos == 0 && _readLen == 0 && _writePos >= 0) || (_writePos == 0 && _readPos <= _readLen), "We're either reading or writing, but not both.");
 
-                // Verify that internal position is in sync with the handle
+                // Verify that internal position is in [....] with the handle
                 if (_exposedHandle)
                     VerifyOSHandlePosition();
 
@@ -1353,7 +1353,7 @@ namespace System.IO {
 
         // Reading is done by blocks from the file, but someone could read
         // 1 byte from the buffer then write.  At that point, the OS's file
-        // pointer is out of sync with the stream's position.  All write 
+        // pointer is out of [....] with the stream's position.  All write 
         // functions should call this function to preserve the position in the file.
         private void FlushRead() {
             Contract.Assert(_writePos == 0, "FileStream: Write buffer must be empty in FlushRead!");
@@ -1628,7 +1628,7 @@ namespace System.IO {
                 offset -= (_readLen - _readPos);
             }
 
-            // Verify that internal position is in sync with the handle
+            // Verify that internal position is in [....] with the handle
             if (_exposedHandle)
                 VerifyOSHandlePosition();
 
@@ -1722,7 +1722,7 @@ namespace System.IO {
 
         // Checks the position of the OS's handle equals what we expect it to.
         // This will fail if someone else moved the FileStream's handle or if
-        // we've hit a 
+        // we've hit a bug in FileStream's position updating code.
         private void VerifyOSHandlePosition()
         {
             if (!CanSeek)
@@ -1945,7 +1945,7 @@ namespace System.IO {
                 // (either synchronously or asynchronously) before the first one 
                 // returns.  This would involve some sort of complex buffer locking
                 // that we probably don't want to get into, at least not in V1.
-                // If we did a sync read to fill the buffer, we could avoid the
+                // If we did a [....] read to fill the buffer, we could avoid the
                 // problem, and any async read less than 64K gets turned into a
                 // synchronous read by NT anyways...       -- 
 
@@ -2513,7 +2513,7 @@ namespace System.IO {
 
             if (r==0) {
                 hr = Marshal.GetLastWin32Error();
-                // We should never silently swallow an error here without some
+                // We should never silently ---- an error here without some
                 // extra work.  We must make sure that BeginReadCore won't return an 
                 // IAsyncResult that will cause EndRead to block, since the OS won't
                 // call AsyncFSCallback for us.  
@@ -2570,7 +2570,7 @@ namespace System.IO {
 
             if (r==0) {
                 hr = Marshal.GetLastWin32Error();
-                // We should never silently swallow an error here without some
+                // We should never silently ---- an error here without some
                 // extra work.  We must make sure that BeginWriteCore won't return an 
                 // IAsyncResult that will cause EndWrite to block, since the OS won't
                 // call AsyncFSCallback for us.