Changed a link to the more proper xref-based version.

Author: DennisLee-DennisLee

docs/vsto/development-best-practices-for-com-vsto-and-vba-add-ins-in-office.md

@@ -33,7 +33,7 @@ If your solution uses .NET 4.0 or later, use embedded interop types (NoPIA) inst
 If your solution uses an earlier version of .NET, we recommend that you update your solution to use .NET 4.0 or later. Using .NET 4.0 or later reduces runtime prerequisites on newer versions of Windows.
 
 ## Avoid depending on specific Office versions  
-If your solution uses functionality that is only available in newer versions of Office, verify that the capability exists (if possible, at the feature level) at runtime (for example, using exception handling or by checking the version). Validate minimum versions, rather than specific versions, using supported APIs in the object model, such as the [Application.Version property](/dotnet/api/microsoft.office.interop.excel._application.version#Microsoft_Office_Interop_Excel__Application_Version). We don’t recommend that you rely on Office binary metadata, installation paths, or registry keys because these can change between installations, environments, and versions.
+If your solution uses functionality that is only available in newer versions of Office, verify that the capability exists (if possible, at the feature level) at runtime (for example, using exception handling or by checking the version). Validate minimum versions, rather than specific versions, using supported APIs in the object model, such as the [Application.Version property](<xref:Microsoft.Office.Interop.Excel._Application.Version%2A>). We don’t recommend that you rely on Office binary metadata, installation paths, or registry keys because these can change between installations, environments, and versions.
 
 ## Enable both 32-bit and 64-bit Office usage   
 Your default build target should support both 32-bit (x86) and 64-bit (x64), unless your solution depends on libraries that are only available for a specific bitness. The 64-bit version of Office is increasing in adoption, especially in big data environments. Supporting both 32-bit and 64-bit makes it easier for your users to transition between 32-bit and 64-bit versions of Office.