Fix typos in comments

Author: stakx

src/Moq/Moq.Sdk/Behavior.cs

@@ -28,7 +28,7 @@ public Behavior(InvokeBehavior invoke, string displayName)
         /// delegate and friendly display name.
         /// </summary>
         /// <remarks>
-        /// Use this constructor overload whenver constructing the display 
+        /// Use this constructor overload whenever constructing the display
         /// name is somewhat expensive.
         /// </remarks>
         public Behavior(InvokeBehavior invoke, Lazy<string> displayName)

src/Moq/Moq.Sdk/IMockFactory.cs

@@ -15,7 +15,7 @@ public interface IMockFactory
         /// <param name="baseType">The base type (or main interface) of the mock.</param>
         /// <param name="implementedInterfaces">Additional interfaces implemented by the mock, or an empty array.</param>
         /// <param name="construtorArguments">
-        /// Contructor arguments if the <paramref name="baseType" /> is a class, rather than an interface, or an empty array.
+        /// Constructor arguments if the <paramref name="baseType" /> is a class, rather than an interface, or an empty array.
         /// </param>
         /// <returns>A mock that implements <see cref="IMocked"/> in addition to the specified interfaces (if any).</returns>
 		object CreateMock(Assembly mocksAssembly, Type baseType, Type[] implementedInterfaces, object[] construtorArguments);

src/Moq/Moq.Sdk/MockContext.cs

@@ -17,7 +17,7 @@ public static class MockContext
         /// <summary>
         /// The last invocation on the mock, turned into an <see cref="IMockSetup"/> 
         /// ready for use together with the <see cref="IMock.BehaviorFor(IMockSetup)"/> 
-        /// method to locate the maching <see cref="IMockBehavior"/> to add new behaviors 
+        /// method to locate the matching <see cref="IMockBehavior"/> to add new behaviors
         /// when a matching invocation is performed.
         /// </summary>
         /// <remarks>

src/Moq/Moq/CallbackExtension.cs

@@ -23,7 +23,7 @@ static TResult Callback<TResult>(this TResult target, Action<IArgumentCollection
 
                 // If there is already a behavior wrap it instead, 
                 // so we can do a callback after even if it's a 
-                // shortcircuiting one like Returns.
+                // short-circuiting one like Returns.
                 if (behavior.Behaviors.Count > 0)
                 {
                     var wrapped = behavior.Behaviors.Pop();

src/Moq/Moq/ReturnsBehavior.cs

@@ -7,7 +7,7 @@ namespace Moq
 {
     /// <summary>
     /// A custom behavior for returning values, so that 
-    /// the actual value to return can be replaced on succesive 
+    /// the actual value to return can be replaced on successive
     /// <see cref="ReturnsExtension"/> method calls.
     /// </summary>
     [DebuggerDisplay("{DebuggerValue}", Name = "Returns", Type = nameof(ReturnsBehavior))]

src/Moq/Moq/ReturnsExtension.cs

@@ -66,8 +66,8 @@ static TResult Returns<TResult>(Delegate value, InvokeBehavior behavior)
             var setup = MockContext.CurrentSetup;
             if (setup != null)
             {
-                // TODO: Is this even necessary given that intellisense gives us 
-                // the rigth compiler safety already?
+                // TODO: Is this even necessary given that IntelliSense gives us
+                // the right compiler safety already?
                 setup.Invocation.EnsureCompatible(value);
 
                 var mock = ((IMocked)setup.Invocation.Target).Mock;

src/Stunts/Stunts.Analyzer/DiagnosticsExtensions.cs

@@ -21,7 +21,7 @@ public static class DiagnosticsExtensions
         };
 
         /// <summary>
-        /// Gets the diangostics that represent build errors that happen when generated 
+        /// Gets the diagnostics that represent build errors that happen when generated
         /// code is out of date.
         /// </summary>
         public static Diagnostic[] GetCompilationErrors(this Compilation compilation) 

src/Stunts/Stunts.Analyzer/StuntGeneratorAnalyzer.cs

@@ -50,12 +50,12 @@ protected StuntGeneratorAnalyzer(NamingConvention naming, Type generatorAttribut
         public virtual DiagnosticDescriptor OutdatedDiagnostic => StuntDiagnostics.OutdatedStunt;
 
         /// <summary>
-        /// Returns the single <see cref="MissingDiagnostic"/> this analyer supports.
+        /// Returns the single <see cref="MissingDiagnostic"/> this analyzer supports.
         /// </summary>
         public sealed override ImmutableArray<DiagnosticDescriptor> SupportedDiagnostics
         {
             // NOTE: this creates the return value at this point because both Missing and Outdated 
-            // descriptors can be overriden as a customization point.
+            // descriptors can be overridden as a customization point.
             get { return ImmutableArray.Create(MissingDiagnostic, OutdatedDiagnostic); }
         }
 
@@ -74,7 +74,7 @@ void AnalyzeSyntaxNode(SyntaxNodeAnalysisContext context)
             var generator = context.Compilation.GetTypeByMetadataName(generatorAttribute.FullName);
             if (generator == null)
                 // This may be an extender authoring error, but another analyzer should ensure proper 
-                // metadata references exist. Typically, the same nuget package that adds this analyzer 
+                // metadata references exist. Typically, the same NuGet package that adds this analyzer
                 // also adds the required assembly references, so this should never happen anyway.
                 return;
 

src/Stunts/Stunts.Analyzer/UnsupportedNestedTypeAnalyzer.cs

@@ -12,7 +12,7 @@ namespace Stunts
     /// the <see cref="StuntGeneratorAttribute"/> and reports unsupported nested types for 
     /// codegen.
     /// </summary>
-    // TODO: this is a stop-gap meassure until we can figure out why the ImplementInterfaces codefix 
+    // TODO: this is a stop-gap measure until we can figure out why the ImplementInterfaces codefix
     // is not returning any code actions for the CSharpScaffold (maybe VB too?) when the type to 
     // be implemented is a nested interface :(. In the IDE, the code action is properly available after 
     // generating the (non-working, since the interface isn't implemented) mock class. 
@@ -58,7 +58,7 @@ protected UnsupportedNestedTypeAnalyzer(NamingConvention naming, Type generatorA
         }
 
         /// <summary>
-        /// Returns the single descriptor this analyer supports.
+        /// Returns the single descriptor this analyzer supports.
         /// </summary>
         public sealed override ImmutableArray<DiagnosticDescriptor> SupportedDiagnostics => ImmutableArray.Create(descriptor);
 
@@ -77,7 +77,7 @@ void AnalyzeSyntaxNode(SyntaxNodeAnalysisContext context)
             var generator = context.Compilation.GetTypeByMetadataName(generatorAttribute.FullName);
             if (generator == null)
                 // This may be an extender authoring error, but another analyzer should ensure proper 
-                // metadata references exist. Typically, the same nuget package that adds this analyzer 
+                // metadata references exist. Typically, the same NuGet package that adds this analyzer
                 // also adds the required assembly references, so this should never happen anyway.
                 return;
 

src/Stunts/Stunts.Analyzer/ValidateTypesAnalyzer.cs

@@ -33,7 +33,7 @@ protected ValidateTypesAnalyzer(Type generatorAttribute)
 
         /// <summary>
         /// Returns the single <see cref="StuntDiagnostics.BaseTypeNotFirst"/> 
-        /// diagnostic this analyer supports.
+        /// diagnostic this analyzer supports.
         /// </summary>
         public sealed override ImmutableArray<DiagnosticDescriptor> SupportedDiagnostics { get; }
             = ImmutableArray.Create(