Merge pull request #3878 from corob-msft/docs/corob/link-fix-more

Correct or remove links: validation issues

Author: PRMerger8

docs/build/reference/fsanitize-coverage.md

@@ -7,7 +7,7 @@ helpviewer_keywords: ["/fsanitize-coverage [C++]", "sanitizer compiler option [C
 ---
 # `/fsanitize-coverage` (Configure sanitizer coverage)
 
-The **`/fsanitize-coverage`** compiler options instruct the compiler to add various kinds of instrumentation points where user-defined functions are called. These options are useful for fuzzing scenarios that use **`/fsanitize=fuzzer`**, like OneFuzz. For more information, see the [OneFuzz documentation](https://www.microsoft.com/en-us/research/project/project-onefuzz/) and [OneFuzz GitHub project](https://github.com/microsoft/onefuzz).
+The **`/fsanitize-coverage`** compiler options instruct the compiler to add various kinds of instrumentation points where user-defined functions are called. These options are useful for fuzzing scenarios that use **`/fsanitize=fuzzer`**, like OneFuzz. For more information, see the [OneFuzz documentation](https://www.microsoft.com/research/project/project-onefuzz/) and [OneFuzz GitHub project](https://github.com/microsoft/onefuzz).
 
 ## Syntax
 

docs/build/reference/fsanitize.md

@@ -20,7 +20,7 @@ Use the **`/fsanitize`** compiler options to enable sanitizers.
 
 The **`/fsanitize=address`** compiler option enables [AddressSanitizer](../../sanitizers/asan.md), a powerful compiler and runtime technology to uncover [hard-to-find bugs](../../sanitizers/asan.md#error-types). Support for the **`/fsanitize=address`** option is available starting in Visual Studio 2019 version 16.9.
 
-The **`/fsanitize=fuzzer`** compiler option enables experimental support for [LibFuzzer](https://releases.llvm.org/3.8.0/docs/LibFuzzer.html). LibFuzzer is a coverage-guided fuzzing library that can be used to find bugs and crashes caused by user-provided input. We recommended you use **`/fsanitize=address`** with LibFuzzer. This option is useful for fuzzing tools such as OneFuzz. For more information, see the [OneFuzz documentation](https://www.microsoft.com/en-us/research/project/project-onefuzz/) and [OneFuzz GitHub project](https://github.com/microsoft/onefuzz). Support for the **`/fsanitize=fuzzer`** option is available starting in Visual Studio 2022 version 17.0.
+The **`/fsanitize=fuzzer`** compiler option enables experimental support for [LibFuzzer](https://releases.llvm.org/3.8.0/docs/LibFuzzer.html). LibFuzzer is a coverage-guided fuzzing library that can be used to find bugs and crashes caused by user-provided input. We recommended you use **`/fsanitize=address`** with LibFuzzer. This option is useful for fuzzing tools such as OneFuzz. For more information, see the [OneFuzz documentation](https://www.microsoft.com/research/project/project-onefuzz/) and [OneFuzz GitHub project](https://github.com/microsoft/onefuzz). Support for the **`/fsanitize=fuzzer`** option is available starting in Visual Studio 2022 version 17.0.
 
 The **`/fsanitize`** option doesn't allow comma-separated syntax, for example: **`/fsanitize=address,fuzzer`**. These options must be specified individually.
 

docs/build/reference/qspectre.md

@@ -96,7 +96,7 @@ There are several ways to specify the Spectre-mitigated libraries to the build c
 
 ### Additional information
 
-For more information, see the official [Microsoft Security Advisory ADV180002, Guidance to mitigate speculative execution side-channel vulnerabilities](https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/ADV180002). Guidance is also available from Intel, [Speculative Execution Side Channel Mitigations](https://software.intel.com/sites/default/files/managed/c5/63/336996-Speculative-Execution-Side-Channel-Mitigations.pdf), and ARM, [Cache Speculation Side-channels](https://developer.arm.com/-/media/Files/pdf/Cache_Speculation_Side-channels.pdf).
+For more information, see the official [Microsoft Security Advisory ADV180002, Guidance to mitigate speculative execution side-channel vulnerabilities](https://msrc.microsoft.com/update-guide/vulnerability/ADV180002). Guidance is also available from Intel, [Speculative Execution Side Channel Mitigations](https://software.intel.com/sites/default/files/managed/c5/63/336996-Speculative-Execution-Side-Channel-Mitigations.pdf), and ARM, [Cache Speculation Side-channels](https://developer.arm.com/-/media/Files/pdf/Cache_Speculation_Side-channels.pdf).
 
 For a Windows-specific overview of Spectre and Meltdown mitigations, see [Understanding the performance impact of Spectre and Meltdown mitigations on Windows Systems](https://www.microsoft.com/security/blog/2018/01/09/understanding-the-performance-impact-of-spectre-and-meltdown-mitigations-on-windows-systems/).
 

docs/c-language/static-assert-c.md

@@ -73,7 +73,7 @@ int main()
 
 Compile with [`/std:c11`](../build/reference/std-specify-language-standard-version.md).
 
-Windows SDK 10.0.20348.0 (version 2104) or later. See [Windows SDK](https://developer.microsoft.com/windows/downloads/windows-sdk/) to download the latest SDK. For instructions to install and use the SDK for C11 and C17 development, see [Install C11 and C17 support in Visual Studio](../overview/install-c17-support.md).
+Windows SDK 10.0.20348.0 (version 2104) or later. For more information on installing the Windows SDK for C11 and C17 development, see [Install C11 and C17 support in Visual Studio](../overview/install-c17-support.md).
 
 ## See also
 

docs/code-quality/c6236.md

@@ -57,4 +57,4 @@ void f( int n )
 
 ## See also
 
-[C++ Bitwise Operators](https://www.microsoft.com/download/details.aspx?id=55979)
+[Bitwise AND operator: `&`](../cpp/bitwise-and-operator-amp.md)

docs/mfc/upgrading-an-existing-activex-control.md

@@ -1,7 +1,7 @@
 ---
 description: "Learn more about: Upgrading an Existing ActiveX Control"
 title: "Upgrading an Existing ActiveX Control"
-ms.date: "09/12/2018"
+ms.date: 11/03/2021
 helpviewer_keywords: ["ActiveX controls [MFC], Internet", "LPK files for Internet controls", "safe for scripting and initialization (controls)", "OLE controls [MFC], upgrading to ActiveX", "CAB files, for ActiveX controls", "Internet applications [MFC], ActiveX controls", "Internet applications [MFC], packaging code for download", "upgrading ActiveX controls", "licensing ActiveX controls"]
 ms.assetid: 4d12ddfa-b491-4f9f-a0b7-b51458e05651
 ---
@@ -10,7 +10,7 @@ ms.assetid: 4d12ddfa-b491-4f9f-a0b7-b51458e05651
 Existing ActiveX controls (formerly OLE controls) can be used on the Internet without modification. However, you may want to modify controls to improve their performance.
 
 > [!IMPORTANT]
-> ActiveX is a legacy technology that should not be used for new development. For more information about modern technologies that supersede ActiveX, see [ActiveX Controls](activex-controls.md).
+> ActiveX is a legacy technology that should not be used for new development. For more information about modern technologies that supersede ActiveX, see [ActiveX Controls](activex-controls.md). Support for ActiveX controls was deprecated in later versions of Internet Explorer, and is not supported by modern browsers. Microsoft no longer supplies web-accessible ActiveX components.
 
 When using your control on a Web page, there are additional considerations. The .ocx file and all supporting files must be on the target machine or be downloaded across the Internet. This makes code size and download time an important consideration. Downloads can be packaged in a signed .cab file. You can mark your control as safe for scripting, and as safe for initializing.
 
@@ -41,7 +41,7 @@ ActiveX controls are embedded in Web pages using the `<OBJECT>` tag. The `CODEBA
 ### Using the CODEBASE Tag with an OCX File
 
 ```
-CODEBASE="http://example.microsoft.com/mycontrol.ocx#version=4,
+CODEBASE="http://example.contoso.com/mycontrol.ocx#version=4,
     70,
     0,
     1086"
@@ -52,15 +52,15 @@ This solution downloads only the control's .ocx file, and requires any supportin
 ### Using the CODEBASE Tag with an INF File
 
 ```
-CODEBASE="http://example.microsoft.com/trustme.inf"
+CODEBASE="http://example.contoso.com/trustme.inf"
 ```
 
 An .inf file will control the installation of an .ocx and its supporting files. This method is not recommended because it is not possible to sign an .inf file (see [Signing Code](#_core_signing_code) for pointers on code signing).
 
 ### Using the CODEBASE Tag with a CAB File
 
 ```
-CODEBASE="http://example.microsoft.com/acontrol.cab#version=1,
+CODEBASE="http://example.contoso.com/acontrol.cab#version=1,
     2,
     0,
     0"
@@ -78,12 +78,12 @@ For details on how to create a CAB file, see [Creating a CAB File](/windows/win3
 
 ### The INF File
 
-The following example, spindial.inf, lists the supporting files and the version information needed for the MFC Spindial control. Notice the location for the MFC DLLs is a Microsoft Web site. The mfc42.cab is provided and signed by Microsoft.
+The following example, spindial.inf, lists the supporting files and the version information needed for the MFC Spindial control. The mfc42.cab is provided and signed by Microsoft.
 
 ```
 Contents of spindial.inf:
 [mfc42installer]
-file-win32-x86=http://activex.microsoft.com/controls/vc/mfc42.cab
+file-win32-x86=http://example.contoso.com/controls/vc/mfc42.cab
 [Olepro32.dll] - FileVersion=5,
     0,
     4261,
@@ -105,7 +105,7 @@ The following example illustrates using the `<OBJECT>` tag to package the MFC Sp
 ```
 <OBJECT ID="Spindial1" WIDTH=100 HEIGHT=51
     CLASSID="CLSID:06889605-B8D0-101A-91F1-00608CEAD5B3"
-    CODEBASE="http://example.microsoft.com/spindial.cab#Version=1,0,0,001">
+    CODEBASE="http://example.contoso.com/spindial.cab#Version=1,0,0,001">
 <PARAM NAME="_Version" VALUE="65536">
 <PARAM NAME="_ExtentX" VALUE="2646">
 <PARAM NAME="_ExtentY" VALUE="1323">