Merge pull request #8402 from MicrosoftDocs/main637971664746838250sync_temp

Repo sync for protected CLA branch

Author: Jak-MS

docs/debugger/using-the-debuggerdisplay-attribute.md

@@ -20,7 +20,7 @@ ms.workload:
 
  [!INCLUDE [Visual Studio](~/includes/applies-to-version/vs-windows-only.md)]
 
-The <xref:System.Diagnostics.DebuggerDisplayAttribute> controls how an object, property, or field is displayed in the debugger variable windows. This attribute can be applied to types, delegates, properties, fields, and assemblies. If applied to a base type, the attribute also applies to a subclass.
+The <xref:System.Diagnostics.DebuggerDisplayAttribute> controls how an object, property, or field is displayed in the debugger variable windows. This attribute can be applied to types (classes, structs, enums, delegates). If applied to a base type, the attribute also applies to a subclass.
 
 The `DebuggerDisplay` attribute has a single argument, which is a string to be displayed in the value column for instances of the type. This string can contain braces (`{` and `}`). Text within a pair of braces is evaluated as a field, property or method.
 

docs/test/troubleshooting-code-coverage.md

@@ -34,10 +34,6 @@ For more information, see [Use code coverage to determine how much code is being
 
 You need Visual Studio Enterprise.
 
-### Are you running code coverage for native(c++) module on ARM64 version of Visual Studio?
-
-Code coverage for native module is not supported on ARM64 version of Visual Studio.
-
 ### No tests were executed
 
 Analysis—Check your output window. In the **Show Output from** drop-down list, choose **Tests**. See if there are any warnings or errors logged.