MicrosoftDocs · Rageking8 · Jul 20, 2025 · Jul 20, 2025
diff --git a/docs/build/reference/files-created-for-clr-projects.md b/docs/build/reference/files-created-for-clr-projects.md
@@ -1,17 +1,16 @@
 ---
-description: "Learn more about: Files Created for CLR Projects"
 title: "Files Created for CLR Projects"
-ms.date: "11/04/2016"
+description: "Learn more about: Files Created for CLR Projects"
+ms.date: 11/04/2016
 helpviewer_keywords: ["Visual Studio C++ projects, CLR programming", ".NET applications, C++"]
-ms.assetid: 59ae9020-5f26-4ad0-bbdd-97c2e2023a20
 ---
 # Files Created for CLR Projects
 
 When you use Visual C++ templates to create your projects, several files are created, depending on which template you use. The following table lists all the files that are created by project templates for .NET Framework projects.
 
 |File name|File description|
 |---------------|----------------------|
-|AssemblyInfo.cpp|The file that contains information (that is, attributes, files, resources, types, versioning information, signing information, and so on) for modifying the project's assembly metadata. For more information see [Assembly Concepts](/dotnet/framework/app-domains/assembly-contents).|
+|AssemblyInfo.cpp|The file that contains information (that is, attributes, files, resources, types, versioning information, signing information, and so on) for modifying the project's assembly metadata. For more information, see [Assembly Concepts](/dotnet/framework/app-domains/assembly-contents).|
 |*projname*.asmx|A text file that references managed classes that encapsulate the functionality of the XML Web service.|
 |*projname*.cpp|The main source file and entry point into the application that Visual Studio created for you. Identifies the project .dll file and the project namespace. Provide your own code in this file.|
 |*projname*.vsdisco|An XML deployment file containing links to other resources that describe the XML Web service.|

diff --git a/docs/build/reference/return-value-of-cl-exe.md b/docs/build/reference/return-value-of-cl-exe.md
@@ -1,9 +1,8 @@
 ---
-description: "Learn more about: Return Value of cl.exe"
 title: "Return Value of cl.exe"
-ms.date: "09/05/2018"
+description: "Learn more about: Return Value of cl.exe"
+ms.date: 09/05/2018
 helpviewer_keywords: ["cl.exe compiler, return value"]
-ms.assetid: 7c2d7f33-ee0d-4199-8ef4-75fe2b007670
 ---
 # Return Value of cl.exe
 
@@ -13,7 +12,7 @@ The return value of cl.exe can be useful if you are compiling from a script, pow
 
 There are too many possible error exit codes for cl.exe to list them all. You can look up an error code in the winerror.h or ntstatus.h files included in the Windows Software Development Kit in the %ProgramFiles(x86)%\Windows Kits\\<em>version</em>\Include\shared\ directory. Error codes returned in decimal must be converted to hexadecimal for search. For example, an error code of -1073741620 converted to hexadecimal is 0xC00000CC. This error is found in ntstatus.h, where the corresponding message is "The specified share name cannot be found on the remote server." For a downloadable list of Windows error codes, see [`[MS-ERREF]` Windows Error Codes](/openspecs/windows_protocols/MS-ERREF).
 
-You can also use the error lookup utility in Visual Studio to find out what a compiler error message means. In a Visual Studio command shell, enter **errlook.exe** to start the utility; or in the Visual Studio IDE, on the menu bar, choose **Tools**, **Error Lookup**. Enter the error value to find the descriptive text associated with the error. For more information see [ERRLOOK Reference](errlook-reference.md).
+You can also use the error lookup utility in Visual Studio to find out what a compiler error message means. In a Visual Studio command shell, enter **errlook.exe** to start the utility; or in the Visual Studio IDE, on the menu bar, choose **Tools**, **Error Lookup**. Enter the error value to find the descriptive text associated with the error. For more information, see [ERRLOOK Reference](errlook-reference.md).
 
 ## Remarks
 

