Fix --brokenlink-- and other problem links (MicrosoftDocs#564)

* Fix conveniently labeled broken links

* Fix some SDK links

* REmove links to non-existent topic

* Fix more janky links in CRT

Author: Colin Robertson

docs/atl-mfc-shared/atl-mfc-shared-classes.md

@@ -31,9 +31,5 @@ These utility classes can be used in any native C++ project without requiring an
  [Microsoft Foundation Class Library (MFC) Reference](../mfc/mfc-desktop-applications.md)  
  Provides reference material for the MFC Library, a set of classes in that constitute an application framework, which is the framework of an application written for the Windows API.  
 
- [Visual C++ Libraries](http://msdn.microsoft.com/en-us/fec23c40-10c0-4857-9cdc-33a3b99b30ae)  
- Provides links to the various libraries provided with Visual C++, including ATL, MFC, OLE DB Templates, the C run-time library, and the C++ Standard Library.  
-  
  [Debugging](/visualstudio/debugger/debugging-in-visual-studio)  
  Provides links to using the Visual Studio debugger to correct logic errors in your application or stored procedures.
-

docs/atl/atl-com-desktop-components.md

@@ -59,7 +59,3 @@ The ATL Reference documents the Active Template Library (ATL), a set of template
 
  [OLE DB Templates](../data/oledb/ole-db-templates.md)  
  Provides reference material for the OLE DB consumer and provider templates, a set of template classes that implement many commonly used OLE DB interfaces.  
-  
- [Visual C++ Libraries](http://msdn.microsoft.com/en-us/fec23c40-10c0-4857-9cdc-33a3b99b30ae)  
- Provides links to the various libraries provided with Visual C++, including ATL, MFC, OLE DB Templates, the C run-time library, and the C++ Standard Library.
-

docs/c-runtime-library/c-run-time-library-reference.md

@@ -54,11 +54,5 @@ The Microsoft run-time library provides routines for programming for the Microso
  [DLLs and Visual C++ run-time library behavior](../build/run-time-library-behavior.md)  
  Discusses the entry point and startup code used for a DLL.  
 
- [Visual C++ Libraries](http://msdn.microsoft.com/en-us/fec23c40-10c0-4857-9cdc-33a3b99b30ae)  
- Provides links to the various libraries provided with Visual C++, including ATL, MFC, OLE DB Templates, the C run-time library, and the C++ Standard Library.  
-  
  [Debugging](/visualstudio/debugger/debugging-in-visual-studio)  
  Provides links to using the Visual Studio debugger to correct logic errors in your application or stored procedures.  
-  
-## See Also  
- [Visual C++ Libraries Reference](http://msdn.microsoft.com/en-us/fec23c40-10c0-4857-9cdc-33a3b99b30ae)

docs/c-runtime-library/compatibility.md

@@ -26,7 +26,7 @@ The Universal C Run-Time Library (UCRT) supports most of the C standard library
 
  Certain functions in the standard C library have a history of unsafe usage, because of misused parameters and unchecked buffers. These functions are often the source of security issues in code. Microsoft created a set of safer versions of these functions that verify parameter usage and invoke the invalid parameter handler when an issue is detected at runtime.  By default, the Visual C++ compiler issues a deprecation warning when a function is used that has a safer variant available. When you compile your code as C++ , you can define `_CRT_SECURE_CPP_OVERLOAD_STANDARD_NAMES` as 1 to eliminate most warnings. This uses template overloads to call the safer variants while maintaining portable source code. To suppress the warning, define `_CRT_SECURE_NO_WARNINGS` before including any headers in code that uses these functions. For more information, see [Security Features in the CRT](../c-runtime-library/security-features-in-the-crt.md).  
 
- Except as noted within the documentation for specific functions, the UCRT is compatible with the Windows API.  Certain functions are not supported in Windows 8 Store apps or in Universal Windows apps on Windows 10. These functions are listed in [CRT functions not supported with /ZW](http://msdn.microsoft.com/library/windows/apps/jj606124.aspx), which enumerates the functions not supported by the [Windows Runtime](http://msdn.microsoft.com/en-us/9a1a18b8-9802-4ec5-b9de-0d2dfdf414e9).  
+ Except as noted within the documentation for specific functions, the UCRT is compatible with the Windows API.  Certain functions are not supported in Windows 8 Store apps or in Universal Windows Platform (UWP) apps on Windows 10. These functions are listed in [CRT functions not supported in Universal Windows Platform apps](../cppcx/crt-functions-not-supported-in-universal-windows-platform-apps.md), which enumerates the functions not supported by the Windows Runtime and [UWP](/uwp).  
 
 ## Related Articles  
 

docs/c-runtime-library/reference/crtcheckmemory.md

@@ -58,7 +58,7 @@ _ASSERTE( _CrtCheckMemory( ) );
  Debug versions of [C run-time libraries](../../c-runtime-library/crt-library-features.md) only.  
 
 ## Example  
- For a sample of how to use `_CrtCheckMemory`, see [crt_dbg1](http://msdn.microsoft.com/en-us/17b4b20c-e849-48f5-8eb5-dca6509cbaf9).  
+ For a sample of how to use `_CrtCheckMemory`, see [crt_dbg1](https://github.com/Microsoft/VCSamples/tree/master/VC2010Samples/crt/crt_dbg1).  
 
 ## See Also  
  [Debug Routines](../../c-runtime-library/debug-routines.md)   

docs/c-runtime-library/reference/crtdbgreport-crtdbgreportw.md

@@ -114,7 +114,7 @@ int main(int argc, char *argv[]) {
 }  
 ```  
 
- See [crt_dbg2](http://msdn.microsoft.com/en-us/21e1346a-6a17-4f57-b275-c76813089167) for an example of how to change the report function.  
+ See [crt_dbg2](https://github.com/Microsoft/VCSamples/tree/master/VC2010Samples/crt/crt_dbg2) for an example of how to change the report function.  
 
 ## See Also  
  [Debug Routines](../../c-runtime-library/debug-routines.md)   

docs/c-runtime-library/reference/crtdumpmemoryleaks.md

@@ -56,7 +56,7 @@ int _CrtDumpMemoryLeaks( void );
  Debug versions of [C run-time libraries](../../c-runtime-library/crt-library-features.md) only.  
 
 ## Example  
- For a sample of how to use `_CrtDumpMemoryLeaks`, see [crt_dbg1](http://msdn.microsoft.com/en-us/17b4b20c-e849-48f5-8eb5-dca6509cbaf9).  
+ For a sample of how to use `_CrtDumpMemoryLeaks`, see [crt_dbg1](https://github.com/Microsoft/VCSamples/tree/master/VC2010Samples/crt/crt_dbg1).  
 
 ## See Also  
  [Debug Routines](../../c-runtime-library/debug-routines.md)

docs/c-runtime-library/reference/crtgetreporthook.md

@@ -49,7 +49,7 @@ _CRT_REPORT_HOOK _CrtGetReportHook( void );
  Debug versions of [C run-time libraries](../../c-runtime-library/crt-library-features.md) only.  
 
 ## Example  
- For a sample of how to use `_CrtSetReportHook`, see [report](http://msdn.microsoft.com/en-us/f6e08c30-6bd9-459a-830a-56deec0d2051).  
+ For a sample of how to use `_CrtSetReportHook`, see [report](https://github.com/Microsoft/VCSamples/tree/master/VC2010Samples/crt/report).  
 
 ## See Also  
  [Debug Routines](../../c-runtime-library/debug-routines.md)   

docs/c-runtime-library/reference/crtmemdumpallobjectssince.md

@@ -57,7 +57,7 @@ Dumps information about objects in the heap from the start of program execution
  Debug versions of [C run-time libraries](../../c-runtime-library/crt-library-features.md) only.  
 
 ## Example  
- For a sample of how to use `_CrtMemDumpAllObjectsSince`, see [crt_dbg2](http://msdn.microsoft.com/en-us/21e1346a-6a17-4f57-b275-c76813089167).  
+ For a sample of how to use `_CrtMemDumpAllObjectsSince`, see [crt_dbg2](https://github.com/Microsoft/VCSamples/tree/master/VC2010Samples/crt/crt_dbg2).  
 
 ## See Also  
  [Debug Routines](../../c-runtime-library/debug-routines.md)   

docs/c-runtime-library/reference/crtsetallochook.md

@@ -76,7 +76,7 @@ lineNumber);
  Debug versions of [C run-time libraries](../../c-runtime-library/crt-library-features.md) only.  
 
 ## Example  
- For a sample of how to use `_CrtSetAllocHook`, see [crt_dbg2](http://msdn.microsoft.com/en-us/21e1346a-6a17-4f57-b275-c76813089167).  
+ For a sample of how to use `_CrtSetAllocHook`, see [crt_dbg2](https://github.com/Microsoft/VCSamples/tree/master/VC2010Samples/crt/crt_dbg2).  
 
 ## See Also  
  [Debug Routines](../../c-runtime-library/debug-routines.md)   

docs/c-runtime-library/reference/expm1-expm1f-expm1l.md

@@ -63,5 +63,5 @@ long double expm1l(
 
 ## See Also  
  [Floating-Point Support](../../c-runtime-library/floating-point-support.md)   
- [exp2, exp2f, exp2l](http://msdn.microsoft.com/en-us/a7974629-be1e-4196-a562-6624a0732003)   
+ [exp2, exp2f, exp2l](exp2-exp2f-exp2l.md)   
  [pow, powf, powl](../../c-runtime-library/reference/pow-powf-powl.md)

docs/c-runtime-library/reference/free-dbg.md

@@ -57,7 +57,7 @@ void _free_dbg(
  For more compatibility information, see [Compatibility](../../c-runtime-library/compatibility.md) in the Introduction.  
 
 ## Example  
- For a sample of how to use `_free_dbg`, see [crt_dbg2](http://msdn.microsoft.com/en-us/21e1346a-6a17-4f57-b275-c76813089167).  
+ For a sample of how to use `_free_dbg`, see [crt_dbg2](https://github.com/Microsoft/VCSamples/tree/master/VC2010Samples/crt/crt_dbg2).  
 
 ## See Also  
  [Debug Routines](../../c-runtime-library/debug-routines.md)   

docs/c-runtime-library/reference/lround-lroundf-lroundl-llround-llroundf-llroundl.md

@@ -121,7 +121,7 @@ lroundl(-2.500000) is -4
  [ceil, ceilf, ceill](../../c-runtime-library/reference/ceil-ceilf-ceill.md)   
  [floor, floorf, floorl](../../c-runtime-library/reference/floor-floorf-floorl.md)   
  [fmod, fmodf](../../c-runtime-library/reference/fmod-fmodf.md)   
- [lrint, lrintf, lrintl, llrint, llrintf, llrintl](http://msdn.microsoft.com/en-us/312fd869-a9c0-4107-bb23-ab8299d04385)   
+ [lrint, lrintf, lrintl, llrint, llrintf, llrintl](lrint-lrintf-lrintl-llrint-llrintf-llrintl.md)   
  [round, roundf, roundl](../../c-runtime-library/reference/round-roundf-roundl.md)   
- [nearbyint, nearbyintf, nearbyintl](http://msdn.microsoft.com/en-us/15111e73-331d-41d1-81b7-3e10df894848)   
+ [nearbyint, nearbyintf, nearbyintl](nearbyint-nearbyintf-nearbyintl1.md)   
  [rint, rintf, rintl](../../c-runtime-library/reference/rint-rintf-rintl.md)

docs/c-runtime-library/reference/malloc-dbg.md

@@ -73,7 +73,7 @@ void *_malloc_dbg(
  Debug versions of [C run-time libraries](../../c-runtime-library/crt-library-features.md) only.  
 
 ## Example  
- For a sample of how to use `_malloc_dbg`, see [crt_dbg1](http://msdn.microsoft.com/en-us/17b4b20c-e849-48f5-8eb5-dca6509cbaf9).  
+ For a sample of how to use `_malloc_dbg`, see [crt_dbg1](https://github.com/Microsoft/VCSamples/tree/master/VC2010Samples/crt/crt_dbg1).  
 
 ## See Also  
  [Debug Routines](../../c-runtime-library/debug-routines.md)   

docs/c-runtime-library/reference/nearbyint-nearbyintf-nearbyintl1.md

@@ -1,5 +1,5 @@
 ---
-title: "nearbyint, nearbyintf, nearbyintl1 | Microsoft Docs"
+title: "nearbyint, nearbyintf, nearbyintl | Microsoft Docs"
 ms.custom: ""
 ms.date: "11/04/2016"
 ms.reviewer: ""

docs/c-runtime-library/reference/rint-rintf-rintl.md

@@ -98,7 +98,7 @@ rintl(-2.500000) is -3
  [ceil, ceilf, ceill](../../c-runtime-library/reference/ceil-ceilf-ceill.md)   
  [floor, floorf, floorl](../../c-runtime-library/reference/floor-floorf-floorl.md)   
  [fmod, fmodf](../../c-runtime-library/reference/fmod-fmodf.md)   
- [lrint, lrintf, lrintl, llrint, llrintf, llrintl](http://msdn.microsoft.com/en-us/312fd869-a9c0-4107-bb23-ab8299d04385)   
+ [lrint, lrintf, lrintl, llrint, llrintf, llrintl](lrint-lrintf-lrintl-llrint-llrintf-llrintl.md)   
  [lround, lroundf, lroundl, llround, llroundf, llroundl](../../c-runtime-library/reference/lround-lroundf-lroundl-llround-llroundf-llroundl.md)   
- [nearbyint, nearbyintf, nearbyintl](http://msdn.microsoft.com/en-us/15111e73-331d-41d1-81b7-3e10df894848)   
+ [nearbyint, nearbyintf, nearbyintl](nearbyint-nearbyintf-nearbyintl1.md)   
  [rint](../../c-runtime-library/reference/rint-rintf-rintl.md)

docs/c-runtime-library/reference/round-roundf-roundl.md

@@ -106,7 +106,7 @@ roundl(-2.500000) is -3
  [ceil, ceilf, ceill](../../c-runtime-library/reference/ceil-ceilf-ceill.md)   
  [floor, floorf, floorl](../../c-runtime-library/reference/floor-floorf-floorl.md)   
  [fmod, fmodf](../../c-runtime-library/reference/fmod-fmodf.md)   
- [lrint, lrintf, lrintl, llrint, llrintf, llrintl](http://msdn.microsoft.com/en-us/312fd869-a9c0-4107-bb23-ab8299d04385)   
+ [lrint, lrintf, lrintl, llrint, llrintf, llrintl](lrint-lrintf-lrintl-llrint-llrintf-llrintl.md)   
  [lround, lroundf, lroundl, llround, llroundf, llroundl](../../c-runtime-library/reference/lround-lroundf-lroundl-llround-llroundf-llroundl.md)   
- [nearbyint, nearbyintf, nearbyintl](http://msdn.microsoft.com/en-us/15111e73-331d-41d1-81b7-3e10df894848)   
+ [nearbyint, nearbyintf, nearbyintl](nearbyint-nearbyintf-nearbyintl1.md)   
  [rint, rintf, rintl](../../c-runtime-library/reference/rint-rintf-rintl.md)

docs/c-runtime-library/reference/set-sse2-enable.md

@@ -21,7 +21,7 @@ manager: "ghogen"
 ms.workload: ["cplusplus"]
 ---
 # _set_SSE2_enable
-Enables or disables the use of [Streaming SIMD Extensions 2](http://msdn.microsoft.com/en-us/f98440eb-73a9-4f96-b203-ac41bb6701ea) (SSE2) instructions in CRT math routines. (This function is not available on x64 architectures because SSE2 is enabled by default.)  
+Enables or disables the use of Streaming SIMD Extensions 2 (SSE2) instructions in CRT math routines. (This function is not available on x64 architectures because SSE2 is enabled by default.)  
 
 ## Syntax  
 

docs/c-runtime-library/security-features-in-the-crt.md

@@ -40,7 +40,7 @@ strcpy(szBuf, "test"); // warning: deprecated
 
  For those deprecated functions without secure template overloads, you should definitely consider manually updating your code to use the secure versions.  
 
- Another source of deprecation warnings, unrelated to security, is the POSIX functions. Replace POSIX function names with their standard equivalents (for example, change [access](../c-runtime-library/reference/access-crt.md) to [_access](../c-runtime-library/reference/access-waccess.md)), or disable POSIX-related deprecation warnings by defining `_CRT_NONSTDC_NO_WARNINGS`. For more information, see [Deprecated CRT Functions](http://msdn.microsoft.com/en-us/7e259932-c6c8-4c1a-9637-639e591681a5).  
+ Another source of deprecation warnings, unrelated to security, is the POSIX functions. Replace POSIX function names with their standard equivalents (for example, change [access](../c-runtime-library/reference/access-crt.md) to [_access](../c-runtime-library/reference/access-waccess.md)), or disable POSIX-related deprecation warnings by defining `_CRT_NONSTDC_NO_WARNINGS`. For more information, see [Compatibility](compatibility.md).  
 
 ## Additional Security Features  
  Some of the security features include the following:  

docs/data/oledb/ole-db-templates.md

@@ -58,8 +58,5 @@ The OLE DB templates make OLE DB data access easier. Visual C++ provides templat
  [Active Template Library (ATL) Reference](../../atl/atl-com-desktop-components.md)  
  Provides reference material for the ATL Library, a set of template-based C++ classes that simplify the programming of COM objects.  
 
- [Visual C++ Libraries](http://msdn.microsoft.com/en-us/fec23c40-10c0-4857-9cdc-33a3b99b30ae)  
- Provides links to the various libraries provided with Visual C++, including ATL, MFC, OLE DB Templates, the C run-time library, and the C++ Standard Library.  
-  
  [Debugging](/visualstudio/debugger/debugging-in-visual-studio)  
  Provides links to using the Visual Studio debugger to correct logic errors in your application or stored procedures.

docs/mfc/mfc-technical-notes.md

@@ -29,6 +29,6 @@ A technical note is a document written for programmers by programmers.
 -   [Technical Notes By Category](../mfc/technical-notes-by-category.md)  
 
 ## See Also  
- [Visual C++ Libraries Reference](http://msdn.microsoft.com/en-us/fec23c40-10c0-4857-9cdc-33a3b99b30ae)   
+
  [MFC Desktop Applications](../mfc/mfc-desktop-applications.md)
 

docs/mfc/reference/cmfcdragframeimpl-class.md

@@ -30,7 +30,7 @@ class CMFCDragFrameImpl
 ## Remarks  
  An object of this class is embedded in each [CPane Class](../../mfc/reference/cpane-class.md) object. Thus, each pane that uses the `CanFloat` method displays a drag rectangle when the user drags it.  
 
- You can control the thickness of the drag rectangle by using [AFX_GLOBAL_DATA::m_nDragFrameThicknessFloat]--brokenlink--(afx-global-data-structure.md#m_ndragframethicknessfloat) and [AFX_GLOBAL_DATA::m_nDragFrameThicknessDock](afx-global-data-structure.md#m_ndragframethicknessdock).  
+ You can control the thickness of the drag rectangle by using [AFX_GLOBAL_DATA::m_nDragFrameThicknessFloat](afx-global-data-structure.md#m_ndragframethicknessfloat) and [AFX_GLOBAL_DATA::m_nDragFrameThicknessDock](afx-global-data-structure.md#m_ndragframethicknessdock).  
 
 ## Inheritance Hierarchy  
  [CMFCDragFrameImpl](../../mfc/reference/cmfcdragframeimpl-class.md)  

docs/mfc/reference/cmousemanager-class.md

@@ -218,7 +218,7 @@ void SetCommandForDblClk(
  The command identifier.  
 
 ### Remarks  
- In order to associate a custom command with a view, you must first register the view by using [CMouseManager::AddView](#addview). The `AddView` method requires a view identifier as an input parameter. Once you register a view, you can call `CMouseManager::SetCommandForDblClk` with the same view identifier input parameter that you supplied to `AddView`. Thereafter, when the user double-clicks the mouse in the registered view, the application will execute the command indicated by `uiCmd.` To support the custom mouse behavior, you will also need to customize the view registered with the mouse manager. For more information about custom mouse behavior, see [Keyboard and Mouse Customization]--brokenlink--(../mouse-and-keyboard-customization.md).  
+ In order to associate a custom command with a view, you must first register the view by using [CMouseManager::AddView](#addview). The `AddView` method requires a view identifier as an input parameter. Once you register a view, you can call `CMouseManager::SetCommandForDblClk` with the same view identifier input parameter that you supplied to `AddView`. Thereafter, when the user double-clicks the mouse in the registered view, the application will execute the command indicated by `uiCmd.` To support the custom mouse behavior, you will also need to customize the view registered with the mouse manager. For more information about custom mouse behavior, see [Keyboard and Mouse Customization](../keyboard-and-mouse-customization.md).  
 
  If `uiCmd` is set to 0, the specified view is no longer associated with a command.  
 

docs/mfc/special-cwinapp-services.md

@@ -29,9 +29,9 @@ Besides running the message loop and giving you an opportunity to initialize the
 
  This automatic registration support in `CWinApp` eliminates the need to ship a .reg file with your application or to do special installation work.  
 
- If you want to initialize GDI+ for your application (by calling [GdiplusStartup]--brokenlink--(_gdiplus_FUNC_GdiplusStartup_token_input_output_) in your [InitInstance](../mfc/reference/cwinapp-class.md#initinstance) function), you have to suppress the GDI+ background thread.  
+ If you want to initialize GDI+ for your application (by calling [GdiplusStartup](https://msdn.microsoft.com/library/ms534077) in your [InitInstance](../mfc/reference/cwinapp-class.md#initinstance) function), you have to suppress the GDI+ background thread.  
 
- You can do this by setting the **SuppressBackgroundThread** member of the [GdiplusStartupInput]--brokenlink--(_gdiplus_STRUC_GdiplusStartupInput) structure to **TRUE**. When suppressing the GDI+ background thread, the **NotificationHook** and **NotificationUnhook** calls (see [GdiplusStartupOutput]--brokenlink--(_gdiplus_STRUC_GdiplusStartupOutput)) should be made just prior to entering and exiting the application's message loop. Therefore, a good place to call **GdiplusStartup** and the hook notification functions would be in an override of the virtual function [CWinApp::Run](../mfc/reference/cwinapp-class.md#run), as shown below:  
+ You can do this by setting the **SuppressBackgroundThread** member of the [GdiplusStartupInput](https://msdn.microsoft.com/library/ms534067) structure to **TRUE**. When suppressing the GDI+ background thread, the **NotificationHook** and **NotificationUnhook** calls should be made just prior to entering and exiting the application's message loop. For more information on these calls, see [GdiplusStartupOutput](https://msdn.microsoft.com/library/ms534068). Therefore, a good place to call **GdiplusStartup** and the hook notification functions would be in an override of the virtual function [CWinApp::Run](../mfc/reference/cwinapp-class.md#run), as shown below:  
 
  [!code-cpp[NVC_MFCDocView#6](../mfc/codesnippet/cpp/special-cwinapp-services_1.cpp)]