From 26fcc1aa1f4ae27cb5f8fed34d8944fe4bc346a8 Mon Sep 17 00:00:00 2001
From: Next Turn <45985406+NextTurn@users.noreply.github.com>
Date: Wed, 9 Oct 2019 23:25:01 +0800
Subject: [PATCH] Move cross-reference into See also section

---
 xml/System.Runtime.InteropServices/SEHException.xml | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/xml/System.Runtime.InteropServices/SEHException.xml b/xml/System.Runtime.InteropServices/SEHException.xml
index 6c58d0f5b09..9b5d9a3edf6 100644
--- a/xml/System.Runtime.InteropServices/SEHException.xml
+++ b/xml/System.Runtime.InteropServices/SEHException.xml
@@ -64,8 +64,6 @@
   
  Any SEH exception that is not automatically mapped to a specific exception is mapped to the <xref:System.Runtime.InteropServices.SEHException> class by default.  
   
- For more information, see [Structured Exception Handling (C/C++)](/cpp/cpp/structured-exception-handling-c-cpp).  
-  
  Note that the <xref:System.Runtime.InteropServices.SEHException> class does not cause unmanaged C++ exception destructors to be called. To ensure that unmanaged C++ exception destructors are called, use the following syntax in the `catch` block.  
   
 ```vb  
@@ -93,6 +91,7 @@ catch(…)
     <altmember cref="T:System.Exception" />
     <related type="Article" href="~/docs/standard/exceptions/index.md">Handling and throwing exceptions in .NET</related>
     <related type="Article" href="https://msdn.microsoft.com/library/610b364b-2761-429d-9c4a-afbc3e66f1b9">How to: Map HRESULTs and Exceptions</related>
+    <related type="Article" href="/cpp/cpp/structured-exception-handling-c-cpp">Structured Exception Handling (C/C++)</related>
   </Docs>
   <Members>
     <MemberGroup MemberName=".ctor">