more fwlinks

Author: mikeblome

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

@@ -32,7 +32,7 @@ int rand( void );
 
 The **rand** function returns a pseudorandom integer in the range 0 to **RAND_MAX** (32767). Use the [srand](srand.md) function to seed the pseudorandom-number generator before calling **rand**.
 
-The **rand** function generates a well-known sequence and is not appropriate for use as a cryptographic function. For more cryptographically secure random number generation, use [rand_s](rand-s.md) or the functions declared in the C++ Standard Library in [\<random>](../../standard-library/random.md). For information about what's wrong with **rand** and how \<random> addresses these shortcomings, see [this video](http://go.microsoft.com/fwlink/?LinkId=397615).
+The **rand** function generates a well-known sequence and is not appropriate for use as a cryptographic function. For more cryptographically secure random number generation, use [rand_s](rand-s.md) or the functions declared in the C++ Standard Library in [\<random>](../../standard-library/random.md). For information about what's wrong with **rand** and how \<random> addresses these shortcomings, see this video entitled [rand Considered Harmful](https://channel9.msdn.com/Events/GoingNative/2013/rand-Considered-Harmful).
 
 ## Requirements
 

docs/c-runtime-library/reference/set-abort-behavior.md

@@ -19,7 +19,7 @@ ms.workload: ["cplusplus"]
 Specifies the action to be taken when a program is abnormally terminated.
 
 > [!NOTE]
