revert changes to design-guidelines folder (#50350)

Author: gewarren

docs/standard/design-guidelines/attributes.md

@@ -13,7 +13,7 @@ ms.assetid: ee0038ef-b247-4747-a650-3c5c5cd58d8b
 
 <xref:System.Attribute?displayProperty=nameWithType> is a base class used to define custom attributes.
 
- Attributes are annotations that can be added to programming elements such as assemblies, types, members, and parameters. They are stored in the metadata of the assembly and can be accessed at runtime using the reflection APIs. For example, the Framework defines the <xref:System.ObsoleteAttribute>, which can be applied to a type or a member to indicate that the type or member has been deprecated.
+ Attributes are annotations that can be added to programming elements such as assemblies, types, members, and parameters. They are stored in the metadata of the assembly and can be accessed at run time using the reflection APIs. For example, the Framework defines the <xref:System.ObsoleteAttribute>, which can be applied to a type or a member to indicate that the type or member has been deprecated.
 
  Attributes can have one or more properties that carry additional data related to the attribute. For example, `ObsoleteAttribute` could carry additional information about the release in which a type or a member got deprecated and the description of the new APIs replacing the obsolete API.
 

docs/standard/design-guidelines/events-and-callbacks.md

@@ -27,7 +27,7 @@ Callbacks are extensibility points that allow a framework to call back into user
 
  ✔️ DO use the new `Func<...>`, `Action<...>`, or `Expression<...>` types instead of custom delegates, when defining APIs with callbacks.
 
- `Func<...>` and `Action<...>` represent generic delegates. `Expression<...>` represents function definitions that can be compiled and subsequently invoked at runtime but can also be serialized and passed to remote processes.
+ `Func<...>` and `Action<...>` represent generic delegates. `Expression<...>` represents function definitions that can be compiled and subsequently invoked at run time but can also be serialized and passed to remote processes.
 
  ✔️ DO measure and understand performance implications of using `Expression<...>`, instead of using `Func<...>` and `Action<...>` delegates.
 

docs/standard/design-guidelines/extension-methods.md

@@ -24,7 +24,7 @@ Extension methods are a language feature that allows static methods to be called
 
  ❌ AVOID defining extension methods on <xref:System.Object?displayProperty=nameWithType>.
 
- VB users will not be able to call such methods on object references using the extension method syntax. VB does not support calling such methods because, in VB, declaring a reference as Object forces all method invocations on it to be late bound (actual member called is determined at runtime), while bindings to extension methods are determined at compile-time (early bound).
+ VB users will not be able to call such methods on object references using the extension method syntax. VB does not support calling such methods because, in VB, declaring a reference as Object forces all method invocations on it to be late bound (actual member called is determined at run time), while bindings to extension methods are determined at compile-time (early bound).
 
  Note that the guideline applies to other languages where the same binding behavior is present, or where extension methods are not supported.
 

docs/standard/design-guidelines/virtual-members.md

@@ -16,7 +16,7 @@ Virtual members can be overridden, thus changing the behavior of the subclass. T
 
  Virtual members perform better than callbacks and events, but do not perform better than non-virtual methods.
 
- The main disadvantage of virtual members is that the behavior of a virtual member can only be modified at the time of compilation. The behavior of a callback can be modified at runtime.
+ The main disadvantage of virtual members is that the behavior of a virtual member can only be modified at the time of compilation. The behavior of a callback can be modified at run time.
 
  Virtual members, like callbacks (and maybe more than callbacks), are costly to design, test, and maintain because any call to a virtual member can be overridden in unpredictable ways and can execute arbitrary code. Also, much more effort is usually required to clearly define the contract of virtual members, so the cost of designing and documenting them is higher.