Merge pull request #5660 from MicrosoftDocs/main

9/10/2024 AM Publish

Author: Albertyang0

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

@@ -1,14 +1,13 @@
 ---
-description: "Learn more about: _calloc_dbg"
 title: "_calloc_dbg"
+description: "Learn more about: _calloc_dbg"
 ms.date: "11/04/2016"
 api_name: ["_calloc_dbg"]
 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_type: ["DLLExport"]
 topic_type: ["apiref"]
 f1_keywords: ["_calloc_dbg", "calloc_dbg"]
 helpviewer_keywords: ["_calloc_dbg function", "calloc_dbg function"]
-ms.assetid: 7f62c42b-eb9f-4de5-87d0-df57036c87de
 ---
 # `_calloc_dbg`
 
@@ -37,7 +36,7 @@ Requested size of each memory block (bytes).
 *`blockType`*\
 Requested type of memory block: `_CLIENT_BLOCK` or `_NORMAL_BLOCK`.
 
-For information about the allocation block types and how they're used, see[Types of blocks on the debug heap](../crt-debug-heap-details.md#types-of-blocks-on-the-debug-heap).
+For information about the allocation block types and how they're used, see [Types of blocks on the debug heap](../crt-debug-heap-details.md#types-of-blocks-on-the-debug-heap).
 
 *`filename`*\
 Pointer to name of the source file that requested allocation operation or `NULL`.

docs/cppcx/collections-c-cx.md

@@ -1,8 +1,7 @@
 ---
-description: "Learn more about: Collections (C++/CX)"
 title: "Collections (C++/CX)"
+description: "Learn more about: Collections (C++/CX)"
 ms.date: "11/19/2018"
-ms.assetid: 914da30b-aac5-4cd7-9da3-a5ac08cdd72c
 ---
 # Collections (C++/CX)
 
@@ -16,7 +15,7 @@ The Windows Runtime defines the interfaces for collections and related types, an
 
 - The [Platform::Collections::Map class](../cppcx/platform-collections-map-class.md) resembles the [std::map class](../standard-library/map-class.md).
 
