From 8fe00c0d714453125f495a0edc0504f6fecc852e Mon Sep 17 00:00:00 2001
From: Genevieve Warren <24882762+gewarren@users.noreply.github.com>
Date: Mon, 21 Jul 2025 13:39:01 -0700
Subject: [PATCH] Fix grammar

---
 docs/standard/native-interop/type-marshalling.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/standard/native-interop/type-marshalling.md b/docs/standard/native-interop/type-marshalling.md
index 13f94986fff94..4bce686fbf5da 100644
--- a/docs/standard/native-interop/type-marshalling.md
+++ b/docs/standard/native-interop/type-marshalling.md
@@ -26,7 +26,7 @@ If you apply the [`System.Runtime.CompilerServices.DisableRuntimeMarshallingAttr
 
 Generally, the runtime tries to do the "right thing" when marshalling to require the least amount of work from you. The following tables describe how each type is marshalled by default when used in a parameter or field. The C99/C++11 fixed-width integer and character types are used to ensure that the following table is correct for all platforms. You can use any native type that has the same alignment and size requirements as these types.
 
-This first table describes the mappings for various types for whom the marshalling is the same for both P/Invoke and field marshalling.
+This first table describes the mappings for types for which the marshalling is the same for both P/Invoke and field marshalling.
 
 | C# keyword  | .NET Type        | Native Type             |
 |-------------|------------------|-------------------------|