Merge pull request #5940 from MicrosoftDocs/FromPublicMasterBranch

Confirm merge from FromPublicMasterBranch to main to sync with https://github.com/MicrosoftDocs/cpp-docs (branch main)

Author: Albertyang0

docs/atl-mfc-shared/reference/csize-class.md

@@ -1,10 +1,9 @@
 ---
-description: "Learn more about: CSize Class"
 title: "CSize Class"
-ms.date: "10/18/2018"
+description: "Learn more about: CSize Class"
+ms.date: 10/18/2018
 f1_keywords: ["CSize", "ATLTYPES/ATL::CSize", "ATLTYPES/ATL::CSize::CSize"]
 helpviewer_keywords: ["SIZE", "dimensions, MFC", "dimensions", "CSize class"]
-ms.assetid: fb2cf85a-0bc1-46f8-892b-309c108b52ae
 ---
 # CSize Class
 
@@ -101,7 +100,7 @@ BOOL operator==(SIZE size) const throw();
 
 ### Remarks
 
-Returns nonzero if the sizes are equal, otherwize 0.
+Returns nonzero if the sizes are equal, otherwise 0.
 
 ### Example
 

docs/build-insights/tutorials/build-insights-function-view.md

@@ -63,7 +63,7 @@ When the build finishes, an Event Trace Log (ETL) file opens. It's saved in the
 In the window for the ETL file, choose the **Functions** tab. It shows the functions that were compiled and the time it took to generate the code for each function. If the amount of code generated for a function is negligible, it won't appear in the list to avoid degrading build event collection performance.
 
 :::image type="complex" source="./media/functions-view-before-fix.png" alt-text="Screenshot of the Build Insights Functions view file.":::
