Merge pull request #4412 from ktarbet/patch-1

fix a broken link

Author: ktoliver

docs/debugger/how-can-i-find-out-if-my-pointers-corrupt-a-memory-address-q.md

@@ -30,7 +30,7 @@ ms.workload:
 
 #### Check for heap corruption
 
-- Most memory corruption is actually due to heap corruption. Try using the Global Flags Utility (gflags.exe) or pageheap.exe. See [http://support.microsoft.com/default.aspx?scid=kb;en-us;286470](http://support.microsoft.com/default.aspx?scid=kb;en-us;286470).
+- Most memory corruption is actually due to heap corruption. Try using the Global Flags Utility (gflags.exe) or pageheap.exe. See [https://docs.microsoft.com/windows-hardware/drivers/debugger/gflags-and-pageheap](/windows-hardware/drivers/debugger/gflags-and-pageheap).
 
 #### To find where the memory address is modified
 
@@ -40,4 +40,4 @@ ms.workload:
 
 ## See also
 - [Debugging Native Code FAQs](../debugger/debugging-native-code-faqs.md)
-- [Debugging Native Code](../debugger/debugging-native-code.md)
+- [Debugging Native Code](../debugger/debugging-native-code.md)