MicrosoftDocs
diff --git a/‎docs/atl/reference/iolecontrolimpl-class.md
Lines changed: 5 additions & 6 deletions b/‎docs/atl/reference/iolecontrolimpl-class.md
Lines changed: 5 additions & 6 deletions
diff --git a/‎docs/atl/reference/ipersiststorageimpl-class.md
Lines changed: 10 additions & 11 deletions b/‎docs/atl/reference/ipersiststorageimpl-class.md
Lines changed: 10 additions & 11 deletions
diff --git a/‎docs/build/reference/zc-alignednew.md
Lines changed: 2 additions & 2 deletions b/‎docs/build/reference/zc-alignednew.md
Lines changed: 2 additions & 2 deletions
diff --git a/‎docs/c-runtime-library/reference/itoa-itow.md
Lines changed: 1 addition & 2 deletions b/‎docs/c-runtime-library/reference/itoa-itow.md
Lines changed: 1 addition & 2 deletions
diff --git a/‎docs/cloud/cloud-and-web-programming-in-visual-cpp.md
Lines changed: 4 additions & 5 deletions b/‎docs/cloud/cloud-and-web-programming-in-visual-cpp.md
Lines changed: 4 additions & 5 deletions
diff --git a/‎docs/code-quality/c6029.md
Lines changed: 3 additions & 3 deletions b/‎docs/code-quality/c6029.md
Lines changed: 3 additions & 3 deletions
diff --git a/‎docs/cpp/type-conversions-and-type-safety-modern-cpp.md
Lines changed: 5 additions & 6 deletions b/‎docs/cpp/type-conversions-and-type-safety-modern-cpp.md
Lines changed: 5 additions & 6 deletions
@@ -1,10 +1,9 @@
 ---
-description: "Learn more about: IOleControlImpl Class"
 title: "IOleControlImpl Class"
+description: "Learn more about: IOleControlImpl Class"
 ms.date: "11/04/2016"
 f1_keywords: ["IOleControlImpl", "ATLCTL/ATL::IOleControlImpl", "ATLCTL/ATL::IOleControlImpl::FreezeEvents", "ATLCTL/ATL::IOleControlImpl::GetControlInfo", "ATLCTL/ATL::IOleControlImpl::OnAmbientPropertyChange", "ATLCTL/ATL::IOleControlImpl::OnMnemonic"]
 helpviewer_keywords: ["IOleControlImpl class"]
-ms.assetid: 5a4255ad-ede4-49ca-ba9a-07c2e919fa85
 ---
 # IOleControlImpl Class
 
@@ -22,7 +21,7 @@ class IOleControlImpl
 
 #### Parameters
 
-*T*<br/>
+*T*\
 Your class, derived from `IOleControlImpl`.
 
 ## Members
@@ -76,7 +75,7 @@ HRESULT GetControlInfo(LPCONTROLINFO pCI);
 
 ### Remarks
 
-See [IOleControl:GetControlInfo](/windows/win32/api/ocidl/nf-ocidl-iolecontrol-getcontrolinfo) in the Windows SDK.
+See [IOleControl::GetControlInfo](/windows/win32/api/ocidl/nf-ocidl-iolecontrol-getcontrolinfo) in the Windows SDK.
 
 ### Return Value
 
