From bc175b499dd6f918aedeab747a0cba66dfcf88c9 Mon Sep 17 00:00:00 2001
From: Vitek Karas <10670590+vitek-karas@users.noreply.github.com>
Date: Thu, 5 Dec 2024 18:58:31 +0100
Subject: [PATCH] UnmanagedFunctionPointer doesn't require field names to be
 functional. Fixing the doc to just state that the fields are optional.
 (#10724)

---
 .../UnmanagedFunctionPointerAttribute.xml                       | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xml/System.Runtime.InteropServices/UnmanagedFunctionPointerAttribute.xml b/xml/System.Runtime.InteropServices/UnmanagedFunctionPointerAttribute.xml
index 8608931bb9e..28f03058dfc 100644
--- a/xml/System.Runtime.InteropServices/UnmanagedFunctionPointerAttribute.xml
+++ b/xml/System.Runtime.InteropServices/UnmanagedFunctionPointerAttribute.xml
@@ -61,7 +61,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The fields of the <xref:System.Runtime.InteropServices.UnmanagedFunctionPointerAttribute> attribute control various aspects of the transition of a delegate to an unmanaged function pointer, and are the same as the fields with identical names in the <xref:System.Runtime.InteropServices.DllImportAttribute> attribute. These fields are optional, but if you do not specify a field name, <xref:System.Runtime.InteropServices.UnmanagedFunctionPointerAttribute> is ignored.  
+ The fields of the <xref:System.Runtime.InteropServices.UnmanagedFunctionPointerAttribute> attribute control various aspects of the transition of a delegate to an unmanaged function pointer, and are the same as the fields with identical names in the <xref:System.Runtime.InteropServices.DllImportAttribute> attribute. These fields are optional.  
   
  For more information about using attributes, see [Attributes](/dotnet/standard/attributes/).