-In the Function Name column, performPhysicsCalculations() is highlighted and marked with a fire icon.:::
+In the Function Name column, performPhysicsCalculations() is highlighted and marked with a fire icon.
 :::image-end:::
 
 The **Time [sec, %]** column shows how long it took to compile each function in [wall clock responsibility time (WCTR)](https://devblogs.microsoft.com/cppblog/faster-cpp-builds-simplified-a-new-metric-for-time/#:~:text=Today%2C%20we%E2%80%99d%20like%20to%20teach%20you%20about%20a,your%20build%2C%20even%20in%20the%20presence%20of%20parallelism). This metric distributes the wall clock time among functions based on their use of parallel compiler threads. For example, if two different threads are compiling two different functions simultaneously within a one-second period, each function's WCTR is recorded as 0.5 seconds. This reflects each function's proportional share of the total compilation time, taking into account the resources each consumed during parallel execution. Thus, WCTR provides a better measure of the impact each function has on the overall build time in environments where multiple compilation activities occur simultaneously.
@@ -112,7 +112,7 @@ We rerun Build Insights from the main menu by choosing **Build** > **Run Build I
 The build time goes from 25.181 seconds to 13.376 seconds and the `performPhysicsCalculations` function doesn't show up anymore in the **Functions** view because it doesn't contribute enough to the build time to be counted.
 
 :::image type="complex" source="./media/functions-view-after-fix.png" alt-text="Screenshot of the 2D vector header file.":::
-In the Function Name column, performPhysicsCalculations() is highlighted and marked with a fire icon.:::
+In the Function Name column, performPhysicsCalculations() is highlighted and marked with a fire icon.
 :::image-end:::
 
 The Diagnostics Session time is the overall time it took do the build plus any overhead for gathering the Build Insights data.

docs/build/reference/dumpbin-options.md

@@ -1,9 +1,8 @@
 ---
 title: "DUMPBIN options"
 description: "Reference guide to the Microsoft DUMPBIN utility command-line options."
-ms.date: "02/09/2020"
+ms.date: 02/09/2020
 helpviewer_keywords: ["DUMPBIN program, options"]
-ms.assetid: 563b696e-7599-4480-94b9-014776289ec8
 ---
 # DUMPBIN options
 
@@ -49,7 +48,7 @@ DUMPBIN has the following options:
 
 - [/PDBPATH\[:VERBOSE\]](pdbpath.md)
 
-- [/RANGEE:vaMin\[,vaMax\]](range.md)
+- [/RANGE:vaMin\[,vaMax\]](range.md)
 
 - [/RAWDATA\[:{NONE\|1\|2\|4\|8}\[,#\]\]](rawdata.md)
 

docs/build/reference/gs-buffer-security-check.md

@@ -1,10 +1,9 @@
 ---
-description: "Learn more about: /GS (Buffer Security Check)"
 title: "/GS (Buffer Security Check)"
-ms.date: "11/04/2016"
+description: "Learn more about: /GS (Buffer Security Check)"
+ms.date: 11/04/2016
 f1_keywords: ["VC.Project.VCCLWCECompilerTool.BufferSecurityCheck", "VC.Project.VCCLCompilerTool.BufferSecurityCheck"]
 helpviewer_keywords: ["buffers [C++], buffer overruns", "buffer overruns, compiler /GS switch", "GS compiler option [C++]", "/GS compiler option [C++]", "security check compiler option [C++]", "-GS compiler option [C++]", "buffers [C++], avoiding overruns"]
-ms.assetid: 8d8a5ea1-cd5e-42e1-bc36-66e1cd7e731e
 ---
 # /GS (Buffer Security Check)
 
@@ -29,11 +28,8 @@ On functions that the compiler recognizes as subject to buffer overrun problems,
 A buffer overrun security check is performed on a *GS buffer*. A GS buffer can be one of these:
 
 - An array that is larger than 4 bytes, has more than two elements, and has an element type that is not a pointer type.
-
 - A data structure whose size is more than 8 bytes and contains no pointers.
-
-- A buffer allocated by using the [_alloca](../../c-runtime-library/reference/alloca.md) function.
-
+- A buffer allocated by using the [`_alloca`](../../c-runtime-library/reference/alloca.md) function.
 - Any class or structure that contains a GS buffer.
 
 For example, the following statements declare GS buffers.
@@ -57,16 +53,14 @@ struct { int a; int b; };
 
 ## Initialize the Security Cookie
 
-The **/GS** compiler option requires that the security cookie be initialized before any function that uses the cookie is run. The security cookie must be initialized immediately on entry to an EXE or DLL. This is done automatically if you use the default VCRuntime entry points: mainCRTStartup, wmainCRTStartup, WinMainCRTStartup, wWinMainCRTStartup, or _DllMainCRTStartup. If you use an alternate entry point, you must manually initialize the security cookie by calling [__security_init_cookie](../../c-runtime-library/reference/security-init-cookie.md).
+The **/GS** compiler option requires that the security cookie be initialized before any function that uses the cookie is run. The security cookie must be initialized immediately on entry to an EXE or DLL. This is done automatically if you use the default VCRuntime entry points: `mainCRTStartup`, `wmainCRTStartup`, `WinMainCRTStartup`, `wWinMainCRTStartup`, or `_DllMainCRTStartup`. If you use an alternate entry point, you must manually initialize the security cookie by calling [`__security_init_cookie`](../../c-runtime-library/reference/security-init-cookie.md).
 
 ## What Is Protected
 
 The **/GS** compiler option protects the following items:
 
 - The return address of a function call.
-
 - The address of an exception handler for a function.
-
 - Vulnerable function parameters.
 
 On all platforms, **/GS** attempts to detect buffer overruns into the return address. Buffer overruns are more easily exploited on platforms such as x86 and x64, which use calling conventions that store the return address of a function call on the stack.
@@ -80,15 +74,10 @@ A vulnerable parameter is allocated before the cookie and local variables. A buf
 The compiler does not make copies of vulnerable parameters in the following situations:
 
 - Functions that do not contain a GS buffer.
-
-- Optimizations ([/O options](o-options-optimize-code.md)) are not enabled.
-
+- Optimizations ([`/O` options](o-options-optimize-code.md)) are not enabled.
 - Functions that have a variable argument list (...).
-
 - Functions that are marked with [naked](../../cpp/naked-cpp.md).
-
 - Functions that contain inline assembly code in the first statement.
-
 - A parameter is used only in ways that are less likely to be exploitable in the event of a buffer overrun.
 
 ## What Is Not Protected
@@ -100,9 +89,7 @@ Even if you use **/GS**, always try to write secure code that has no buffer over
 ### To set this compiler option in Visual Studio
 
 1. Open the project's **Property Pages** dialog box. For details, see [Set C++ compiler and build properties in Visual Studio](../working-with-project-properties.md).
-
 1. Select the **Configuration Properties** > **C/C++** > **Code Generation** property page.
-
 1. Modify the **Buffer Security Check** property.
 
 ### To set this compiler option programmatically
@@ -138,5 +125,5 @@ int main() {
 
 ## See also
 
-[MSVC Compiler Options](compiler-options.md)<br/>
+[MSVC Compiler Options](compiler-options.md)\
 [MSVC Compiler Command-Line Syntax](compiler-command-line-syntax.md)

docs/c-runtime-library/reference/atanh-atanhf-atanhl.md

@@ -1,14 +1,13 @@
 ---
 title: "atanh, atanhf, atanhl"
 description: "API reference for atanh, atanhf, and atanhl; which calculate the inverse hyperbolic tangent of a floating-point value."
-ms.date: "08/31/2020"
+ms.date: 08/31/2020
 api_name: ["atanhl", "atanhf", "atanh", "_o_atanh", "_o_atanhf", "_o_atanhl"]
 api_location: ["msvcrt.dll", "msvcr80.dll", "msvcr90.dll", "msvcr100.dll", "msvcr100_clr0400.dll", "msvcr110.dll", "msvcr110_clr0400.dll", "msvcr120.dll", "msvcr120_clr0400.dll", "ucrtbase.dll", "api-ms-win-crt-math-l1-1-0.dll"]
 api_type: ["DLLExport"]
 topic_type: ["apiref"]
 f1_keywords: ["atanhl", "atanhf", "atanh"]
-helpviewer_keywords: ["atanhf function", "atanhl function", "atanh funciton"]
-ms.assetid: 83a43b5b-2580-4461-854f-dc84236d9f32
+helpviewer_keywords: ["atanhf function", "atanhl function", "atanh function"]
 ---
 # `atanh`, `atanhf`, `atanhl`
 

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

@@ -1,14 +1,13 @@
 ---
-description: "Learn more about: mbrtowc"
 title: "mbrtowc"
-ms.date: "4/2/2020"
+description: "Learn more about: mbrtowc"
+ms.date: 4/2/2020
 api_name: ["mbrtowc", "_o_mbrtowc"]
 api_location: ["msvcrt.dll", "msvcr80.dll", "msvcr90.dll", "msvcr100.dll", "msvcr100_clr0400.dll", "msvcr110.dll", "msvcr110_clr0400.dll", "msvcr120.dll", "msvcr120_clr0400.dll", "ucrtbase.dll", "api-ms-win-crt-convert-l1-1-0.dll"]
 api_type: ["DLLExport"]
 topic_type: ["apiref"]
 f1_keywords: ["mbrtowc"]
 helpviewer_keywords: ["mbrtowc function"]
-ms.assetid: a1e87fcc-6de0-4ca1-bf26-508d28490286
 ---
 # `mbrtowc`
 
@@ -100,7 +99,7 @@ int Sample(char* szIn, wchar_t* wcOut, int nMax)
     szLocal = setlocale(LC_ALL, "French_Canada.1252");
     if (!szLocal)
     {
-        printf("The fuction setlocale(LC_ALL, \"French_Canada.1252\") failed!\n");
+        printf("The function setlocale(LC_ALL, \"French_Canada.1252\") failed!\n");
         return 1;
     }
 
@@ -110,7 +109,7 @@ int Sample(char* szIn, wchar_t* wcOut, int nMax)
     // from a previous call to setlocale.
     if (_setmbcp(_MB_CP_SBCS) == -1)
     {
-        printf("The fuction _setmbcp(_MB_CP_SBCS) failed!");
+        printf("The function _setmbcp(_MB_CP_SBCS) failed!");
         return 1;
     }
 

docs/c-runtime-library/reference/strtoimax-strtoimax-l-wcstoimax-wcstoimax-l.md

@@ -1,14 +1,13 @@
 ---
-description: "Learn more about: strtoimax, _strtoimax_l, wcstoimax, _wcstoimax_l"
 title: "strtoimax, _strtoimax_l, wcstoimax, _wcstoimax_l"
-ms.date: "11/04/2016"
+description: "Learn more about: strtoimax, _strtoimax_l, wcstoimax, _wcstoimax_l"
+ms.date: 11/04/2016
 api_name: ["wcstoimax", "_wcstoimax_l", "_strtoimax_l", "strtoimax"]
 api_location: ["msvcrt.dll", "msvcr80.dll", "msvcr90.dll", "msvcr100.dll", "msvcr100_clr0400.dll", "msvcr110.dll", "msvcr110_clr0400.dll", "msvcr120.dll", "msvcr120_clr0400.dll", "ucrtbase.dll", "api-ms-win-crt-convert-l1-1-0.dll"]
 api_type: ["DLLExport"]
 topic_type: ["apiref"]
 f1_keywords: ["wcstoimax", "_tcstoimax", "strtoimax", "_wcstoimax_l", "_strtoimax_l", "_tcstoimax_l"]
-helpviewer_keywords: ["strtoimax funciton", "conversion functions", "_strtoimax_l function", "_wcstoimax_l function", "wcstoimax function"]
-ms.assetid: 4530d3dc-aaac-4a76-b7cf-29ae3c98d0ae
+helpviewer_keywords: ["strtoimax function", "conversion functions", "_strtoimax_l function", "_wcstoimax_l function", "wcstoimax function"]
 ---
 # `strtoimax`, `_strtoimax_l`, `wcstoimax`, `_wcstoimax_l`
 

docs/code-quality/c28310.md

@@ -1,9 +1,9 @@
 ---
-description: "Learn more about: Warning C28310"
 title: Warning C28310
+description: "Learn more about: Warning C28310"
 ms.date: 11/04/2016
 f1_keywords: ["C28310"]
-ms.assetid: 51054ca8-01b6-454b-9853-f05f1c817b18
+helpviewer_keywords: ["C28310"]
 ---
 # Warning C28310
 

docs/code-quality/c28311.md

@@ -1,9 +1,9 @@
 ---
-description: "Learn more about: Warning C28311"
 title: Warning C28311
+description: "Learn more about: Warning C28311"
 ms.date: 11/04/2016
 f1_keywords: ["C28311"]
-ms.assetid: 2c76e07a-4418-40ef-8a77-c62774bc3677
+helpviewer_keywords: ["C28311"]
 ---
 # Warning C28311
 

docs/code-quality/c28312.md

@@ -1,9 +1,9 @@
 ---
-description: "Learn more about: Warning C28312"
 title: Warning C28312
+description: "Learn more about: Warning C28312"
 ms.date: 11/04/2016
 f1_keywords: ["C28312"]
-ms.assetid: 19828546-33c9-4373-b7df-2a362ca12637
+helpviewer_keywords: ["C28312"]
 ---
 # Warning C28312