Spelling Fixes (#43600)

Author: ArieHein

docs/ai/conceptual/rag.md

@@ -1,6 +1,6 @@
 ---
 title: "Integrate Your Data into AI Apps with Retrieval-Augmented Generation"
-description: "Learn how retreival-augmented generation lets you use your data with LLMs to generate better completions in .NET."
+description: "Learn how retrieval-augmented generation lets you use your data with LLMs to generate better completions in .NET."
 author: catbutler
 ms.topic: concept-article #Don't change.
 ms.date: 04/15/2024

docs/ai/quickstarts/quickstart-local-ai.md

@@ -1,6 +1,6 @@
 ---
 title: Quickstart - Connect to and chat with a local AI using .NET and Semantic Kernel
-description: Set up a local AI model and chat with it using a .NET consle app and the Semantic Kernel SDK
+description: Set up a local AI model and chat with it using a .NET console app and the Semantic Kernel SDK
 ms.date: 06/04/2024
 ms.topic: quickstart
 ms.custom: devx-track-dotnet, devx-track-dotnet-ai

docs/ai/tutorials/tutorial-ai-vector-search.md

@@ -12,7 +12,7 @@ ms.author: alexwolf
 
 This tutorial explores integration of the RAG pattern using Open AI models and vector search capabilities in a .NET app. The sample application performs vector searches on custom data stored in Azure Cosmos DB for MongoDB and further refines the responses using generative AI models, such as GPT-35 and GPT-4. In the sections that follow, you'll set up a sample application and explore key code examples that demonstrate these concepts.
 
-## Prerequsites
+## Prerequisites
 
 - [.NET 8.0 installed](https://dotnet.microsoft.com/)
 - An [Azure Account](https://azure.microsoft.com/free)

docs/azure/migration/appcat/interpret-results.md

@@ -39,7 +39,7 @@ Categories section displays a graph with issues grouped by different categories
 
 * **Projects**: the number of projects scanned.
 * **Issues**: the number of unique encounters of a rule that may need to be addressed.
-* **Incidents**: the total number of occurences of all issues found.
+* **Incidents**: the total number of occurrences of all issues found.
 * **Story points**: the estimated effort to fix all of the issues found. This is a relative measure of effort and is not meant to be an exact estimate.
 
 ## Projects view

docs/core/compatibility/serialization/8.0/publishtrimmed.md

@@ -35,7 +35,7 @@ This change ensures that trimmed applications use appropriate defaults. It also
 
 ## Recommended action
 
-To ensure that serialization suceeds, we recommend that you migrate your trimmed applications to use the source generator.
+To ensure that serialization succeeds, we recommend that you migrate your trimmed applications to use the source generator.
 
 However, if you must use reflection, you can revert to the original behavior by explicitly enabling the `JsonSerializerIsReflectionEnabledByDefault` property in your project file:
 

docs/core/deploying/trimming/trim-warnings/il2075.md

@@ -72,7 +72,7 @@ void MyMethod(MyType argument)
 Applying `DynamicallyAccessedMembersAttribute` to a class, interface, or struct, indicates to the linker the members specified may be accessed dynamically on <xref:System.Type> instances returned from calling <xref:System.Object.GetType> on instances of that class, interface, or struct.
 
 > [!NOTE]
-> Applying `DynamicallyAccessedMembersAttribute` to a type definition will "root" all the indicated `DynamicallyAccessedMemberTypes` on the type and all it's derived types (or implementing types when placed on an interface). This means the members will be kept, as well as any metadata referenced by the members. Be careful to use the minimum `DynamicalylAccessedMemberTypes` required, and apply it on the most specific type possible.
+> Applying `DynamicallyAccessedMembersAttribute` to a type definition will "root" all the indicated `DynamicallyAccessedMemberTypes` on the type and all it's derived types (or implementing types when placed on an interface). This means the members will be kept, as well as any metadata referenced by the members. Be careful to use the minimum `DynamicallyAccessedMemberTypes` required, and apply it on the most specific type possible.
 
 ## More information
 

docs/core/deploying/trimming/trim-warnings/il2111.md

@@ -28,7 +28,7 @@ void TestMethod()
 }
 ```
 
-This warning can also be caused by passing a type to a field, paramter, argument, or return value that is annotated with <xref:System.Diagnostics.CodeAnalysis.DynamicallyAccessedMembersAttribute>. <xref:System.Diagnostics.CodeAnalysis.DynamicallyAccessedMembersAttribute> implies reflection access over all of the listed <xref:System.Diagnostics.CodeAnalysis.DynamicallyAccessedMemberTypes>. This means that when a type is passed to a parameter, field, generic parameter, or return value annotated with <xref:System.Diagnostics.CodeAnalysis.DynamicallyAccessedMemberTypes.PublicMethods> .NET tooling assumes that all public methods are accessed via reflection. If a type that contains a method with an annotated parameter or return value is passed to a location annotated with <xref:System.Diagnostics.CodeAnalysis.DynamicallyAccessedMemberTypes.PublicMethods>, then IL2111 will be raised.
+This warning can also be caused by passing a type to a field, paramater, argument, or return value that is annotated with <xref:System.Diagnostics.CodeAnalysis.DynamicallyAccessedMembersAttribute>. <xref:System.Diagnostics.CodeAnalysis.DynamicallyAccessedMembersAttribute> implies reflection access over all of the listed <xref:System.Diagnostics.CodeAnalysis.DynamicallyAccessedMemberTypes>. This means that when a type is passed to a parameter, field, generic parameter, or return value annotated with <xref:System.Diagnostics.CodeAnalysis.DynamicallyAccessedMemberTypes.PublicMethods> .NET tooling assumes that all public methods are accessed via reflection. If a type that contains a method with an annotated parameter or return value is passed to a location annotated with <xref:System.Diagnostics.CodeAnalysis.DynamicallyAccessedMemberTypes.PublicMethods>, then IL2111 will be raised.
 
 ```csharp
 class TypeWithAnnotatedMethod

docs/core/diagnostics/available-counters.md

@@ -103,7 +103,7 @@ The following counters are published by the HTTP stack and are maintained in [_H
 
 ## System.Net.NameResolution counters
 
-The following counters track metrics related to DNS lookups and are mantained in [_NameResolutionTelemetry.cs_](https://github.com/dotnet/runtime/blob/main/src/libraries/System.Net.NameResolution/src/System/Net/NameResolutionTelemetry.cs).
+The following counters track metrics related to DNS lookups and are maintained in [_NameResolutionTelemetry.cs_](https://github.com/dotnet/runtime/blob/main/src/libraries/System.Net.NameResolution/src/System/Net/NameResolutionTelemetry.cs).
 
 | Counter | Description | First available in |
 |--|--|--|
@@ -113,7 +113,7 @@ The following counters track metrics related to DNS lookups and are mantained in
 
 ## System.Net.Security counters
 
-The following counters track metrics related to the Transport Layer Security protocol and are mantained in [_NetSecurityTelemetry.cs_](https://github.com/dotnet/runtime/blob/main/src/libraries/System.Net.Security/src/System/Net/Security/NetSecurityTelemetry.cs).
+The following counters track metrics related to the Transport Layer Security protocol and are maintained in [_NetSecurityTelemetry.cs_](https://github.com/dotnet/runtime/blob/main/src/libraries/System.Net.Security/src/System/Net/Security/NetSecurityTelemetry.cs).
 
 | Counter | Description | First available in |
 |--|--|--|
@@ -134,7 +134,7 @@ The following counters track metrics related to the Transport Layer Security pro
 
 ## System.Net.Sockets counters
 
-The following counters track metrics related to <xref:System.Net.Sockets.Socket> and are mantained in [_SocketsTelemetry_](https://github.com/dotnet/runtime/blob/main/src/libraries/System.Net.Sockets/src/System/Net/Sockets/SocketsTelemetry.cs).
+The following counters track metrics related to <xref:System.Net.Sockets.Socket> and are maintained in [_SocketsTelemetry_](https://github.com/dotnet/runtime/blob/main/src/libraries/System.Net.Sockets/src/System/Net/Sockets/SocketsTelemetry.cs).
 
 | Counter | Description | First available in |
 |--|--|--|

docs/core/diagnostics/diagnostic-resource-monitoring.md

@@ -25,7 +25,7 @@ The preceding code:
 - Gets an instance of the <xref:Microsoft.Extensions.Diagnostics.ResourceMonitoring.IResourceMonitor> interface from the `ServiceProvider` instance.
 
 > [!IMPORTANT]
-> The <xref:Microsoft.Extensions.Diagnostics.ResourceMonitoring?displayProperty=fullName> package assumes that the consumer will register logging providers with the `Microsoft.Extensions.Logging` package. If you don't register logging, the call to `AddResourceMonitoring` will throw an exception. Furthemore, you can enable internal library logging by configuring the [`Debug`](xref:Microsoft.Extensions.Logging.LogLevel.Debug) log level for the `Microsoft.Extensions.Diagnostics.ResourceMonitoring` category as per the [guide](../extensions/logging.md#log-category).
+> The <xref:Microsoft.Extensions.Diagnostics.ResourceMonitoring?displayProperty=fullName> package assumes that the consumer will register logging providers with the `Microsoft.Extensions.Logging` package. If you don't register logging, the call to `AddResourceMonitoring` will throw an exception. Furthermore, you can enable internal library logging by configuring the [`Debug`](xref:Microsoft.Extensions.Logging.LogLevel.Debug) log level for the `Microsoft.Extensions.Diagnostics.ResourceMonitoring` category as per the [guide](../extensions/logging.md#log-category).
 
 At this point, with the `IResourceMonitor` implementation you'll ask for resource utilization with the <xref:Microsoft.Extensions.Diagnostics.ResourceMonitoring.IResourceMonitor.GetUtilization%2A?displayProperty=nameWithType> method. The `GetUtilization` method returns a <xref:Microsoft.Extensions.Diagnostics.ResourceMonitoring.ResourceUtilization> instance that contains the following information:
 

docs/core/diagnostics/logging-tracing.md

@@ -46,7 +46,7 @@ The <xref:System.Console?displayProperty=nameWithType> class has the <xref:Syste
 
 Logging can either be structured or unstructured:
 
-- Unstructured: Log entries are encoded as free-form text that humans can read but it is difficult to programatically parse and query.
+- Unstructured: Log entries are encoded as free-form text that humans can read but it is difficult to programmatically parse and query.
 - Structured: Log entries have a well defined schema and can be encoded in different binary and textual formats. These logs are designed to be machine translatable and queryable so that both humans and automated systems can work with them easily.
 
 Good structured logging APIs can offer more functionality and performance with only a small increase in usage complexity.