diff --git a/docs/error-messages/compiler-errors-1/compiler-error-c2349.md b/docs/error-messages/compiler-errors-1/compiler-error-c2349.md
@@ -1,13 +1,12 @@
 ---
-description: "Learn more about: Compiler Error C2349"
 title: "Compiler Error C2349"
-ms.date: "11/04/2016"
+description: "Learn more about: Compiler Error C2349"
+ms.date: 11/04/2016
 f1_keywords: ["C2349"]
 helpviewer_keywords: ["C2349"]
-ms.assetid: ce9f2e65-fda0-41b6-9c4a-538607136396
 ---
 # Compiler Error C2349
 
 'function' cannot be compiled as managed: 'reason'; use #pragma unmanaged
 
-For more information see [Compiler Warning (level 1 and 3) C4793](../../error-messages/compiler-warnings/compiler-warning-level-1-and-3-c4793.md).
+For more information, see [Compiler Warning (level 1 and 3) C4793](../../error-messages/compiler-warnings/compiler-warning-level-1-and-3-c4793.md).
diff --git a/docs/extensions/string-cpp-component-extensions.md b/docs/extensions/string-cpp-component-extensions.md
@@ -49,7 +49,7 @@ When passed a <xref:System.String>, the compiler will box, if necessary, and the
 > [!NOTE]
 > The caret ("^") indicates that the declared variable is a handle to a C++/CLI managed object.
 
-For more information see [String and Character Literals](../cpp/string-and-character-literals-cpp.md).
+For more information, see [String and Character Literals](../cpp/string-and-character-literals-cpp.md).
 
 ### Requirements
 

diff --git a/docs/mfc/mfc-com.md b/docs/mfc/mfc-com.md
@@ -1,16 +1,15 @@
 ---
-description: "Learn more about: MFC COM"
 title: "MFC COM"
-ms.date: "09/12/2018"
+description: "Learn more about: MFC COM"
+ms.date: 09/12/2018
 f1_keywords: ["MFC COM (MFC)"]
 helpviewer_keywords: ["MFC, COM support", "MFC ActiveX controls [MFC], COM support in MFC", "MFC COM [MFC]", "ActiveX controls [MFC], COM object model", "Active technology [MFC]", "COM [MFC], MFC support"]
-ms.assetid: 7646bdcb-3a06-4ed5-9386-9b00f3979dcb
 ---
 # MFC COM
 
 A subset of MFC is designed to support COM, while most of the Active Template Library (ATL) is designed for COM programming. This section of topics describes MFC's support for COM.
 
-Active technologies (such as ActiveX controls, Active document containment, OLE, and so on) use the Component Object Model (COM) to enable software components to interact with one another in a networked environment, regardless of the language with which they were created. Active technologies can be used to create applications that run on the desktop or the Internet. For more information see [Introduction to COM](../atl/introduction-to-com.md) or [The Component Object Model](/windows/win32/com/the-component-object-model).
+Active technologies (such as ActiveX controls, Active document containment, OLE, and so on) use the Component Object Model (COM) to enable software components to interact with one another in a networked environment, regardless of the language with which they were created. Active technologies can be used to create applications that run on the desktop or the Internet. For more information, see [Introduction to COM](../atl/introduction-to-com.md) or [The Component Object Model](/windows/win32/com/the-component-object-model).
 
 Active technologies include both client and server technologies, including the following:
 

diff --git a/docs/mfc/reference/ctabview-class.md b/docs/mfc/reference/ctabview-class.md
@@ -1,10 +1,9 @@
 ---
-description: "Learn more about: CTabView Class"
 title: "CTabView Class"
