Merge pull request #38951 from nnpcYvIVl/spelling-15

Spelling fixes

src/EditorFeatures/CSharp/CompleteStatement/CompleteStatementCommandHandler.cs

@@ -391,7 +391,7 @@ private static bool SemicolonIsMissing(SyntaxNode currentNode)
         /// preceding the semicolon. These delimiters are not part of the expression, but they behave like an argument
         /// list for the purposes of identifying relevant places for statement completion:</para>
         /// <list type="bullet">
-        /// <item><description>The closing delimiter is typically inserted by the Automatic Brace Compeltion feature.</description></item>
+        /// <item><description>The closing delimiter is typically inserted by the Automatic Brace Completion feature.</description></item>
         /// <item><description>It is not syntactically valid to place a semicolon <em>directly</em> within the delimiters.</description></item>
         /// </list>
         /// </remarks>

src/EditorFeatures/CSharpTest/ChangeSignature/ChangeSignatureTests.cs

@@ -280,7 +280,7 @@ public class C3
                     }
                     else if (updatedDocument.Name == "C3.cs")
                     {
-                        // shouldn't change unchangable document
+                        // shouldn't change unchangeable document
                         Assert.Contains("bool _x = C1.M(1, 2);", (await updatedDocument.GetTextAsync(CancellationToken.None)).ToString());
                     }
                 }

src/EditorFeatures/CSharpTest/CodeActions/ConvertLinq/ConvertLinqQueryToForEachTests.cs

@@ -1824,7 +1824,7 @@ List<int> M(IEnumerable<int> q)
 }
 ";
 
-            // No support for expresison bodied constructors yet.
+            // No support for expression bodied constructors yet.
             await TestMissingAsync(source);
         }
 

src/EditorFeatures/Core.Wpf/Classification/ClassificationTypeFormatDefinitions.cs

@@ -162,11 +162,11 @@ public SymbolStaticFormatDefinition()
 
         // User Types - * and User Members - * are ordered after Keyword
         // so that, in the case both classifications are applied to the same
-        // span, the styling for the identifier type would be choosen.
+        // span, the styling for the identifier type would be chosen.
 
         // User Types - * and User Members - * are ordered before Symbol - Static 
-        // so that the font styling choosen for static symbols would override the
-        // styling choosen for specific identifier types.
+        // so that the font styling chosen for static symbols would override the
+        // styling chosen for specific identifier types.
         #region User Types - Classes
         [Export(typeof(EditorFormatDefinition))]
         [ClassificationType(ClassificationTypeNames = ClassificationTypeNames.ClassName)]

src/EditorFeatures/Core.Wpf/Options/LegacyEditorConfigDocumentOptionsProvider.DocumentOptions.cs

@@ -35,7 +35,7 @@ public bool TryGetDocumentOption(OptionKey option, out object value)
                     return false;
                 }
 
-                // Temporarly map our old Dictionary<string, object> to a Dictionary<string, string>. This can go away once we either
+                // Temporarily map our old Dictionary<string, object> to a Dictionary<string, string>. This can go away once we either
                 // eliminate the legacy editorconfig support, or we change IEditorConfigStorageLocation.TryGetOption to take
                 // some interface that lets us pass both the Dictionary<string, string> we get from the new system, and the
                 // Dictionary<string, object> from the old system.

src/EditorFeatures/Core.Wpf/QuickInfo/IContentControlService.cs

@@ -19,7 +19,7 @@ internal interface IContentControlService : IWorkspaceService
         /// get <see cref="DisposableToolTip"/> /> from the given <paramref name="textBuffer"/>'s <paramref name="contentSpan"/>
         /// based on given <paramref name="baseDocument"/>
         /// 
-        /// tooltip will show embeded textview which shows code from the content span of the text buffer with the context of the
+        /// tooltip will show embedded textview which shows code from the content span of the text buffer with the context of the
         /// base document
         /// </summary>
         /// <param name="baseDocument">document to be used as a context for the code</param>
@@ -32,7 +32,7 @@ internal interface IContentControlService : IWorkspaceService
         /// <summary>
         /// get <see cref="DisposableToolTip"/> /> from the given <paramref name="textBuffer"/>
         /// 
