Respond to feedback.

Author: BillWagner

docs/csharp/fundamentals/types/interfaces.md

@@ -20,7 +20,7 @@ The following example declares an interface and a class that implements it:
 
 :::code language="csharp" source="./snippets/interfaces/interfaces.cs" ID="ImplementEquatable":::
 
-Any class or struct that implements <xref:System.IEquatable`1> must provide an `Equals` method that matches the interface signature. You can count on any `IEquatable<T>` implementation to support equality comparison, regardless of the concrete type. That predictability is the core value of interfaces.
+Any class or struct that implements <xref:System.IEquatable`1> must provide an `Equals` method that matches the interface signature. You can count on any `IEquatable<T>` implementation to support equality comparison, regardless of the concrete type. That predictability is the core value of interfaces.
 
 ## Declare an interface
 
@@ -48,7 +48,7 @@ Explicit implementation is useful when two interfaces declare members with the s
 
 ## Interface inheritance
 
-Interfaces can inherit from one or more other interfaces. A class that implements a derived interface must implement all members from the derived interface and all of its base interfaces:
+Interfaces can inherit from one or more other interfaces. A class that implements a derived interface must implement all members from the derived interface and all of its base interfaces:
 
 :::code language="csharp" source="./snippets/interfaces/interfaces.cs" ID="InterfaceInheritance":::
 
@@ -78,7 +78,7 @@ Interfaces support two advanced features that go beyond basic contracts:
 - **Default interface members** let an interface provide a method body. Implementing types inherit the default implementation and can optionally override it. For more information, see [default interface methods](../../advanced-topics/interface-implementation/default-interface-methods-versions.md).
 - **Static abstract members** require implementing types to provide a static member, which is useful for defining operator contracts or factory patterns. For more information, see [static abstract members in interfaces](../../language-reference/keywords/interface.md#static-abstract-and-virtual-members).
 
-Both features are covered in the advanced topics section. Most everyday interface usage involves the declaring and implementing patterns described earlier in this article.
+Both features are covered in the article on [interfaces](../../language-reference/keywords/interface.md) in the language reference. Most everyday interface usage involves the declaring and implementing patterns described earlier in this article.
 
 ## Interfaces summary
 

docs/standard/base-types/choosing-between-anonymous-and-tuple.md

@@ -6,7 +6,7 @@ ms.date: 07/01/2020
 ---
 # Choosing between anonymous and tuple types
 
-Choosing the appropriate type involves considering its usability, performance, and tradeoffs compared to other types. Anonymous types have been available since C# 3.0, while generic <xref:System.Tuple`2?displayProperty=nameWithType> types were introduced with .NET Framework 4.0. Since then new options have been introduced with language level support, such as <xref:System.ValueTuple`2?displayProperty=nameWithType> - which as the name implies, provide a value type with the flexibility of anonymous types. In this article, you'll learn when it's appropriate to choose one type over the other.
+Choosing the appropriate type involves considering its usability, performance, and tradeoffs compared to other types. Anonymous types have been available since C# 3.0, while generic <xref:System.Tuple`2?displayProperty=nameWithType> types were introduced with .NET Framework 4.0. Since then, new options have been introduced with language level support, such as <xref:System.ValueTuple`2?displayProperty=nameWithType>. As the names imply, these options provide a value type with the flexibility of anonymous types. In this article, you'll learn when it's appropriate to choose one type over the other.
 
 ## Usability and functionality