-ms.date: "11/04/2016"
+description: "Learn more about: CTabView Class"
+ms.date: 11/04/2016
 f1_keywords: ["CTabView", "AFXTABVIEW/CTabView", "AFXTABVIEW/CTabView::AddView", "AFXTABVIEW/CTabView::FindTab", "AFXTABVIEW/CTabView::GetActiveView", "AFXTABVIEW/CTabView::GetTabControl", "AFXTABVIEW/CTabView::RemoveView", "AFXTABVIEW/CTabView::SetActiveView", "AFXTABVIEW/CTabView::IsScrollBar", "AFXTABVIEW/CTabView::OnActivateView"]
 helpviewer_keywords: ["CTabView [MFC], AddView", "CTabView [MFC], FindTab", "CTabView [MFC], GetActiveView", "CTabView [MFC], GetTabControl", "CTabView [MFC], RemoveView", "CTabView [MFC], SetActiveView", "CTabView [MFC], IsScrollBar", "CTabView [MFC], OnActivateView"]
-ms.assetid: 8e6ecd9d-d28d-432b-8ec8-0446f0204d52
 ---
 # CTabView Class
 
@@ -208,7 +207,7 @@ TRUE if the specified view was made active, FALSE if the view's index is invalid
 
 ### Remarks
 
-For more information see [CMFCTabCtrl::SetActiveTab](../../mfc/reference/cmfctabctrl-class.md#setactivetab).
+For more information, see [CMFCTabCtrl::SetActiveTab](../../mfc/reference/cmfctabctrl-class.md#setactivetab).
 
 ## See also
 

diff --git a/docs/parallel/amp/graphics-cpp-amp.md b/docs/parallel/amp/graphics-cpp-amp.md
@@ -377,7 +377,7 @@ void write2ComponentTexture() {
 
 Texture views whose elements are based on floating-point types—for example, float, float_2, or float_4—can also be read by using texture sampling to take advantage of hardware support for various filtering modes and addressing modes. C++ AMP supports the two filtering modes that are most common in compute scenarios—point-filtering (nearest-neighbor) and linear-filtering (weighted average)—and four addressing modes—wrapped, mirrored, clamped, and border. For more information about addressing modes, see [address_mode Enumeration](reference/concurrency-graphics-namespace-enums.md#address_mode).
 
-In addition to modes that C++ AMP supports directly, you can access other filtering modes and addressing modes of the underlying platform by using the interop APIs to adopt a texture sampler that was created by using the platform APIs directly. For example, Direct3D supports other filtering modes such as anisotropic filtering, and can apply a different addressing mode to each dimension of a texture. You could create a texture sampler whose coordinates are wrapped vertically, mirrored horizontally, and sampled with anisotropic filtering by using the Direct3D APIs, and then leverage the sampler in your C++ AMP code by using the `make_sampler` interop API. For more information see [Texture Sampling in C++ AMP](/archive/blogs/nativeconcurrency/texture-sampling-in-c-amp) on the Parallel Programming in Native Code blog.
+In addition to modes that C++ AMP supports directly, you can access other filtering modes and addressing modes of the underlying platform by using the interop APIs to adopt a texture sampler that was created by using the platform APIs directly. For example, Direct3D supports other filtering modes such as anisotropic filtering, and can apply a different addressing mode to each dimension of a texture. You could create a texture sampler whose coordinates are wrapped vertically, mirrored horizontally, and sampled with anisotropic filtering by using the Direct3D APIs, and then leverage the sampler in your C++ AMP code by using the `make_sampler` interop API. For more information, see [Texture Sampling in C++ AMP](/archive/blogs/nativeconcurrency/texture-sampling-in-c-amp) on the Parallel Programming in Native Code blog.
 
 Texture views also support the reading of mipmaps. Read-only texture views (those that have a const element type) offer the most flexibility because a range of mip-levels that is determined at instantiation can be dynamically sampled, and because elements that have 1, 2, or 4 components are supported. Read-write texture views that have elements that have one component also support mipmaps, but only of a level that's determined at instantiation. For more information, see [Texture with Mipmaps](/archive/blogs/nativeconcurrency/texture-with-mipmaps) on the Parallel Programming in Native Code blog.