-- [Platform::Collections::VectorView class](../cppcx/platform-collections-vectorview-class.md) and[Platform::Collections::MapView class](../cppcx/platform-collections-mapview-class.md) are read-only versions of `Vector` and `Map`.
+- [Platform::Collections::VectorView class](../cppcx/platform-collections-vectorview-class.md) and [Platform::Collections::MapView class](../cppcx/platform-collections-mapview-class.md) are read-only versions of `Vector` and `Map`.
 
 - Iterators are defined in the [Platform::Collections Namespace](../cppcx/platform-collections-namespace.md). These iterators satisfy the requirements for STL iterators and enable the use of [std::find](../standard-library/algorithm-functions.md#find),  [std::count_if](../standard-library/algorithm-functions.md#count_if), and other STL algorithms on any [Windows::Foundation::Collections](/uwp/api/windows.foundation.collections) interface type or [Platform::Collections](../cppcx/platform-collections-namespace.md) concrete type. For example, this means that you can iterate a collection in a Windows Runtime component that's created in C# and apply an STL algorithm to it.
 
@@ -140,6 +139,6 @@ The [Windows::Foundation::Collections::VectorChangedEventHandler](/uwp/api/windo
 
 ## See also
 
-[Type System](../cppcx/type-system-c-cx.md)<br/>
-[C++/CX Language Reference](../cppcx/visual-c-language-reference-c-cx.md)<br/>
+[Type System](../cppcx/type-system-c-cx.md)\
+[C++/CX Language Reference](../cppcx/visual-c-language-reference-c-cx.md)\
 [Namespaces Reference](../cppcx/namespaces-reference-c-cx.md)

docs/cppcx/platform-object-class.md

@@ -1,11 +1,10 @@
 ---
-description: "Learn more about: Platform::Object Class"
 title: "Platform::Object Class"
+description: "Learn more about: Platform::Object Class"
 ms.date: "12/30/2016"
 ms.topic: "reference"
 f1_keywords: ["VCCORLIB/Platform::Object::Object", "VCCORLIB/Platform::Object::Equals", "VCCORLIB/Platform::Object::GetHashCode", "VCCORLIB/Platform::Object::ReferenceEquals", "VCCORLIB/Platform::ToString", "VCCORLIB/Platform::GetType"]
 helpviewer_keywords: ["Object class"]
-ms.assetid: 709e84a8-0bff-471b-bc14-63e424080b5a
 ---
 # Platform::Object Class
 
@@ -104,7 +103,7 @@ A [Platform::Type](../cppcx/platform-type-class.md) object that describes the ru
 
 The static [Type::GetTypeCode](../cppcx/platform-type-class.md#gettypecode) can be used to get a [Platform::TypeCode Enumeration](../cppcx/platform-typecode-enumeration.md) value that represents the current type. This is mostly useful for built-in types. The type code for any ref class besides [Platform::String](../cppcx/platform-string-class.md) is Object (1).
 
-The [Windows::UI::Xaml::Interop::TypeName](/uwp/api/windows.ui.xaml.interop.typename) class is used in the Windows APIs as a language-independent way of passing type information between Windows components and apps. The T[Platform::Type Class](../cppcx/platform-type-class.md) has operators for converting between `Type` and `TypeName`.
+The [Windows::UI::Xaml::Interop::TypeName](/uwp/api/windows.ui.xaml.interop.typename) class is used in the Windows APIs as a language-independent way of passing type information between Windows components and apps. The [Platform::Type Class](../cppcx/platform-type-class.md) has operators for converting between `Type` and `TypeName`.
 
 Use the [typeid](../extensions/typeid-cpp-component-extensions.md) operator to return a `Platform::Type` object for a class name, for example when navigating between XAML pages:
 
@@ -173,6 +172,6 @@ public:
 
 ## See also
 
-[Platform Namespace](platform-namespace-c-cx.md)<br/>
-[Platform::Type Class](platform-type-class.md)<br/>
+[Platform Namespace](platform-namespace-c-cx.md)\
+[Platform::Type Class](platform-type-class.md)\
 [Type System](type-system-c-cx.md)

docs/get-started/tutorial-console-cpp.md

@@ -360,7 +360,7 @@ Let's handle division by zero more gracefully so that it's easier for the user t
             cin >> x >> oper >> y;
             if (oper == '/' && y == 0)
             {
-                cout << "Attempted to divide by zero!" << endl;
+                cout << "Math error: Attempted to divide by zero!" << endl;
                 continue;
             }
             else

docs/mfc/mfc-activex-controls-using-fonts.md

@@ -1,10 +1,9 @@
 ---
-description: "Learn more about: MFC ActiveX Controls: Using Fonts"
 title: "MFC ActiveX Controls: Using Fonts"
+description: "Learn more about: MFC ActiveX Controls: Using Fonts"
 ms.date: "11/19/2018"
 f1_keywords: ["OnFontChanged", "HeadingFont", "InternalFont"]
 helpviewer_keywords: ["notifications [MFC], MFC ActiveX controls fonts", "OnDraw method, MFC ActiveX controls", "InternalFont method [MFC]", "SetFont method [MFC]", "OnFontChanged method [MFC]", "IPropertyNotifySink class [MFC]", "MFC ActiveX controls [MFC], fonts", "Stock Font property [MFC]", "HeadingFont property [MFC]", "GetFont method [MFC]", "SelectStockFont method [MFC]", "fonts [MFC], ActiveX controls"]
-ms.assetid: 7c51d602-3f5a-481d-84d1-a5d8a3a71761
 ---
 # MFC ActiveX Controls: Using Fonts
 
@@ -112,7 +111,7 @@ To implement a custom Font property, you use the Add Property Wizard to add the
 
 1. Click **Finish**.
 
-The Add Property Wizard creates the code to add the `HeadingFont` custom property to the `CSampleCtrl` class and the SAMPLE.IDL file. Because `HeadingFont` is a Get/Set property type, the Add Property Wizard modifies the `CSampleCtrl` class's dispatch map to include a DISP_PROPERTY_EX_ID[DISP_PROPERTY_EX](reference/dispatch-maps.md#disp_property_ex) macro entry:
+The Add Property Wizard creates the code to add the `HeadingFont` custom property to the `CSampleCtrl` class and the SAMPLE.IDL file. Because `HeadingFont` is a Get/Set property type, the Add Property Wizard modifies the `CSampleCtrl` class's dispatch map to include a DISP_PROPERTY_EX_ID [DISP_PROPERTY_EX](reference/dispatch-maps.md#disp_property_ex) macro entry:
 
 [!code-cpp[NVC_MFC_AxFont#5](codesnippet/cpp/mfc-activex-controls-using-fonts_5.cpp)]
 
@@ -215,6 +214,6 @@ After these changes have been made to your project, rebuild the project and use
 
 ## See also
 
-[MFC ActiveX Controls](mfc-activex-controls.md)<br/>
-[MFC ActiveX Controls: Using Pictures in an ActiveX Control](mfc-activex-controls-using-pictures-in-an-activex-control.md)<br/>
+[MFC ActiveX Controls](mfc-activex-controls.md)\
+[MFC ActiveX Controls: Using Pictures in an ActiveX Control](mfc-activex-controls-using-pictures-in-an-activex-control.md)\
 [MFC ActiveX Controls: Using Stock Property Pages](mfc-activex-controls-using-stock-property-pages.md)

docs/mfc/tn014-custom-controls.md

@@ -1,10 +1,9 @@
 ---
-description: "Learn more about: TN014: Custom Controls"
 title: "TN014: Custom Controls"
+description: "Learn more about: TN014: Custom Controls"
 ms.date: "06/28/2018"
 f1_keywords: ["vc.controls"]
 helpviewer_keywords: ["TN014", "custom controls [MFC]"]
-ms.assetid: 1917a498-f643-457c-b570-9a0af7dbf7bb
 ---
 # TN014: Custom Controls
 
@@ -118,13 +117,13 @@ There are three common ways these are related:
 
 - `CWnd` is attached to an existing `HWND` and you can modify the behavior in a derived class. This is called dynamic subclassing because we are changing the behavior, and therefore the class, of a Windows object at run time.
 
-You can achieve dynamic subclassing by using the methods [CWnd::SubclassWindow](../mfc/reference/cwnd-class.md#subclasswindow) and[CWnd::SubclassDlgItem](../mfc/reference/cwnd-class.md#subclassdlgitem).
+You can achieve dynamic subclassing by using the methods [CWnd::SubclassWindow](../mfc/reference/cwnd-class.md#subclasswindow) and [CWnd::SubclassDlgItem](../mfc/reference/cwnd-class.md#subclassdlgitem).
 
 Both routines attach a `CWnd` object to an existing `HWND`. `SubclassWindow` takes the `HWND` directly. `SubclassDlgItem` is a helper function that takes a control ID and the parent window. `SubclassDlgItem` is designed for attaching C++ objects to dialog controls created from a dialog template.
 
 See the [CTRLTEST](../overview/visual-cpp-samples.md) example for several examples of when to use `SubclassWindow` and `SubclassDlgItem`.
 
 ## See also
 
-[Technical Notes by Number](../mfc/technical-notes-by-number.md)<br/>
+[Technical Notes by Number](../mfc/technical-notes-by-number.md)\
 [Technical Notes by Category](../mfc/technical-notes-by-category.md)

docs/sanitizers/asan-shadow-bytes.md

@@ -7,7 +7,7 @@ helpviewer_keywords: ["Shadow bytes", "AddressSanitizer shadow bytes","Address S
 
 # AddressSanitizer shadow bytes
 
-We briefly summarize the concept of shadow bytes and how they can be used by the runtime implementation of [`/fsanitize=address`](../build/reference/fsanitize.md). For further details, we refer you to the [seminal paper](https://www.usenix.org/system/files/conference/atc12/atc12-final39.pdf) and the [AddressSanitizer algorithm](https://github.com/google/sanitizers/wiki/AddressSanitizerAlgorithm).
+We briefly summarize the concept of shadow bytes and how they can be used by the runtime implementation of [`/fsanitize=address`](../build/reference/fsanitize.md). For further details, we refer you to the initial research [AddressSanitizer -  Serebryany, et al](https://www.usenix.org/system/files/conference/atc12/atc12-final39.pdf) and the [current AddressSanitizer algorithm documentation](https://github.com/google/sanitizers/wiki/AddressSanitizerAlgorithm).
 
 ## Core concept