9/19/2022 AM Publish (#4526)

* Updated C6101

Mirror of my public PR. Added an example. Added proper spacing between headers and code blocks, matched formatting to my other PRs

* Updated C6101

Minor changes in response to Acrolinx report

* Updated C6101

More Acrolinx changes, split a run-on sentence

* Updated C26495

Matched formatting to my other PRs. Added more information to the example.

* Updated C26495

Fixed spelling error

* Updated C6101

Updated to the latest format

* Updated C6101

Single backticks and InOut->Inout

* Updated C26495

Updated to the new format
NOTE: This warning has no code analysis name. Per @MichaelSquires instructions, I omitted the usual keywords and 'Code analysis name:' section to match

* Update compiler-warning-level-4-c4464.md

@corob-msft 
proposal.  I don't warrant it shouldn't be worded in a better way.

* Update compiler-warning-level-4-c4464.md

typo fix

* fix: delete unnecessary asterisk

followup fix of #4136

* optimize prime test

* Update floating-point-support.md

Explain what "ulp" stands for

* Updates for cpp-docs 4161

* Update integritycheck-require-signature-check.md

* alt-text

* Update abstract-cpp-component-extensions.md

* Add syntax highlighting to atl-mfc-shared

* Updated C26495

Added code analysis ID

* alt-text updates

* customer fix

* minor updates

* Incorporate changes in rewrite

Updates for style and clarity. Also give it an Acrolinx pass.

* Clarify version support

* Tweak language for minimum support

* Add code style, comment

@MugBergerFries 
It's a good idea to use code styling for mentions of variable or class names (especially when they're easily confused generic names like "value").
I also added a comment to the fixed code sample to amplify the change and what it was doing.

* acrolinx

* cleanup pass

* [BULK] DocuTune - Rebranding

* Update README.md

Co-authored-by: Samuel Berger <sjamesberger@gmail.com>
Co-authored-by: Brad Litterell <49081806+bradlitterell@users.noreply.github.com>
Co-authored-by: opbld17 <opbld17@microsoft.com>
Co-authored-by: Colin Robertson <3836425+corob-msft@users.noreply.github.com>
Co-authored-by: opbld16 <opbld16@microsoft.com>
Co-authored-by: Kisaragi <48310258+KisaragiEffective@users.noreply.github.com>
Co-authored-by: Courtney Wales <62625502+Court72@users.noreply.github.com>
Co-authored-by: opbld15 <opbld15@microsoft.com>
Co-authored-by: TylerMSFT <Tyler.Whitney@microsoft.com>
Co-authored-by: Bryan Gold <101299717+19BMG00@users.noreply.github.com>
Co-authored-by: Edward Breeveld <42862235+EddieBreeveld@users.noreply.github.com>
Co-authored-by: Jeff Borsecnik <36546697+jborsecnik@users.noreply.github.com>
Co-authored-by: jsuther1974 <jsuther@microsoft.com>
Co-authored-by: Austin Morton <apmorton@users.noreply.github.com>
Co-authored-by: Jak Koke <v-jokoke@microsoft.com>
Co-authored-by: HO-COOH <42881734+HO-COOH@users.noreply.github.com>
Co-authored-by: prmerger-automator[bot] <40007230+prmerger-automator[bot]@users.noreply.github.com>
Co-authored-by: James Barnett <v-jabarnett@microsoft.com>
Co-authored-by: Dennis Rea <v-denrea@microsoft.com>
Co-authored-by: Alex Buck <abuck@microsoft.com>
Co-authored-by: Feng Xu <fenxu@microsoft.com>

Author: 22 people

CONTRIBUTING.md

@@ -2,7 +2,7 @@
 
 Thank you for your interest in contributing to the Visual C++ documentation!
 
-In this topic, you'll see the basic process for adding or updating content in the [Visual C++ documentation site](https://docs.microsoft.com/cpp/).
+In this topic, you'll see the basic process for adding or updating content in the [Visual C++ documentation site](https://learn.microsoft.com/cpp/).
 
 In this topic, we'll cover:
 
@@ -54,7 +54,7 @@ The Visual Studio team will review your PR and let you know if the change looks
 
 The maintainers will merge your PR into the main branch once feedback has been applied and your change looks good.
 
-On a certain cadence, we push all commits from main branch into the live branch and then you'll be able to see your contribution on [Microsoft Docs](https://docs.microsoft.com/cpp/).
+On a certain cadence, we push all commits from main branch into the live branch and then you'll be able to see your contribution on [Microsoft Learn](https://learn.microsoft.com/cpp/).
 
 ## DOs and DON'Ts
 
@@ -72,7 +72,7 @@ Below is a short list of guiding rules that you should keep in mind when you are
 
 ## Building the docs
 
