Update how-to-define-value-equality-for-a-type.md (#1349)

public and non-public fields is the same thing as fields

e.g.,  x || !x == true

docs/csharp/programming-guide/statements-expressions-operators/how-to-define-value-equality-for-a-type.md

@@ -50,7 +50,7 @@ When you define a class or struct, you decide whether it makes sense to create a
 
 5.  x.`Equals`(null) returns `false`. However, null.Equals(null) throws an exception; it does not obey rule number two above.  
 
- Any struct that you define already has a default implementation of value equality that it inherits from the <xref:System.ValueType?displayProperty=fullName> override of the <xref:System.Object.Equals%28System.Object%29?displayProperty=fullName> method. This implementation uses reflection to examine all the public and non-public fields and properties in the type. Although this implementation produces correct results, it is relatively slow compared to a custom implementation that you write specifically for the type.  
+ Any struct that you define already has a default implementation of value equality that it inherits from the <xref:System.ValueType?displayProperty=fullName> override of the <xref:System.Object.Equals%28System.Object%29?displayProperty=fullName> method. This implementation uses reflection to examine all the fields and properties in the type. Although this implementation produces correct results, it is relatively slow compared to a custom implementation that you write specifically for the type.  
 
  The implementation details for value equality are different for classes and structs. However, both classes and structs require the same basic steps for implementing equality: