Fix API references in reflection breaking change documentation

Co-authored-by: gewarren <[email protected]>

Author: Copilot

docs/core/compatibility/reflection/10.0/ireflect-damt-annotations.md

@@ -7,19 +7,19 @@ ai-usage: ai-generated
 
 # Replace DAMT.All with more restricted annotation on InvokeMember/FindMembers/DeclaredMembers
 
-Starting in .NET 10, the <xref:System.Reflection> APIs <xref:System.Reflection.IReflect.InvokeMember%2A>, <xref:System.Reflection.IReflect.GetMembers%2A>, and <xref:System.Reflection.TypeInfo.DeclaredMembers?displayProperty=nameWithType> have been updated to use more restricted annotations instead of <xref:System.Diagnostics.CodeAnalysis.DynamicallyAccessedMemberTypes.All?displayProperty=nameWithType>. This change affects scenarios where developers implement the <xref:System.Reflection.IReflect> interface or derive from <xref:System.Reflection.TypeInfo>. The previous use of `DAMT.All` was overly permissive and could lead to unintended behavior, such as capturing interface methods implemented by a class or generating warnings due to unsafe reflection calls.
+Starting in .NET 10, the <xref:System.Reflection> APIs <xref:System.Reflection.IReflect.InvokeMember%2A>, <xref:System.Type.FindMembers%2A?displayProperty=nameWithType>, and <xref:System.Reflection.TypeInfo.DeclaredMembers?displayProperty=nameWithType> have been updated to use more restricted annotations instead of <xref:System.Diagnostics.CodeAnalysis.DynamicallyAccessedMemberTypes.All?displayProperty=nameWithType>. This change affects scenarios where developers implement the <xref:System.Reflection.IReflect> interface or derive from <xref:System.Reflection.TypeInfo>. The previous use of `DAMT.All` was overly permissive and could lead to unintended behavior, such as capturing interface methods implemented by a class or generating warnings due to unsafe reflection calls.
 
 ## Version introduced
 
 .NET 10 Preview 1
 
 ## Previous behavior
 
-The <xref:System.Reflection.IReflect.InvokeMember%2A>, <xref:System.Reflection.IReflect.GetMembers%2A>, and <xref:System.Reflection.TypeInfo.DeclaredMembers?displayProperty=nameWithType> APIs used the <xref:System.Diagnostics.CodeAnalysis.DynamicallyAccessedMemberTypes.All?displayProperty=nameWithType> annotation, which was overly permissive. This could result in capturing additional members, such as interface methods implemented by a class, and potentially cause runtime warnings or unsafe reflection calls.
+The <xref:System.Reflection.IReflect.InvokeMember%2A>, <xref:System.Type.FindMembers%2A?displayProperty=nameWithType>, and <xref:System.Reflection.TypeInfo.DeclaredMembers?displayProperty=nameWithType> APIs used the <xref:System.Diagnostics.CodeAnalysis.DynamicallyAccessedMemberTypes.All?displayProperty=nameWithType> annotation, which was overly permissive. This could result in capturing additional members, such as interface methods implemented by a class, and potentially cause runtime warnings or unsafe reflection calls.
 
 ## New behavior
 
-The <xref:System.Reflection.IReflect.InvokeMember%2A>, <xref:System.Reflection.IReflect.GetMembers%2A>, and <xref:System.Reflection.TypeInfo.DeclaredMembers?displayProperty=nameWithType> APIs now use more restricted annotations, which provide better control over the members captured during reflection. Developers implementing <xref:System.Reflection.IReflect> or deriving from <xref:System.Reflection.TypeInfo> must update their annotations to match the new behavior.
+The <xref:System.Reflection.IReflect.InvokeMember%2A>, <xref:System.Type.FindMembers%2A?displayProperty=nameWithType>, and <xref:System.Reflection.TypeInfo.DeclaredMembers?displayProperty=nameWithType> APIs now use more restricted annotations, which provide better control over the members captured during reflection. Developers implementing <xref:System.Reflection.IReflect> or deriving from <xref:System.Reflection.TypeInfo> must update their annotations to match the new behavior.
 
 The following code snippet shows an example of the required annotation for implementing <xref:System.Reflection.IReflect.InvokeMember%2A>:
 
@@ -47,5 +47,5 @@ For more information on `DynamicallyAccessedMembers` annotations and their usage
 ## Affected APIs
 
 - <xref:System.Reflection.IReflect.InvokeMember(System.String,System.Reflection.BindingFlags,System.Reflection.Binder,System.Object,System.Object[],System.Reflection.ParameterModifier[],System.Globalization.CultureInfo,System.String[])?displayProperty=fullName>
-- <xref:System.Reflection.IReflect.GetMembers(System.Reflection.BindingFlags)?displayProperty=fullName>
+- <xref:System.Type.FindMembers(System.Reflection.MemberTypes,System.Reflection.BindingFlags,System.Reflection.MemberFilter,System.Object)?displayProperty=fullName>
 - <xref:System.Reflection.TypeInfo.DeclaredMembers?displayProperty=fullName>