-> Do not use the [abort](abort.md) function to shut down a Microsoft Store app, except in testing or debugging scenarios. Programmatic or UI ways to close a Store app are not permitted according to the [Microsoft Store policies](http://go.microsoft.com/fwlink/?LinkId=865936). For more information, see [UWP app lifecycle](http://go.microsoft.com/fwlink/p/?LinkId=865934).
+> Do not use the [abort](abort.md) function to shut down a Microsoft Store app, except in testing or debugging scenarios. Programmatic or UI ways to close a Store app are not permitted according to the [Microsoft Store policies](/legal/windows/agreements/store-policies). For more information, see [UWP app lifecycle](/windows/uwp/launch-resume/app-lifecycle).
 
 ## Syntax
 

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

@@ -19,7 +19,7 @@ ms.workload: ["cplusplus"]
 Sets interrupt signal handling.
 
 > [!IMPORTANT]
-> Do not use this method to shut down a Microsoft Store app, except in testing or debugging scenarios. Programmatic or UI ways to close a Store app are not permitted according to the [Microsoft Store policies](http://go.microsoft.com/fwlink/?LinkId=865936). For more information, see [UWP app lifecycle](http://go.microsoft.com/fwlink/p/?LinkId=865934).
+> Do not use this method to shut down a Microsoft Store app, except in testing or debugging scenarios. Programmatic or UI ways to close a Store app are not permitted according to the [Microsoft Store policies](/legal/windows/agreements/store-policies). For more information, see [UWP app lifecycle](/windows/uwp/launch-resume/app-lifecycle).
 
 ## Syntax
 

docs/cpp/restrict-cpp-amp.md

@@ -75,7 +75,7 @@ The restriction specifier can be applied to function and lambda declarations. It
 
     -   Varargs.  
 
- For a discussion of function limitations, see [restrict(amp) Restrictions](http://go.microsoft.com/fwlink/p/?LinkId=251089).  
+ For a discussion of function limitations, see [restrict (amp) Restrictions](https://blogs.msdn.microsoft.com/nativeconcurrency/2011/12/19/restrictamp-restrictions-part-0-of-n-introduction/).  
 
 ## Example  
  The following example shows how to use the `restrict(amp)`clause.  

docs/cpp/rvalue-reference-declarator-amp-amp.md

@@ -49,7 +49,7 @@ int main()
 
  Before Visual C++ 2010, each call to **operator+** allocates and returns a new temporary `string` object (an rvalue). **operator+** cannot append one string to the other because it does not know whether the source strings are lvalues or rvalues. If the source strings are both lvalues, they might be referenced elsewhere in the program and therefore must not be modified. By using rvalue references, **operator+** can be modified to take rvalues, which cannot be referenced elsewhere in the program. Therefore, **operator+** can now append one string to another. This can significantly reduce the number of dynamic memory allocations that the `string` class must perform. For more information about the `string` class, see [basic_string Class](../standard-library/basic-string-class.md).  
 
- Move semantics also helps when the compiler cannot use Return Value Optimization (RVO) or Named Return Value Optimization (NRVO). In these cases, the compiler calls the move constructor if the type defines it. For more information about Named Return Value Optimization, see [Named Return Value Optimization in Visual C++ 2005](http://go.microsoft.com/fwlink/p/?linkid=131571).  
+ Move semantics also helps when the compiler cannot use Return Value Optimization (RVO) or Named Return Value Optimization (NRVO). In these cases, the compiler calls the move constructor if the type defines it. For more information about Named Return Value Optimization, see [Named Return Value Optimization in Visual C++ 2005](https://msdn.microsoft.com/en-us/library/ms364057.aspx).  
 
  To better understand move semantics, consider the example of inserting an element into a `vector` object. If the capacity of the `vector` object is exceeded, the `vector` object must reallocate memory for its elements and then copy each element to another memory location to make room for the inserted element. When an insertion operation copies an element, it creates a new element, calls the copy constructor to copy the data from the previous element to the new element, and then destroys the previous element. Move semantics enables you to move objects directly without having to perform expensive memory allocation and copy operations.  
 

docs/cpp/safebuffers.md

@@ -24,7 +24,7 @@ __declspec( safebuffers )
 ```  
 
 ## Remarks  
- The **/GS** compiler option causes the compiler to test for buffer overruns by inserting security checks on the stack. The types of data structures that are eligible for security checks are described in [/GS (Buffer Security Check)](../build/reference/gs-buffer-security-check.md). For more information about buffer overrun detection, see [Compiler Security Checks In Depth](http://go.microsoft.com/fwlink/p/?linkid=7260) on the MSDN Web site.  
+ The **/GS** compiler option causes the compiler to test for buffer overruns by inserting security checks on the stack. The types of data structures that are eligible for security checks are described in [/GS (Buffer Security Check)](../build/reference/gs-buffer-security-check.md). For more information about buffer overrun detection, see [Security Features in MSVC](https://blogs.msdn.microsoft.com/vcblog/2017/06/28/security-features-in-microsoft-visual-c/).  
 
  An expert manual code review or external analysis might determine that a function is safe from a buffer overrun. In that case, you can suppress security checks for a function by applying the **__declspec(safebuffers)** keyword to the function declaration.  
 

docs/error-messages/tool-errors/c-runtime-error-r6025.md

@@ -30,4 +30,3 @@ pure virtual function call
 
  This error is caused by calling a virtual function in an abstract base class through a pointer which is created by a cast to the type of the derived class, but is actually a pointer to the base class. This can occur when casting from a **void**<strong>\*</strong> to a pointer to a class when the **void**<strong>\*</strong> was created during the construction of the base class.  
 
- For more information, see the [Microsoft support](http://go.microsoft.com/fwlink/p/?linkid=75220) website.

docs/error-messages/tool-errors/c-runtime-error-r6035.md

@@ -67,4 +67,4 @@ void DllEntryHelper() {
 >  Error message R6035 is only generated by the x86 debug CRT, and only for structured exception handling, but the condition is an error on all platforms, and for all forms of exception handling, such as C++ EH.  
   
 ## See Also  
- [Compiler Security Checks In Depth](http://go.microsoft.com/fwlink/p/?linkid=7260)
+ [Security Features in MSVC](https://blogs.msdn.microsoft.com/vcblog/2017/06/28/security-features-in-microsoft-visual-c/)

docs/error-messages/tool-errors/c-runtime-errors-r6002-through-r6035.md

@@ -15,7 +15,7 @@ ms.workload: ["cplusplus"]
 
 This section is a reference to the errors that can be generated by the C Runtime Library (CRT) when your app is loaded or running. Even though the message refers to the Microsoft Visual C++ runtime, these errors indicate either a bug in your app's code, or a condition that the runtime library can't handle, such as low memory. End users of your app may see these errors if you do not code your app to prevent the conditions that cause them, or write code to capture these errors and present a friendly message to your users.
 
-You may find additional assistance for errors and warnings in Microsoft's public forums. You can search for the error or warning number on the [Developer Community](https://developercommunity.visualstudio.com) site. The [Visual C++ General](http://go.microsoft.com/fwlink/p/?linkid=158194) forum is for questions about Visual C++ that are not discussed in other forums. You may also search for errors and warnings and ask questions on [Stack Overflow](http://stackoverflow.com/) to find solutions.
+You may find additional assistance for errors and warnings in Microsoft's public forums. You can search for the error or warning number on the [Developer Community](https://developercommunity.visualstudio.com) site. The [Visual C++ General](https://social.msdn.microsoft.com/Forums/vstudio/en-US/home?forum=vcgeneral) forum is for questions about Visual C++ that are not discussed in other forums. You may also search for errors and warnings and ask questions on [Stack Overflow](http://stackoverflow.com/) to find solutions.
 
 For links to additional help and community resources, see [Visual C++ Help and Community](../../visual-cpp-help-and-community.md).
 

docs/error-messages/tool-errors/math-errors-m6101-through-m6205.md

@@ -14,6 +14,6 @@ ms.workload: ["cplusplus"]
 
 This section is a reference to the errors generated by the runtime floating-point math library.
 
-You may find additional assistance for errors and warnings in Microsoft's public forums. You can search for the error or warning number on the [Developer Community](https://developercommunity.visualstudio.com) site. The [Visual C++ General](http://go.microsoft.com/fwlink/p/?linkid=158194) forum is for questions about Visual C++ that are not discussed in other forums. You may also search for errors and warnings and ask questions on [Stack Overflow](http://stackoverflow.com/) to find solutions.
+You may find additional assistance for errors and warnings in Microsoft's public forums. You can search for the error or warning number on the [Developer Community](https://developercommunity.visualstudio.com) site. The [Visual C++ General](https://social.msdn.microsoft.com/Forums/vstudio/en-US/home?forum=vcgeneral) forum is for questions about Visual C++ that are not discussed in other forums. You may also search for errors and warnings and ask questions on [Stack Overflow](http://stackoverflow.com/) to find solutions.
 
 For links to additional help and community resources, see [Visual C++ Help and Community](../../visual-cpp-help-and-community.md).