Code escape pr13 (MicrosoftDocs#3533)

* initial

* adjustments

* Update cwnd-class.md

* adjustment

* Update cdc-class.md

* Update cdc-class.md

* Update cdc-class.md

* Update cdc-class.md

* Update ccombstr-class.md

* Update clistctrl-class.md

Fixing italic/coding formatting

Co-authored-by: Shannon Leavitt <V-SHLEAV>

Author: Matthew Sebolt

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

@@ -5,17 +5,17 @@ ms.date: "06/18/2018"
 helpviewer_keywords: ["CString objects, C++ string manipulation", "CString objects, reference counting", "CString class (Visual C++)"]
 ms.assetid: ed018aaf-8b10-46f9-828c-f9c092dc7609
 ---
-# Using CString
+# Using `CString`
 
-The topics in this section describe how to program with `CString`. For reference documentation about the `CString` class, see the documentation for [CStringT](../atl-mfc-shared/reference/cstringt-class.md).
+The topics in this section describe how to program with `CString`. For reference documentation about the `CString` class, see the documentation for [`CStringT`](../atl-mfc-shared/reference/cstringt-class.md).
 
 To use `CString`, include the `atlstr.h` header.
 
-The `CString`, `CStringA`, and `CStringW` classes are specializations of a class template called [CStringT](../atl-mfc-shared/reference/cstringt-class.md) based on the type of character data they support.
+The `CString`, `CStringA`, and `CStringW` classes are specializations of a class template called [`CStringT`](../atl-mfc-shared/reference/cstringt-class.md) based on the type of character data they support.
 
 A `CStringW` object contains the **`wchar_t`** type and supports Unicode strings. A `CStringA` object contains the **`char`** type, and supports single-byte and multi-byte (MBCS) strings. A `CString` object supports either the **`char`** type or the **`wchar_t`** type, depending on whether the MBCS symbol or the UNICODE symbol is defined at compile time.
 
-A `CString` object keeps character data in a `CStringData` object. `CString` accepts NULL-terminated C-style strings. `CString` tracks the string length for faster performance, but it also retains the NULL character in the stored character data to support conversion to LPCWSTR. `CString` includes the null terminator when it exports a C-style string. You can insert a NULL at other locations in a `CString`, but it may produce unexpected results.
+A `CString` object keeps character data in a `CStringData` object. `CString` accepts NULL-terminated C-style strings. `CString` tracks the string length for faster performance, but it also retains the `NULL` character in the stored character data to support conversion to `LPCWSTR`. `CString` includes the null terminator when it exports a C-style string. You can insert a `NULL` at other locations in a `CString`, but it may produce unexpected results.
 
 The following set of string classes can be used without linking an MFC library, with or without CRT support: `CAtlString`, `CAtlStringA`, and `CAtlStringW`.
 
@@ -36,7 +36,7 @@ int main() {
 
 ## In This Section
 
-[Basic CString Operations](../atl-mfc-shared/basic-cstring-operations.md)<br/>
+[Basic `CString` Operations](../atl-mfc-shared/basic-cstring-operations.md)<br/>
 Describes basic `CString` operations, including creating objects from C literal strings, accessing individual characters in a `CString`, concatenating two objects, and comparing `CString` objects.
 
 [String Data Management](../atl-mfc-shared/string-data-management.md)<br/>
@@ -48,24 +48,24 @@ Explains how `CString` objects are used.
 [CString Operations Relating to C-Style Strings](../atl-mfc-shared/cstring-operations-relating-to-c-style-strings.md)<br/>
 Describes manipulating the contents of a `CString` object like a C-style null-terminated string.
 
-[Allocating and Releasing Memory for a BSTR](../atl-mfc-shared/allocating-and-releasing-memory-for-a-bstr.md)<br/>
-Discusses using memory for a BSTR and COM objects.
+[Allocating and Releasing Memory for a `BSTR`](../atl-mfc-shared/allocating-and-releasing-memory-for-a-bstr.md)<br/>
+Discusses using memory for a `BSTR` and COM objects.
 
 [CString Exception Cleanup](../atl-mfc-shared/cstring-exception-cleanup.md)<br/>
 Explains that explicit cleanup in MFC 3.0 and later is no longer necessary.
 
 [CString Argument Passing](../atl-mfc-shared/cstring-argument-passing.md)<br/>
-Explains how to pass CString objects to functions and how to return `CString` objects from functions.
+Explains how to pass `CString` objects to functions and how to return `CString` objects from functions.
 
 [Unicode and Multibyte Character Set (MBCS) Support](../atl-mfc-shared/unicode-and-multibyte-character-set-mbcs-support.md)<br/>
 Discusses how MFC is enabled for Unicode and MBCS support.
 
 ## Reference
 
-[CStringT](../atl-mfc-shared/reference/cstringt-class.md)<br/>
+[`CStringT`](../atl-mfc-shared/reference/cstringt-class.md)<br/>
 Provides reference information about the `CStringT` class.
 
-[CSimpleStringT Class](../atl-mfc-shared/reference/csimplestringt-class.md)<br/>
+[`CSimpleStringT` Class](../atl-mfc-shared/reference/csimplestringt-class.md)<br/>
 Provides reference information about the `CSimpleStringT` class.
 
 ## Related Sections

docs/atl-mfc-shared/using-cstring.md

@@ -6,15 +6,15 @@ ms.topic: "reference"
 helpviewer_keywords: ["interfaces, pointers", "interfaces, availability", "QueryInterface method"]
 ms.assetid: 62fce95e-aafa-4187-b50b-e6611b74c3b3
 ---
-# QueryInterface
+# `QueryInterface`
 
-Although there are mechanisms by which an object can express the functionality it provides statically (before it is instantiated), the fundamental COM mechanism is to use the `IUnknown` method called [QueryInterface](/windows/win32/api/unknwn/nf-unknwn-iunknown-queryinterface(q)).
+Although there are mechanisms by which an object can express the functionality it provides statically (before it is instantiated), the fundamental COM mechanism is to use the `IUnknown` method called [`QueryInterface`](/windows/win32/api/unknwn/nf-unknwn-iunknown-queryinterface(q)).
 
-Every interface is derived from `IUnknown`, so every interface has an implementation of `QueryInterface`. Regardless of implementation, this method queries an object using the IID of the interface to which the caller wants a pointer. If the object supports that interface, `QueryInterface` retrieves a pointer to the interface, while also calling `AddRef`. Otherwise, it returns the E_NOINTERFACE error code.
+Every interface is derived from `IUnknown`, so every interface has an implementation of `QueryInterface`. Regardless of implementation, this method queries an object using the `IID` of the interface to which the caller wants a pointer. If the object supports that interface, `QueryInterface` retrieves a pointer to the interface, while also calling `AddRef`. Otherwise, it returns the `E_NOINTERFACE` error code.
 
-Note that you must obey [Reference Counting](../atl/reference-counting.md) rules at all times. If you call `Release` on an interface pointer to decrement the reference count to zero, you should not use that pointer again. Occasionally you may need to obtain a weak reference to an object (that is, you may wish to obtain a pointer to one of its interfaces without incrementing the reference count), but it is not acceptable to do this by calling `QueryInterface` followed by `Release`. The pointer obtained in such a manner is invalid and should not be used. This more readily becomes apparent when [_ATL_DEBUG_INTERFACES](reference/debugging-and-error-reporting-macros.md#_atl_debug_interfaces) is defined, so defining this macro is a useful way of finding reference counting bugs.
+Note that you must obey [Reference Counting](../atl/reference-counting.md) rules at all times. If you call `Release` on an interface pointer to decrement the reference count to zero, you should not use that pointer again. Occasionally you may need to obtain a weak reference to an object (that is, you may wish to obtain a pointer to one of its interfaces without incrementing the reference count), but it is not acceptable to do this by calling `QueryInterface` followed by `Release`. The pointer obtained in such a manner is invalid and should not be used. This more readily becomes apparent when [`_ATL_DEBUG_INTERFACES`](reference/debugging-and-error-reporting-macros.md#_atl_debug_interfaces) is defined, so defining this macro is a useful way of finding reference counting bugs.
 
 ## See also
 
 [Introduction to COM](../atl/introduction-to-com.md)<br/>
-[QueryInterface: Navigating in an Object](/windows/win32/com/queryinterface--navigating-in-an-object)
+[`QueryInterface`: Navigating in an Object](/windows/win32/com/queryinterface--navigating-in-an-object)