@@ -116,6 +115,6 @@ See [IOleControl::OnMnemonic](/windows/win32/api/ocidl/nf-ocidl-iolecontrol-onmn
 
 ## See also
 
-[IOleObjectImpl Class](../../atl/reference/ioleobjectimpl-class.md)<br/>
-[ActiveX Controls Interfaces](/windows/win32/com/activex-controls-interfaces)<br/>
+[IOleObjectImpl Class](../../atl/reference/ioleobjectimpl-class.md)\
+[ActiveX Controls Interfaces](/windows/win32/com/activex-controls-interfaces)\
 [Class Overview](../../atl/atl-class-overview.md)
@@ -1,10 +1,9 @@
 ---
-description: "Learn more about: IPersistStorageImpl Class"
 title: "IPersistStorageImpl Class"
+description: "Learn more about: IPersistStorageImpl Class"
 ms.date: "11/04/2016"
 f1_keywords: ["IPersistStorageImpl", "ATLCOM/ATL::IPersistStorageImpl", "ATLCOM/ATL::IPersistStorageImpl::GetClassID", "ATLCOM/ATL::IPersistStorageImpl::HandsOffStorage", "ATLCOM/ATL::IPersistStorageImpl::InitNew", "ATLCOM/ATL::IPersistStorageImpl::IsDirty", "ATLCOM/ATL::IPersistStorageImpl::Load", "ATLCOM/ATL::IPersistStorageImpl::Save", "ATLCOM/ATL::IPersistStorageImpl::SaveCompleted"]
 helpviewer_keywords: ["storage, ATL", "IPersistStorageImpl class"]
-ms.assetid: d652f02c-239c-47c7-9a50-3e9fc3014fff
 ---
 # IPersistStorageImpl Class
 
@@ -22,7 +21,7 @@ class ATL_NO_VTABLE IPersistStorageImpl : public IPersistStorage
 
 #### Parameters
 
-*T*<br/>
+*T*\
 Your class, derived from `IPersistStorageImpl`.
 
 ## Members
@@ -97,7 +96,7 @@ STDMETHOD(InitNew)(IStorage*);
 
 The ATL implementation delegates to the [IPersistStreamInit](/windows/win32/api/ocidl/nn-ocidl-ipersiststreaminit) interface.
 
-See [IPersistStorage:InitNew](/windows/win32/api/objidl/nf-objidl-ipersiststorage-initnew) in the Windows SDK.
+See [IPersistStorage::InitNew](/windows/win32/api/objidl/nf-objidl-ipersiststorage-initnew) in the Windows SDK.
 
 ## <a name="isdirty"></a> IPersistStorageImpl::IsDirty
 
@@ -111,7 +110,7 @@ STDMETHOD(IsDirty)(void);
 
 The ATL implementation delegates to the [IPersistStreamInit](/windows/win32/api/ocidl/nn-ocidl-ipersiststreaminit) interface.
 
-See [IPersistStorage:IsDirty](/windows/win32/api/objidl/nf-objidl-ipersiststorage-isdirty) in the Windows SDK.
+See [IPersistStorage::IsDirty](/windows/win32/api/objidl/nf-objidl-ipersiststorage-isdirty) in the Windows SDK.
 
 ## <a name="load"></a> IPersistStorageImpl::Load
 
@@ -125,7 +124,7 @@ STDMETHOD(Load)(IStorage* pStorage);
 
 The ATL implementation delegates to the [IPersistStreamInit](/windows/win32/api/ocidl/nn-ocidl-ipersiststreaminit) interface. `Load` uses a stream named "Contents" to retrieve the object's data. The [Save](#save) method originally creates this stream.
 
-See [IPersistStorage:Load](/windows/win32/api/objidl/nf-objidl-ipersiststorage-load) in the Windows SDK.
+See [IPersistStorage::Load](/windows/win32/api/objidl/nf-objidl-ipersiststorage-load) in the Windows SDK.
 
 ## <a name="save"></a> IPersistStorageImpl::Save
 
@@ -139,7 +138,7 @@ STDMETHOD(Save)(IStorage* pStorage, BOOL fSameAsLoad);
 
 The ATL implementation delegates to the [IPersistStreamInit](/windows/win32/api/ocidl/nn-ocidl-ipersiststreaminit) interface. When `Save` is first called, it creates a stream named "Contents" on the specified storage. This stream is then used in later calls to `Save` and in calls to [Load](#load).
 
-See [IPersistStorage:Save](/windows/win32/api/objidl/nf-objidl-ipersiststorage-save) in the Windows SDK.
+See [IPersistStorage::Save](/windows/win32/api/objidl/nf-objidl-ipersiststorage-save) in the Windows SDK.
 
 ## <a name="savecompleted"></a> IPersistStorageImpl::SaveCompleted
 
@@ -155,11 +154,11 @@ Returns S_OK.
 
 ### Remarks
 
-See [IPersistStorage:SaveCompleted](/windows/win32/api/objidl/nf-objidl-ipersiststorage-savecompleted) in the Windows SDK.
+See [IPersistStorage::SaveCompleted](/windows/win32/api/objidl/nf-objidl-ipersiststorage-savecompleted) in the Windows SDK.
 
 ## See also
 
-[Storages and Streams](/windows/win32/Stg/storages-and-streams)<br/>
-[IPersistStreamInitImpl Class](../../atl/reference/ipersiststreaminitimpl-class.md)<br/>
-[IPersistPropertyBagImpl Class](../../atl/reference/ipersistpropertybagimpl-class.md)<br/>
+[Storages and Streams](/windows/win32/Stg/storages-and-streams)\
+[IPersistStreamInitImpl Class](../../atl/reference/ipersiststreaminitimpl-class.md)\
+[IPersistPropertyBagImpl Class](../../atl/reference/ipersistpropertybagimpl-class.md)\
 [Class Overview](../../atl/atl-class-overview.md)
@@ -1,6 +1,6 @@
 ---
-description: "Learn more about: /Zc:alignedNew (C++17 over-aligned allocation)"
 title: "/Zc:alignedNew (C++17 over-aligned allocation)"
+description: "Learn more about: /Zc:alignedNew (C++17 over-aligned allocation)"
 ms.date: "05/18/2019"
 f1_keywords: ["/Zc:alignedNew"]
 helpviewer_keywords: ["/Zc:alignedNew", "Zc:alignedNew", "-Zc:alignedNew"]
@@ -17,7 +17,7 @@ Enable support for C++17 over-aligned **`new`**, dynamic memory allocation align
 
 The MSVC compiler and library support C++17 standard over-aligned dynamic memory allocation. When the **`/Zc:alignedNew`** option is specified, a dynamic allocation such as `new Example;` respects the alignment of `Example` even when it's greater than `max_align_t`, the largest alignment required for any fundamental type. When the alignment of the allocated type is no more than the alignment guaranteed by the original operator **`new`**, available as the value of the predefined macro `__STDCPP_DEFAULT_NEW_ALIGNMENT__`, the statement `new Example;` results in a call to `::operator new(size_t)` as it did in C++14. When the alignment is greater than `__STDCPP_DEFAULT_NEW_ALIGNMENT__`, the implementation instead obtains the memory by using `::operator new(size_t, align_val_t)`. Similarly, deletion of over-aligned types invokes `::operator delete(void*, align_val_t)` or the sized delete signature `::operator delete(void*, size_t, align_val_t)`.
 
-The **`/Zc:alignedNew`** option is only available when [`/std:c++17`](std-specify-language-standard-version.md) or later is enabled. Under **`/std:c++17`** or later, **`/Zc:alignedNew`** is enabled by default to conform to the C++ standard. If the only reason you implement operator **`new`** and **`delete`** is to support over-aligned allocations, you may no longer need this code in C++17 or later modes. To turn off this option and revert to the C++14 behavior of **`new`** and **`delete`** when you use **`/std::c++17`** or later, specify **`/Zc:alignedNew-`**. If you implement operator **`new`** and **`delete`** but you're not ready to implement the over-aligned operator **`new`** and **`delete`** overloads that have the `align_val_t` parameter, use the **`/Zc:alignedNew-`** option to prevent the compiler and Standard Library from generating calls to the over-aligned overloads. The [`/permissive-`](permissive-standards-conformance.md) option doesn't change the default setting of **`/Zc:alignedNew`**.
+The **`/Zc:alignedNew`** option is only available when [`/std:c++17`](std-specify-language-standard-version.md) or later is enabled. Under **`/std:c++17`** or later, **`/Zc:alignedNew`** is enabled by default to conform to the C++ standard. If the only reason you implement operator **`new`** and **`delete`** is to support over-aligned allocations, you may no longer need this code in C++17 or later modes. To turn off this option and revert to the C++14 behavior of **`new`** and **`delete`** when you use **`/std:c++17`** or later, specify **`/Zc:alignedNew-`**. If you implement operator **`new`** and **`delete`** but you're not ready to implement the over-aligned operator **`new`** and **`delete`** overloads that have the `align_val_t` parameter, use the **`/Zc:alignedNew-`** option to prevent the compiler and Standard Library from generating calls to the over-aligned overloads. The [`/permissive-`](permissive-standards-conformance.md) option doesn't change the default setting of **`/Zc:alignedNew`**.
 
 Support for **`/Zc:alignedNew`** is available starting in Visual Studio 2017 version 15.5.
 
 
@@ -8,7 +8,6 @@ api_type: ["DLLExport"]
 topic_type: ["apiref"]
 f1_keywords: ["_itoa", "_ltoa", "_ultoa", "_i64toa", "_ui64toa", "_itow", "_ltow", "_ultow", "_i64tow", "_ui64tow", "itoa", "ltoa", "ultoa", "i64toa", "ui64toa", "itow", "ltow", "ultow", "i64tow", "ui64tow", "itot", "_itot", "ltot", "_ltot", "ultot", "_ultot", "i64tot", "_i64tot", "ui64tot", "_ui64tot", "_MAX_ITOSTR_BASE16_COUNT", "_MAX_ITOSTR_BASE10_COUNT", "_MAX_ITOSTR_BASE8_COUNT", "_MAX_ITOSTR_BASE2_COUNT", "_MAX_LTOSTR_BASE16_COUNT", "_MAX_LTOSTR_BASE10_COUNT", "_MAX_LTOSTR_BASE8_COUNT", "_MAX_LTOSTR_BASE2_COUNT", "_MAX_ULTOSTR_BASE16_COUNT", "_MAX_ULTOSTR_BASE10_COUNT", "_MAX_ULTOSTR_BASE8_COUNT", "_MAX_ULTOSTR_BASE2_COUNT", "_MAX_I64TOSTR_BASE16_COUNT", "_MAX_I64TOSTR_BASE10_COUNT", "_MAX_I64TOSTR_BASE8_COUNT", "_MAX_I64TOSTR_BASE2_COUNT", "_MAX_U64TOSTR_BASE16_COUNT", "_MAX_U64TOSTR_BASE10_COUNT", "_MAX_U64TOSTR_BASE8_COUNT", "_MAX_U64TOSTR_BASE2_COUNT"]
 helpviewer_keywords: ["_itot function", "ui64toa function", "_ui64toa function", "converting integers", "itot function", "_i64tow function", "_i64toa function", "_itow function", "ui64tow function", "integers, converting", "itoa function", "_ui64tow function", "i64tow function", "itow function", "i64toa function", "converting numbers, to strings", "_itoa function"]
-ms.assetid: 46592a00-77bb-4e73-98c0-bf629d96cea6
 ---
 # `itoa`, `_itoa`, `ltoa`, `_ltoa`, `ultoa`, `_ultoa`, `_i64toa`, `_ui64toa`, `_itow`, `_ltow`, `_ultow`, `_i64tow`, `_ui64tow`
 
@@ -137,7 +136,7 @@ This example uses a conversion count macro to define a buffer large enough to co
 int main()
 {
     wchar_t buffer[_MAX_U64TOSTR_BASE2_COUNT];
-    std:wcout << _ui64tow(0xFFFFFFFFFFFFFFFFull, buffer, 2) << std::endl;
+    std::wcout << _ui64tow(0xFFFFFFFFFFFFFFFFull, buffer, 2) << std::endl;
 }
 ```
 
 
@@ -1,8 +1,7 @@
 ---
-description: "Learn more about: Cloud and Web Programming in Visual C++"
 title: "Cloud and Web Programming in Visual C++"
+description: "Learn more about: Cloud and Web Programming in Visual C++"
 ms.date: "05/14/2019"
-ms.assetid: b63611f1-9723-44d0-ba7f-c3ebef341313
 ms.topic: "overview"
 ms.custom: intro-overview
 ---
@@ -43,7 +42,7 @@ In C++, you have several options for connecting to the web and the cloud.
 
 - [Windows::Web::Http::HttpClient](/uwp/api/windows.web.http.httpclient)
 
-  A Windows Runtime HTTP client class modeled on the .NET Framework class of the same name in the System.Web namespace. `HttpClient` fully supports asynchronous upload and download over HTTP, and pipeline filters that enable the insertion of custom HTTP handlers into the pipeline. The Windows SDK includes sample filters for metered networks, OAuth authentication, and more. For apps that target only Universal Windows Platform, we recommend that you use the `Windows::Web:HttpClient` class.
+  A Windows Runtime HTTP client class modeled on the .NET Framework class of the same name in the System.Web namespace. `HttpClient` fully supports asynchronous upload and download over HTTP, and pipeline filters that enable the insertion of custom HTTP handlers into the pipeline. The Windows SDK includes sample filters for metered networks, OAuth authentication, and more. For apps that target only Universal Windows Platform, we recommend that you use the `Windows::Web::Http::HttpClient` class.
 
 - [IXMLHTTPRequest2 interface](/windows/win32/api/msxml6/nn-msxml6-ixmlhttprequest2)
 
@@ -55,6 +54,6 @@ In C++, you have several options for connecting to the web and the cloud.
 
 ## See also
 
-[C++ in Visual Studio](../overview/visual-cpp-in-visual-studio.md) <br/>
-[Microsoft Azure C and C++ Developer Center](https://azure.microsoft.com/develop/cpp/) <br/>
+[C++ in Visual Studio](../overview/visual-cpp-in-visual-studio.md)\
+[Microsoft Azure C and C++ Developer Center](https://azure.microsoft.com/develop/cpp/)\
 [Networks and web services (UWP)](/windows/uwp/networking/)
@@ -1,6 +1,6 @@
 ---
-description: "Learn more about: Warning C6029"
 title: Warning C6029
+description: "Learn more about: Warning C6029"
 ms.date: 2/07/2023
 f1_keywords: ["C6029", "USING_TAINTED_DATA", "__WARNING_USING_TAINTED_DATA"]
 helpviewer_keywords: ["C6029"]
@@ -35,7 +35,7 @@ void processData(FILE* file)
 }
 ```
 
-The fix for the issue depends on the nature of the data and the behavior of the annotated function that triggers the diagnostic. For more information, see the documentation for that function. A straightforward fix is to check the size before the second call to `std:fread`. In the next example, we throw an exception to terminate the function. Most real-world code would instead have an error recovery strategy that's specific to the scenario.
+The fix for the issue depends on the nature of the data and the behavior of the annotated function that triggers the diagnostic. For more information, see the documentation for that function. A straightforward fix is to check the size before the second call to `std::fread`. In the next example, we throw an exception to terminate the function. Most real-world code would instead have an error recovery strategy that's specific to the scenario.
 
 ```cpp
 void processData(FILE* file)
@@ -55,7 +55,7 @@ void processData(FILE* file)
 }
 ```
 
-In `std:fread` and similar functions, the code may need to read large amounts of data. To handle large data, you can allocate the size of the buffer dynamically after the size becomes known. Or, you can call `std:fread` multiple times as needed to read in the rest of the data. If you allocate the buffer dynamically, we recommend you put a limit on the size to avoid introducing an out-of-memory exploit for large values. We don't use this approach in our example because it's already bounded by the size of `uint8_t`.
+In `std::fread` and similar functions, the code may need to read large amounts of data. To handle large data, you can allocate the size of the buffer dynamically after the size becomes known. Or, you can call `std::fread` multiple times as needed to read in the rest of the data. If you allocate the buffer dynamically, we recommend you put a limit on the size to avoid introducing an out-of-memory exploit for large values. We don't use this approach in our example because it's already bounded by the size of `uint8_t`.
 
 ```cpp
 void processDataDynamic(FILE* file)
 
@@ -1,9 +1,8 @@
 ---
-description: "Learn more about: Type conversions and type safety"
 title: "Type conversions and type safety"
+description: "Learn more about: Type conversions and type safety"
 ms.date: "11/19/2019"
 ms.topic: "conceptual"
-ms.assetid: 629b361a-2ce1-4700-8b5d-ab4f57b245d5
 ---
 # Type conversions and type safety
 
@@ -105,7 +104,7 @@ The C-style cast operator is identical to the call operator () and is therefore
     int i = d;  // warning C4244 possible loss of data
     int j = static_cast<int>(d);       // No warning.
     string s = static_cast<string>(d); // Error C2440:cannot convert from
-                                       // double to std:string
+                                       // double to std::string
 
     // No error but not necessarily safe.
     Base* b = new Base();
@@ -173,7 +172,7 @@ The C-style cast operator is identical to the call operator () and is therefore
 
 ## See also
 
-[C++ type system](../cpp/cpp-type-system-modern-cpp.md)<br/>
-[Welcome back to C++](../cpp/welcome-back-to-cpp-modern-cpp.md)<br/>
-[C++ Language Reference](../cpp/cpp-language-reference.md)<br/>
+[C++ type system](../cpp/cpp-type-system-modern-cpp.md)\
+[Welcome back to C++](../cpp/welcome-back-to-cpp-modern-cpp.md)\
+[C++ Language Reference](../cpp/cpp-language-reference.md)\
 [C++ Standard Library](../standard-library/cpp-standard-library-reference.md)
Original file line number	Diff line number	Diff line change
`@@ -8,7 +8,6 @@ api_type: ["DLLExport"]`
`8`	`8`	`topic_type: ["apiref"]`
`9`	`9`	f1_keywords: ["_itoa", "_ltoa", "_ultoa", "_i64toa", "_ui64toa", "_itow", "_ltow", "_ultow", "_i64tow", "_ui64tow", "itoa", "ltoa", "ultoa", "i64toa", "ui64toa", "itow", "ltow", "ultow", "i64tow", "ui64tow", "itot", "_itot", "ltot", "_ltot", "ultot", "_ultot", "i64tot", "_i64tot", "ui64tot", "_ui64tot", "_MAX_ITOSTR_BASE16_COUNT", "_MAX_ITOSTR_BASE10_COUNT", "_MAX_ITOSTR_BASE8_COUNT", "_MAX_ITOSTR_BASE2_COUNT", "_MAX_LTOSTR_BASE16_COUNT", "_MAX_LTOSTR_BASE10_COUNT", "_MAX_LTOSTR_BASE8_COUNT", "_MAX_LTOSTR_BASE2_COUNT", "_MAX_ULTOSTR_BASE16_COUNT", "_MAX_ULTOSTR_BASE10_COUNT", "_MAX_ULTOSTR_BASE8_COUNT", "_MAX_ULTOSTR_BASE2_COUNT", "_MAX_I64TOSTR_BASE16_COUNT", "_MAX_I64TOSTR_BASE10_COUNT", "_MAX_I64TOSTR_BASE8_COUNT", "_MAX_I64TOSTR_BASE2_COUNT", "_MAX_U64TOSTR_BASE16_COUNT", "_MAX_U64TOSTR_BASE10_COUNT", "_MAX_U64TOSTR_BASE8_COUNT", "_MAX_U64TOSTR_BASE2_COUNT"]
`10`	`10`	`helpviewer_keywords: ["_itot function", "ui64toa function", "_ui64toa function", "converting integers", "itot function", "_i64tow function", "_i64toa function", "_itow function", "ui64tow function", "integers, converting", "itoa function", "_ui64tow function", "i64tow function", "itow function", "i64toa function", "converting numbers, to strings", "_itoa function"]`
`11`		`-ms.assetid: 46592a00-77bb-4e73-98c0-bf629d96cea6`
`12`	`11`	`---`
`13`	`12`	# `itoa`, `_itoa`, `ltoa`, `_ltoa`, `ultoa`, `_ultoa`, `_i64toa`, `_ui64toa`, `_itow`, `_ltow`, `_ultow`, `_i64tow`, `_ui64tow`
`14`	`13`
`@@ -137,7 +136,7 @@ This example uses a conversion count macro to define a buffer large enough to co`
`137`	`136`	`int main()`
`138`	`137`	`{`
`139`	`138`	`wchar_t buffer[_MAX_U64TOSTR_BASE2_COUNT];`
`140`		`- std:wcout << _ui64tow(0xFFFFFFFFFFFFFFFFull, buffer, 2) << std::endl;`
	`139`	`+ std::wcout << _ui64tow(0xFFFFFFFFFFFFFFFFull, buffer, 2) << std::endl;`
`141`	`140`	`}`
`142`	`141`	```
`143`	`142`