From df4bfde13856a3a4ede96a12e9d6efa16ff81910 Mon Sep 17 00:00:00 2001
From: Arvind Ganesh <newton.arvind@gmail.com>
Date: Sun, 9 Mar 2025 16:50:01 +0530
Subject: [PATCH] Corrected wording for ImportedFromTypeLibAttribute

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

diff --git a/xml/System.Runtime.InteropServices/ImportedFromTypeLibAttribute.xml b/xml/System.Runtime.InteropServices/ImportedFromTypeLibAttribute.xml
index 63a2aee8e09..c1144eb82b3 100644
--- a/xml/System.Runtime.InteropServices/ImportedFromTypeLibAttribute.xml
+++ b/xml/System.Runtime.InteropServices/ImportedFromTypeLibAttribute.xml
@@ -60,7 +60,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- You can apply this attribute to assemblies, although the [Tlbimp.exe (Type Library Importer)](/dotnet/framework/tools/tlbimp-exe-type-library-importer) typically applies it for you when it a type library.  
+ You can apply this attribute to assemblies, although the [Tlbimp.exe (Type Library Importer)](/dotnet/framework/tools/tlbimp-exe-type-library-importer) typically applies it for you when it imports a type library.  
   
  The primary use of the attribute is to capture the original source of the type information. For example, you can import A.tlb as an interop assembly called A.dll and have assembly B.dll reference A.dll. When you export B.dll to B.tlb, this attribute causes the references in B.tlb that point to A.dll to point instead to A.tlb. This should not be confused with the <xref:System.Runtime.InteropServices.ComImportAttribute>, which specifies that an individual type is implemented in COM.