-        /// tooltip will show embeded textview with whole content from the buffer. if the buffer has associated tags
+        /// tooltip will show embedded textview with whole content from the buffer. if the buffer has associated tags
         /// in its property bag, it will be picked up by taggers associated with the tooltip
         /// </summary>
         DisposableToolTip CreateDisposableToolTip(ITextBuffer textBuffer, object backgroundResourceKey);

src/EditorFeatures/Core.Wpf/Structure/AbstractStructureTaggerProvider.cs

@@ -166,7 +166,7 @@ protected sealed override ITaggerEventSource CreateEventSource(ITextView textVie
             }
             catch (TypeLoadException)
             {
-                // We're targetting a version of the BlockTagging infrastructure in 
+                // We're targeting a version of the BlockTagging infrastructure in 
                 // VS that may not match the version that the user is currently
                 // developing against.  Be resilient to this until everything moves
                 // forward to the right VS version.

src/EditorFeatures/Core/FindUsages/FindUsagesHelpers.cs

@@ -88,7 +88,7 @@ public static async Task<(ISymbol symbol, Project project, ImmutableArray<ISymbo
                 var implementations = await SymbolFinder.FindImplementationsAsync(
                     symbol, solution, cancellationToken: cancellationToken).ConfigureAwait(false);
 
-                // It's important we use a HashSet here -- we may have cases in an inheritence hierarchy where more than one method
+                // It's important we use a HashSet here -- we may have cases in an inheritance hierarchy where more than one method
                 // in an overrides chain implements the same interface method, and we want to duplicate those. The easiest way to do it
                 // is to just use a HashSet.
                 var implementationsAndOverrides = new HashSet<ISymbol>();

src/EditorFeatures/Core/Host/IStreamingFindReferencesPresenter.cs

@@ -95,7 +95,7 @@ internal static class IStreamingFindUsagesPresenterExtensions
                 // Note: we don't need to put this in a finally.  The only time we might not hit
                 // this is if cancellation or another error gets thrown.  In the former case,
                 // that means that a new search has started.  We don't care about telling the
-                // context it has completed.  In the latter case somethign wrong has happened
+                // context it has completed.  In the latter case something wrong has happened
                 // and we don't want to run any more code code in this particular context.
                 await context.OnCompletedAsync().ConfigureAwait(false);
             }

src/EditorFeatures/Core/Implementation/IntelliSense/AsyncCompletion/Helpers.cs

@@ -127,12 +127,12 @@ internal static bool TryGetInitialTriggerLocation(EditorAsyncCompletion.IAsyncCo
         }
 
         // This is a temporarily method to support preference of IntelliCode items comparing to non-IntelliCode items.
-        // We expect that Editor will intorduce this support and we will get rid of relying on the "★" then.
+        // We expect that Editor will introduce this support and we will get rid of relying on the "★" then.
         internal static bool IsPreferredItem(this RoslynCompletionItem completionItem)
             => completionItem.DisplayText.StartsWith("★");
 
         // This is a temporarily method to support preference of IntelliCode items comparing to non-IntelliCode items.
-        // We expect that Editor will intorduce this support and we will get rid of relying on the "★" then.
+        // We expect that Editor will introduce this support and we will get rid of relying on the "★" then.
         internal static bool IsPreferredItem(this VSCompletionItem completionItem)
             => completionItem.DisplayText.StartsWith("★");
     }

src/EditorFeatures/Core/Implementation/KeywordHighlighting/HighlighterViewTaggerProvider.cs

