Fix typos

Fixes #50184

Change-Id: If17f838d932171e30ef92d1bda8d4918e7e08a8f
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/263622
Reviewed-by: Lasse Nielsen <lrn@google.com>
Reviewed-by: Brian Wilkerson <brianwilkerson@google.com>
Commit-Queue: Brian Wilkerson <brianwilkerson@google.com>

pkg/analysis_server/test/lsp/call_hierarchy_test.dart

@@ -1,5 +1,5 @@
-// Copyright (c) 2022, the Dart project authors. Please see the FooUTHORS file
+// Copyright (c) 2022, the Dart project authors. Please see the AUTHORS file
-// for details. Fooll rights reserved. Use of this source code is governed by a
+// for details. All rights reserved. Use of this source code is governed by a
 // BSD-style license that can be found in the LICENSE file.
 
 import 'package:analysis_server/lsp_protocol/protocol_generated.dart';

pkg/analyzer/CHANGELOG.md

@@ -772,7 +772,7 @@
   `CompileTimeErrorCode.NOT_ENOUGH_POSITIONAL_ARGUMENTS`.
 
 ## 0.38.1
-* LinterVistor support for extension method AST nodes.
+* LinterVisitor support for extension method AST nodes.
 
 ## 0.38.0
 * The deprecated method `AstFactory.compilationUnit2` has been removed.  Clients
@@ -834,7 +834,7 @@
 * Removed methods `AstVisitor.ForStatement2`, `ListLiteral.elements2`,
   `SetOrMapLiteral.elements2`, `AstFactory.forStatement2`, and
   `NodeLintRegistry.addForStatement2`, as well as class `ForStatement2`.  Use
-  the variants with out the "2" suffix instead.
+  the variants without the "2" suffix instead.
 * Changed the signature and behavior of `parseFile` to match `parseFile2`.
   Clients that switched to using `parseFile2` when `parseFile` was deprecated
   should now switch back to `parseFile`.

pkg/analyzer/test/verify_diagnostics_test.dart

@@ -41,7 +41,7 @@ class DocumentationValidator {
     // The mock SDK doesn't define any internal libraries.
     'CompileTimeErrorCode.EXPORT_INTERNAL_LIBRARY',
     // Has code in the example section that needs to be skipped (because it's
-    // part of the explanitory text not part of the example), but there's
+    // part of the explanatory text not part of the example), but there's
     // currently no way to do that.
     'CompileTimeErrorCode.INVALID_IMPLEMENTATION_OVERRIDE',
     // Produces two diagnostics when it should only produce one. We could get

pkg/kernel/lib/text/ast_to_text.dart

@@ -1056,13 +1056,13 @@ class Printer extends Visitor<void> with VisitorVoidMixin {
       startHighlight(node);
     }
     if (showOffsets) writeWord("[${node.fileOffset}]");
-    bool needsParenteses = false;
+    bool needsParentheses = false;
     if (minimumPrecedence != null && getPrecedence(node) < minimumPrecedence) {
-      needsParenteses = true;
+      needsParentheses = true;
       writeSymbol('(');
     }
     writeNode(node);
-    if (needsParenteses) {
+    if (needsParentheses) {
       writeSymbol(')');
     }
     if (highlight) {

pkg/kernel/problems.md

@@ -17,13 +17,13 @@ problem-texts as reported by the compiler.
 `severity`: An integer representing severity. This should match the index in
 `package:_fe_analyzer_shared/src/messages/severity.dart`.
 
-`uri`: A possibly null uri that this problems relates to. This is the main uri.
+`uri`: A possibly null uri that this problem relates to. This is the main uri.
 Normally this is not null (but it can be).
 
 `involvedFiles`: A possibly null list of uris involved in this message.
 Normally this is null.
 
-`codeName`: A string identifing the specific error message.
+`codeName`: A string identifying the specific error message.
 
 These values are subject to change, but this file will be updated along with any
 such changes. On the code-side these are defined in

pkg/telemetry/README.md

@@ -47,5 +47,5 @@ main() {
 }
 ```
 
-Crash reports will only be sent if the cooresponding [Analytics] object is
+Crash reports will only be sent if the corresponding [Analytics] object is
 configured to send analytics.

pkg/testing/README.md

@@ -195,7 +195,7 @@ The `Dart` suite makes certain assumptions about the tests it runs.
 
  * An asynchronous test returns a `Future` from its `main`.
 
- * Tests manages global state.
+ * Tests manage global state.
 
 All tests are imported into the same program as individual libraries, which is why they all must use the same `.packages` file. The tests aren't concatenated, so they have the lexical scope you'd normally expect from a Dart library.
 

pkg/testing/lib/src/chain.dart

@@ -342,7 +342,7 @@ abstract class Step<I, O, C extends ChainContext> {
   /// the next step is executed by the now-ending step.
   ///
   /// When isAsync is false each step returns a future which is awaited,
-  /// effectivly meaning that only a single test is run at a time.
+  /// effectively meaning that only a single test is run at a time.
   ///
   /// When isAsync is true that step doesn't return a future (but adds it's
   /// future to a list which is awaited before sending an 'entire suite done'

pkg/testing/lib/src/expectation.dart

@@ -98,7 +98,7 @@ class ExpectationSet {
             break;
 
           default:
-            throw "Unrecoginized key: '$key' in '$map'.";
+            throw "Unrecognized key: '$key' in '$map'.";
         }
       });
       if (name == null) {