Merge pull request MicrosoftDocs#1994 from nschonni/fix--MD046/code-block-style

fix: MD046/code-block-style

Author: Colin Robertson

CONTRIBUTING.md

@@ -36,11 +36,13 @@ Be sure to follow the proper Markdown syntax. See the [style guide](./styleguide
 
 ### Example structure
 
-    docs
-        /standard-library
-            wstring-convert-class.md
-            /media
-                wstring-conversion.png
+```
+docs
+    /standard-library
+        wstring-convert-class.md
+        /media
+            wstring-conversion.png
+```
 
 **Step 5:** Submit a Pull Request (PR) from your branch to `MicrosoftDocs/cpp-docs/master`.
 

docs/mfc/containers-advanced-features.md

@@ -52,7 +52,7 @@ The Links to Embedded Objects feature enables a user to create a document with a
 
    - Call `COleTemplateServer::UpdateRegistry`. The only parameter to `UpdateRegistry` should be *OAT_CONTAINER* if the application is not launched with the "/Embedded" switch. This registers the application as a container that can support links to embedded objects.
 
-         If the application is launched with the "/Embedded" switch, it should not show its main window, similar to a server application.
+      If the application is launched with the "/Embedded" switch, it should not show its main window, similar to a server application.
 
 The MFC OLE sample [OCLIENT](../overview/visual-cpp-samples.md) implements this feature. For an example of how this is done, see the `InitInstance` function in the *OCLIENT.CPP* file of this sample application.
 

docs/mfc/data-objects-and-data-sources-manipulation.md

@@ -48,7 +48,7 @@ Before an application allows the user to paste data into it, it needs to know if
 
    - Call the data object's `IsDataAvailable` member function if there are only one or two formats you need. This will save you time in cases where the data on the Clipboard supports significantly more formats than your application.
 
-         -or-
+     \-or-
 
    - Call the data object's `BeginEnumFormats` member function to start enumerating the formats available on the Clipboard. Then call `GetNextFormat` until the Clipboard returns a format your application supports or there are no more formats.
 

docs/mfc/recommendations-for-handling-input-output.md

@@ -24,13 +24,13 @@ Whether you use file-based I/O or not depends on how you respond to the question
 
    - Yes, the data resides in an ODBC data source:
 
-         Use MFC's database support. The standard MFC implementation for this case includes a `CDatabase` object, as discussed in the article [MFC: Using Database Classes with Documents and Views](../data/mfc-using-database-classes-with-documents-and-views.md). The application might also read and write an auxiliary file — the purpose of the application wizard "both a database view and file support" option. In this case, you'd use serialization for the auxiliary file.
+      Use MFC's database support. The standard MFC implementation for this case includes a `CDatabase` object, as discussed in the article [MFC: Using Database Classes with Documents and Views](../data/mfc-using-database-classes-with-documents-and-views.md). The application might also read and write an auxiliary file — the purpose of the application wizard "both a database view and file support" option. In this case, you'd use serialization for the auxiliary file.
 
    - No, the data doesn't reside in an ODBC data source.
 
-         Examples of this case: the data resides in a non-ODBC DBMS; the data is read via some other mechanism, such as OLE or DDE.
+      Examples of this case: the data resides in a non-ODBC DBMS; the data is read via some other mechanism, such as OLE or DDE.
 
-         In such cases, you won't use serialization, and your application won't have Open and Save menu items. You might still want to use a `CDocument` as a home base, just as an MFC ODBC application uses the document to store `CRecordset` objects. But you won't use the framework's default File Open/Save document serialization.
+      In such cases, you won't use serialization, and your application won't have Open and Save menu items. You might still want to use a `CDocument` as a home base, just as an MFC ODBC application uses the document to store `CRecordset` objects. But you won't use the framework's default File Open/Save document serialization.
 
 To support the Open, Save, and Save As commands on the File menu, the framework provides document serialization. Serialization reads and writes data, including objects derived from class `CObject`, to permanent storage, normally a disk file. Serialization is easy to use and serves many of your needs, but it may be inappropriate in many data-access applications. Data-access applications typically update data on a per-transaction basis. They update the records affected by the transaction rather than reading and writing a whole data file at once.
 

docs/mfc/reference/csplitterwnd-class.md

@@ -448,17 +448,17 @@ A pointer to the view from which the scrolling message originates.
 *nScrollCode*<br/>
 A scroll-bar code that indicates the user's scrolling request. This parameter is composed of two parts: a low-order byte, which determines the type of scrolling occurring horizontally, and a high-order byte, which determines the type of scrolling occurring vertically:
 
-    - SB_BOTTOM Scrolls to bottom.
+- SB_BOTTOM Scrolls to bottom.
 
-    - SB_LINEDOWN Scrolls one line down.
+- SB_LINEDOWN Scrolls one line down.
 
-    - SB_LINEUP Scrolls one line up.
+- SB_LINEUP Scrolls one line up.
 
-    - SB_PAGEDOWN Scrolls one page down.
+- SB_PAGEDOWN Scrolls one page down.
 
-    - SB_PAGEUP Scrolls one page up.
+- SB_PAGEUP Scrolls one page up.
 
-    - SB_TOP Scrolls to top.
+- SB_TOP Scrolls to top.
 
 *bDoScroll*<br/>
 Determines whether the specified scrolling action occurs. If *bDoScroll* is TRUE (that is, if a child window exists, and if the split windows have a scroll range), then the specified scrolling action can take place; if *bDoScroll* is FALSE (that is, if no child window exists, or the split views have no scroll range), then scrolling does not occur.
@@ -635,9 +635,9 @@ DWORD GetScrollStyle() const;
 
 One or more of the following windows style flags, if successful:
 
-    - WS_HSCROLL If the splitter currently manages shared horizontal scroll bars.
+- WS_HSCROLL If the splitter currently manages shared horizontal scroll bars.
 
-    - WS_VSCROLL If the splitter currently manages shared vertical scroll bars.
+- WS_VSCROLL If the splitter currently manages shared vertical scroll bars.
 
 If zero, the splitter window does not currently manage any shared scroll bars.
 
@@ -736,13 +736,13 @@ A pointer to the device context in which to draw. If *pDC* is NULL, then [CWnd::
 *nType*<br/>
 A value of the `enum ESplitType`, which can be one of the following:
 
-    - `splitBox` The splitter drag box.
+- `splitBox` The splitter drag box.
 
-    - `splitBar` The bar that appears between the two split windows.
+- `splitBar` The bar that appears between the two split windows.
 
-    - `splitIntersection` The intersection of the split windows. This element will not be called when running on Windows 95/98.
+- `splitIntersection` The intersection of the split windows. This element will not be called when running on Windows 95/98.
 
-    - `splitBorder` The split window borders.
+- `splitBorder` The split window borders.
 
 *rect*<br/>
 A reference to a [CRect](../../atl-mfc-shared/reference/crect-class.md) object specifying the size and shape of the split windows.

docs/mfc/reference/mfc-odbc-consumer-wizard.md

@@ -47,7 +47,7 @@ This wizard sets up an ODBC recordset class and the data bindings necessary to a
 
 - **Class**
 
-      The name of the consumer class, based by default on the name of the file or machine data source that you selected.
+   The name of the consumer class, based by default on the name of the file or machine data source that you selected.
 
 - **.h file**
 

docs/mfc/reference/run-time-object-model-services.md

@@ -333,11 +333,11 @@ The object name exposed to other applications (enclosed in quotation marks).
 *nFlags*<br/>
 Contains one or more of the following flags:
 
-   - `afxRegInsertable` Allows the control to appear in the Insert Object dialog box for OLE objects.
-   - `afxRegApartmentThreading` Sets the threading model in the registry to ThreadingModel=Apartment.
-   - `afxRegFreeThreading` Sets the threading model in the registry to ThreadingModel=Free.
+- `afxRegInsertable` Allows the control to appear in the Insert Object dialog box for OLE objects.
+- `afxRegApartmentThreading` Sets the threading model in the registry to ThreadingModel=Apartment.
+- `afxRegFreeThreading` Sets the threading model in the registry to ThreadingModel=Free.
 
-         You can combine the two flags `afxRegApartmentThreading` and `afxRegFreeThreading` to set ThreadingModel=Both. See [InprocServer32](/windows/win32/com/inprocserver32) in the Windows SDK for more information on threading model registration.
+You can combine the two flags `afxRegApartmentThreading` and `afxRegFreeThreading` to set ThreadingModel=Both. See [InprocServer32](/windows/win32/com/inprocserver32) in the Windows SDK for more information on threading model registration.
 
 *l*, *w1*, *w2*, *b1*, *b2*, *b3*, *b4*, *b5*, *b6*, *b7*, *b8*
 Components of the class's CLSID.

docs/mfc/windows-sockets-using-class-casyncsocket.md

@@ -40,13 +40,13 @@ This article covers:
 
    - A "port": a short integer.
 
-         For a server socket, you must specify a port. For a client socket, you typically accept the default value for this parameter, which lets Windows Sockets select a port.
+      For a server socket, you must specify a port. For a client socket, you typically accept the default value for this parameter, which lets Windows Sockets select a port.
 
    - A socket type: **SOCK_STREAM** (the default) or **SOCK_DGRAM**.
 
    - A socket "address," such as "ftp.microsoft.com" or "128.56.22.8".
 
-         This is your Internet Protocol (IP) address on the network. You will probably always rely on the default value for this parameter.
+      This is your Internet Protocol (IP) address on the network. You will probably always rely on the default value for this parameter.
 
    The terms "port" and "socket address" are explained in [Windows Sockets: Ports and Socket Addresses](../mfc/windows-sockets-ports-and-socket-addresses.md).