@@ -62,7 +62,7 @@ protected override async Task ProduceTagsAsync(TaggerContext<KeywordHighlightTag
             // It turns out a document might be associated with a project of wrong language, e.g. C# document in a Xaml project. 
             // Even though we couldn't repro the crash above, a fix is made in one of possibly multiple code paths that could cause 
             // us to end up in this situation. 
-            // Regardless of the effective of the fix, we want to enhance the guard aginst such scenario here until an audit in 
+            // Regardless of the effective of the fix, we want to enhance the guard against such scenario here until an audit in 
             // workspace is completed to eliminate the root cause.
             if (document?.SupportsSyntaxTree != true)
             {

src/EditorFeatures/Core/Shared/Preview/PreviewSolutionCrawlerRegistrationService.cs

@@ -33,7 +33,7 @@ public PreviewSolutionCrawlerRegistrationServiceFactory(IDiagnosticAnalyzerServi
 
         public IWorkspaceService CreateService(HostWorkspaceServices workspaceServices)
         {
-            // to make life time management easier, just create new sevice per new workspace
+            // to make life time management easier, just create new service per new workspace
             return new Service(this, workspaceServices.Workspace);
         }
 

src/EditorFeatures/Test/Diagnostics/DiagnosticsSquiggleTaggerProviderTests.cs

@@ -107,7 +107,7 @@ public async Task TaggerProviderCreatedAfterInitialDiagnosticsReported()
         public async Task TestWithMockDiagnosticService_TaggerProviderCreatedBeforeInitialDiagnosticsReported()
         {
             // This test produces diagnostics from a mock service so that we are disconnected from
-            // all teh asynchrony of hte actual async analyzer engine.  If this fails, then the 
+            // all the asynchrony of the actual async analyzer engine.  If this fails, then the 
             // issue is almost certainly in the DiagnosticsSquiggleTaggerProvider code.  If this
             // succeed, but other squiggle tests fail, then it is likely an issue with the 
             // diagnostics engine not actually reporting all diagnostics properly.
@@ -124,7 +124,7 @@ public async Task TestWithMockDiagnosticService_TaggerProviderCreatedBeforeIniti
             // Create the tagger before the first diagnostic event has been fired.
             var tagger = provider.CreateTagger<IErrorTag>(workspace.Documents.First().GetTextBuffer());
 
-            // Now product hte first diagnostic and fire the events.
+            // Now product the first diagnostic and fire the events.
             var tree = await workspace.CurrentSolution.Projects.Single().Documents.Single().GetSyntaxTreeAsync();
             var span = TextSpan.FromBounds(0, 5);
             diagnosticService.CreateDiagnosticAndFireEvents(Location.Create(tree, span));
@@ -143,7 +143,7 @@ public async Task TestWithMockDiagnosticService_TaggerProviderCreatedBeforeIniti
         public async Task TestWithMockDiagnosticService_TaggerProviderCreatedAfterInitialDiagnosticsReported()
         {
             // This test produces diagnostics from a mock service so that we are disconnected from
-            // all teh asynchrony of hte actual async analyzer engine.  If this fails, then the 
+            // all the asynchrony of the actual async analyzer engine.  If this fails, then the 
             // issue is almost certainly in the DiagnosticsSquiggleTaggerProvider code.  If this
             // succeed, but other squiggle tests fail, then it is likely an issue with the 
             // diagnostics engine not actually reporting all diagnostics properly.
@@ -157,7 +157,7 @@ public async Task TestWithMockDiagnosticService_TaggerProviderCreatedAfterInitia
                 workspace.ExportProvider.GetExportedValue<IThreadingContext>(),
                 diagnosticService, workspace.GetService<IForegroundNotificationService>(), listenerProvider);
 
-            // Create and fire the diagnostic events before hte tagger is even made.
+            // Create and fire the diagnostic events before the tagger is even made.
             var tree = await workspace.CurrentSolution.Projects.Single().Documents.Single().GetSyntaxTreeAsync();
             var span = TextSpan.FromBounds(0, 5);
             diagnosticService.CreateDiagnosticAndFireEvents(Location.Create(tree, span));

src/EditorFeatures/Test/EditAndContinue/EditAndContinueWorkspaceServiceTests.cs

@@ -1137,7 +1137,7 @@ public async Task BreakMode_ValidSignificantChange_EmitSuccessful_UpdateDeferred
 
             _mockCompilationOutputsService.Outputs.Add(project.Id, new CompilationOutputFiles(moduleFile.Path, pdbFile.Path));
 
-            // set up an active statement in the first method, so that we can test preservaton of local signature.
+            // set up an active statement in the first method, so that we can test preservation of local signature.
             _mockActiveStatementProvider = new Mock<IActiveStatementProvider>(MockBehavior.Strict);
             _mockActiveStatementProvider.Setup(p => p.GetActiveStatementsAsync(It.IsAny<CancellationToken>())).
                 Returns(Task.FromResult(ImmutableArray.Create(new ActiveStatementDebugInfo(