Apply suggestions from code review

Co-authored-by: Copilot <[email protected]>

Author: davidwengier

src/Razor/src/Microsoft.CodeAnalysis.Razor.Workspaces/Formatting/Passes/CSharpFormattingPass.CSharpDocumentGenerator.cs

@@ -611,7 +611,7 @@ public override LineInfo VisitMarkupTransition(MarkupTransitionSyntax node)
                 //          }
                 //     </div>;
                 //
-                // If we convert that to C# the like we normally do, we end up with statements in a C# context where only
+                // If we convert that to C# the way we normally do, we end up with statements in a C# context where only
                 // expressions are valid. To avoid that, we need to emit C# such that we can be sure we're in a context
                 // where statements are valid. To do this we emit a block bodied lambda expression. Ironically this whole
                 // formatting engine arguably exists because the compiler loves to emit lambda expressions, but they're
@@ -629,7 +629,7 @@ public override LineInfo VisitMarkupTransition(MarkupTransitionSyntax node)
 
                 // Roslyn may move the opening brace to the next line, depending on its options. Unlike with code block
                 // formatting where we put the opening brace on the next line ourselves (and Roslyn might bring it back)
-                // if we do that for lambdas, Roslyn wont' adjust the opening brace position at all. See, told you lambdas
+                // if we do that for lambdas, Roslyn won't adjust the opening brace position at all. See, told you lambdas
                 // were annoying to format.
                 _builder.AppendLine("() => {");
                 return CreateLineInfo(skipNextLineIfBrace: true);

src/Razor/src/Microsoft.CodeAnalysis.Razor.Workspaces/Formatting/Passes/CSharpFormattingPass.cs

@@ -147,7 +147,7 @@ public async Task<ImmutableArray<TextChange>> ExecuteAsync(FormattingContext con
             else if (lineInfo.SkipNextLineIfBrace)
             {
                 // If the next line is a brace, we skip it. This is used to skip the opening brace of a class
-                // that we insert, but Roslyn settings might place on the same like as the class declaration,
+                // that we insert, but Roslyn settings might place on the same line as the class declaration,
                 // or skip the opening brace of a lambda definition we insert, but Roslyn might place it on the
                 // next line. In that case, we can't place it on the next line ourselves because Roslyn doesn't
                 // adjust the indentation of opening braces of lambdas in that scenario.