-The documentation is written in [GitHub-Flavored Markdown](https://help.github.com/categories/writing-on-github/) and built using [DocFX](https://dotnet.github.io/docfx/) and other internal publishing and build tools. It's published on [Microsoft Docs](https://docs.microsoft.com/).
+The documentation is written in [GitHub-Flavored Markdown](https://help.github.com/categories/writing-on-github/) and built using [DocFX](https://dotnet.github.io/docfx/) and other internal publishing and build tools. It's published to [Microsoft Learn](https://learn.microsoft.com/).
 
 If you want to build the docs locally, you need to install [DocFX](https://dotnet.github.io/docfx/); latest versions are the best.
 

README.md

@@ -1,12 +1,12 @@
 # Visual Studio documentation for Microsoft C++
 
-Welcome! This repository contains source files for the work-in-progress Microsoft C++ (MSVC or Visual C++) technical documentation. The articles are published on the [C++ in Visual Studio documentation site](https://docs.microsoft.com/cpp).
+Welcome! This repository contains source files for the work-in-progress Microsoft C++ (MSVC or Visual C++) technical documentation. The articles are published on the [C++ in Visual Studio documentation site](https://learn.microsoft.com/cpp).
 
 The documentation for Visual Basic and Visual C# are located in a separate repository at [https://github.com/dotnet/core-docs](https://github.com/dotnet/core-docs), and the Visual Studio documentation is located in the repository located at [https://github.com/Microsoft/visualstudio-docs](https://github.com/Microsoft/visualstudio-docs).
 
 ## Contributing to the documentation
 
-We welcome your contributions to help us improve the MSVC docs. For a comprehensive guide to contributing to Microsoft Docs, see the [contributor guide overview](https://docs.microsoft.com/contribute). For details on how to make a contribution to the MSVC documentation, see the [Contributing guide](CONTRIBUTING.md).
+We welcome your contributions to help us improve the MSVC docs. For a comprehensive guide to contributing, see the [Microsoft Docs contributor guide](https://learn.microsoft.com/contribute). For details on how to make a contribution to the MSVC documentation, see our [Contributing guidance](CONTRIBUTING.md).
 
 Several feature areas of MSVC have their own folders in this repository, such as `standard-library` for articles on the C++ Standard Library, `ide` for C++-specific articles on the Visual Studio interactive development environment (IDE), and so forth. The `/media` subfolder in each folder contains art files for the articles. The [Contributing guide](CONTRIBUTING.md) has more information.
 

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

@@ -72,7 +72,7 @@ void RangedRandDemo(int range_min, int range_max, int n)
         // generating random numbers across a large range using the method below.
         // The approach below also may result in a non-uniform distribution.
         // More robust random number functionality is available in the C++ <random> header.
-        // See https://docs.microsoft.com/cpp/standard-library/random
+        // See https://learn.microsoft.com/cpp/standard-library/random
         int r = ((double)rand() / RAND_MAX) * (range_max - range_min) + range_min;
         printf("  %6d\n", r);
     }

docs/mfc/reference/creating-a-web-browser-style-mfc-application.md

@@ -37,7 +37,7 @@ void CWebView::OnInitialUpdate()
 
     // TODO: This code navigates to a popular spot on the web.
     // Change the code to go where you'd like.
-    Navigate2(_T("http://www.docs.microsoft.com/"),
+    Navigate2(_T("https://learn.microsoft.com/"),
         NULL,
         NULL);
 }

styleguide/template.md

@@ -121,7 +121,7 @@ To link to a header in a Markdown file in the same repo, use relative linking +
 
 ### Docs Links
 
-To link to a file in a different Docs repo, use the docs.microsoft.com relative URL as the link. Don't include the .md suffix or the language/locale element.
+To link to a file in a different Docs repo, use the `learn.microsoft.com` relative URL as the link. Don't include the .md suffix or the language/locale element.
 
 - Example: [Universal Windows Platform documentation](/windows/uwp)
 
@@ -362,8 +362,8 @@ Use backticks (`) for `inline code`. Use inline code for command-line comman
 
 ### Shows
 
-[![C++ A General Purpose Language and Library: (01) Getting Started](https://docs.microsoft.com/video/media/e8265f2d-9ea3-4052-99cd-b8cfb246b0f0/clanguagelibrarym01_960.jpg)
-](https://docs.microsoft.com/en-us/shows/cplusplus-language-library/01)\
+[![C++ A General Purpose Language and Library: (01) Getting Started](https://learn.microsoft.com/video/media/e8265f2d-9ea3-4052-99cd-b8cfb246b0f0/clanguagelibrarym01_960.jpg)
+](https://learn.microsoft.com/shows/cplusplus-language-library/01)\
 C++ A General Purpose Language and Library: (01) Getting Started.
 
 ### YouTube
@@ -408,7 +408,7 @@ And they'll render like this:
 > [!div class="button"]
 [button links](../docs/core/index.md)
 
-You can see an example of buttons in action at the [Intune docs](https://docs.microsoft.com/intune/get-started/choose-how-to-enroll-devices).
+You can see an example of buttons in action at the [Intune docs](https://learn.microsoft.com/intune/get-started/choose-how-to-enroll-devices).
 
 ### Selectors
 
@@ -417,12 +417,12 @@ You can see an example of buttons in action at the [Intune docs](https://docs.mi
 - [macOS](../docs/core/tutorials/using-on-macos.md)
 - [Windows](../docs/core/tutorials/using-on-windows.md)
 
-You can see an example of selectors in action at the [Intune docs](https://docs.microsoft.com/intune/deploy-use/what-to-tell-your-end-users-about-using-microsoft-intune#how-your-end-users-get-their-apps).
+You can see an example of selectors in action at the [Intune docs](https://learn.microsoft.com/intune/deploy-use/what-to-tell-your-end-users-about-using-microsoft-intune#how-your-end-users-get-their-apps).
 
 ### Step-By-Steps
 
 >[!div class="step-by-step"]
 [Pre](../docs/csharp/expression-trees-interpreting.md)
 [Next](../docs/csharp/expression-trees-translating.md)
 
-You can see an example of step-by-steps in action at the [Advanced Threat Analytics docs](https://docs.microsoft.com/advanced-threat-analytics/deploy-use/install-ata-step2).
+You can see an example of step-by-steps in action at the [Advanced Threat Analytics docs](https://learn.microsoft.com/advanced-threat-analytics/deploy-use/install-ata-step2).