From 14eaaa433d6f4b1ce67857c1bbf94eca6512296d Mon Sep 17 00:00:00 2001
From: Aaron Robinson <arobins@microsoft.com>
Date: Mon, 23 Sep 2019 12:06:01 -0700
Subject: [PATCH] Update ValueType.xml

See https://github.com/dotnet/coreclr/issues/26833
---
 xml/System/ValueType.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xml/System/ValueType.xml b/xml/System/ValueType.xml
index 2e23aeebcdd..1b94c3017e5 100644
--- a/xml/System/ValueType.xml
+++ b/xml/System/ValueType.xml
@@ -151,7 +151,7 @@
 ## Remarks  
  The <xref:System.ValueType.Equals%28System.Object%29?displayProperty=nameWithType> method overrides <xref:System.Object.Equals%28System.Object%29?displayProperty=nameWithType> and provides the default implementation of value equality for all value types in the .NET Framework.  
   
- If none of the fields of the current instance and `obj` are reference types, the <xref:System.ValueType.Equals%2A> method performs a byte-by-byte comparison of the two objects in memory. Otherwise, it uses reflection to compare the corresponding fields of `obj` and this instance.  
+ The default implementation calls <xref:System.Object.Equals%28System.Object%29?displayProperty=nameWithType> on each field of the current instance and `obj` and returns `true` if all fields are equal.
   
 > [!TIP]
 >  Particularly if your value type contains fields that are reference types, you should override the <xref:System.ValueType.Equals%28System.Object%29> method. This can improve performance and enable you to more closely represent the meaning of equality for the type.