From 600a84a99db0c6906b5657bef55d6eab558a6c91 Mon Sep 17 00:00:00 2001
From: Nick Guerrera <nicholg@microsoft.com>
Date: Wed, 6 May 2015 07:26:33 -0700
Subject: [PATCH] Fix incorrect documentation about parallel dispose

Previously, PEReader allowed mutliple calls to Dispose in parallel, but
that was removed because the caller must not Dispose the PEReader in
parallel to any other non-Dispose operation and the caller's
synchronization required to guarantee that can also guarantee that
Dispose is not called in parallel.
---
 .../src/System/Reflection/PortableExecutable/PEReader.cs      | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/System.Reflection.Metadata/src/System/Reflection/PortableExecutable/PEReader.cs b/src/System.Reflection.Metadata/src/System/Reflection/PortableExecutable/PEReader.cs
index e9e8ec54eb95..7322ca761cbc 100644
--- a/src/System.Reflection.Metadata/src/System/Reflection/PortableExecutable/PEReader.cs
+++ b/src/System.Reflection.Metadata/src/System/Reflection/PortableExecutable/PEReader.cs
@@ -216,8 +216,8 @@ public PEReader(ImmutableArray<byte> peImage)
         /// Disposes all memory allocated by the reader.
         /// </summary>
         /// <remarks>
-        /// <see cref="Dispose"/>  can be called multiple times (even in parallel). 
-        /// However, it is not safe to call <see cref="Dispose"/> in parallel with any other operation on the <see cref="PEReader"/>
+        /// <see cref="Dispose"/>  can be called multiple times (but not in parallel).
+        /// It is not safe to call <see cref="Dispose"/> in parallel with any other operation on the <see cref="PEReader"/>
         /// or reading from <see cref="PEMemoryBlock"/>s retrieved from the reader.
         /// </remarks>
         public void Dispose()