MicrosoftDocs · colin-home · Nov 7, 2022 · Nov 4, 2022 · Nov 4, 2022 · Nov 4, 2022
diff --git a/docs/atl/reference/iperpropertybrowsingimpl-class.md b/docs/atl/reference/iperpropertybrowsingimpl-class.md
@@ -16,7 +16,6 @@ This class implements `IUnknown` and allows a client to access the information i
 ## Syntax
 
 ```
-
 template <class T>
 class ATL_NO_VTABLE IPerPropertyBrowsingImpl :
     public IPerPropertyBrowsing

diff --git a/docs/build/open-folder-projects-cpp.md b/docs/build/open-folder-projects-cpp.md
@@ -147,7 +147,6 @@ This creates (or opens) the *tasks.vs.json* file in the .vs folder which Visual
     }
   ]
 }
-
 ```
 
 The JSON file is placed in the *.vs* subfolder. To see that folder, click on the **Show All Files** button at the top of **Solution Explorer**. You can run this task by right-clicking on the root node in **Solution Explorer** and choosing **build hello**. When the task completes you should see a new file, *hello.exe* in **Solution Explorer**.
@@ -194,7 +193,6 @@ To customize your program's command line arguments and debugging instructions, r
     }
   ]
 }
-
 ```
 
 To start debugging, choose the executable in the debug dropdown, then click the green arrow:

diff --git a/docs/build/reference/allowbind.md b/docs/build/reference/allowbind.md
@@ -11,7 +11,6 @@ ms.assetid: eaadbb8c-4339-4281-9a75-3a1ce2352ff8
 Specifies whether a DLL can be bound.
 
 ```
-
 /ALLOWBIND[:NO]
 ```
 

diff --git a/docs/build/reference/allowisolation.md b/docs/build/reference/allowisolation.md
@@ -13,7 +13,6 @@ Specifies behavior for manifest lookup.
 ## Syntax
 
 ```
-
 /ALLOWISOLATION[:NO]
 ```
 

diff --git a/docs/build/reference/appcontainer.md b/docs/build/reference/appcontainer.md
@@ -11,7 +11,6 @@ ms.assetid: 0ca4f1ec-c8de-4a37-b3e2-deda7af0bb88
 Marks an executable that must run in an app container—for example, a Microsoft Store or Universal Windows app.
 
 ```
-
 /APPCONTAINER[:NO]
 ```
 

diff --git a/docs/c-language/generic-selection.md b/docs/c-language/generic-selection.md
@@ -67,7 +67,6 @@ int main()
 /* Output:
 Type name: double
 */
-
 ```
 
 ## Requirements

diff --git a/docs/code-quality/c26117.md b/docs/code-quality/c26117.md
@@ -17,7 +17,6 @@ Enforcement of syntactically scoped lock *acquire* and lock *release* pairs in C
 The following example generates warning C26117 because the function `ReleaseUnheldLock` releases a lock that it doesn't necessarily hold—the state of `flag` is ambiguous—and there's no annotation that specifies that it should.
 
 ```cpp
-
 typedef struct _DATA
 {
     CRITICAL_SECTION cs;
@@ -37,7 +36,6 @@ void ReleaseUnheldLock(DATA* p)
 The following code fixes the problem by guaranteeing that the released lock is also acquired under the same conditions.
 
 ```cpp
-
 typedef struct _DATA
 {
     CRITICAL_SECTION cs;

diff --git a/docs/code-quality/c26138.md b/docs/code-quality/c26138.md
@@ -20,7 +20,6 @@ Code analysis name: `SUSPENDED_WITH_LOCK`
 The following code will generate C26138.
 
 ```cpp
-
 #include <experimental/generator>
 #include <future>
 #include <mutex>
@@ -49,7 +48,6 @@ generator<int> mutex_acquiring_generator_report_once() {
 The following code will correct these warnings.
 
 ```cpp
-
 #include <experimental/generator>
 #include <future>
 #include <mutex>

diff --git a/docs/code-quality/c26160.md b/docs/code-quality/c26160.md
@@ -17,7 +17,6 @@ Warning C26160 resembles warning [C26110](../code-quality/c26110.md) except that
 The following code generates warning C26160.
 
 ```cpp
-
 struct Account
 {
     _Guarded_by_(cs) int balance;
@@ -49,7 +48,6 @@ struct Account
 The following code shows a solution to the previous example.
 
 ```cpp
-
 struct Account
 {
     _Guarded_by_(cs) int balance;

diff --git a/docs/code-quality/c26165.md b/docs/code-quality/c26165.md
@@ -17,7 +17,6 @@ Warning C26165 resembles warning [C26115](../code-quality/c26115.md) except that
 The following code generates warning C26165.
 
 ```cpp
-
 _Create_lock_level_(LockLevelOne);
 _Create_lock_level_(LockLevelTwo);
 
@@ -45,7 +44,6 @@ void testLockLevelledStruct(LockLevelledStruct* s) // Warning C26165
 To correct this warning, change the previous example to the following.
 
 ```cpp
-
 _Create_lock_level_(LockLevelOne);
 _Create_lock_level_(LockLevelTwo);
 

diff --git a/docs/code-quality/c26166.md b/docs/code-quality/c26166.md
@@ -17,7 +17,6 @@ Warning C26166 resembles warning [C26116](../code-quality/c26116.md) except that
 The following code shows code that will generate warning C26166.
 
 ```cpp
-
 typedef struct _DATA {
 CRITICAL_SECTION cs;
 } DATA;

diff --git a/docs/code-quality/c26167.md b/docs/code-quality/c26167.md
@@ -17,7 +17,6 @@ Warning C26167 resembles warning [C26117](../code-quality/c26117.md) except that
 The following code will generate C26167 and C26110.
 
 ```cpp
-
 typedef struct _DATA {
     CRITICAL_SECTION cs;
 } DATA;
@@ -34,7 +33,6 @@ void ReleaseUnheldLock(DATA* p) { // Warning C26167
 The following code will correct these warnings.
 
 ```cpp
-
 typedef struct _DATA {
     CRITICAL_SECTION cs;
 } DATA;

diff --git a/docs/code-quality/c26800.md b/docs/code-quality/c26800.md
@@ -20,7 +20,6 @@ Code analysis name: `USE_OF_A_MOVED_FROM_OBJECT`
 The following code will generate C26800.
 
 ```cpp
-
 #include <utility>
 
 struct X {
@@ -45,7 +44,6 @@ void test() {
 The following code won't generate C26800.
 
 ```cpp
-
 #include <utility>
 
 struct MoveOnly {

diff --git a/docs/code-quality/c26810.md b/docs/code-quality/c26810.md
@@ -20,7 +20,6 @@ Code analysis name: `COROUTINES_USE_AFTER_FREE_CAPTURE`
 The following code will generate C26810.
 
 ```cpp
-
 #include <experimental/generator>
 #include <future>
 

diff --git a/docs/code-quality/c26811.md b/docs/code-quality/c26811.md
@@ -20,7 +20,6 @@ Code analysis name: `COROUTINES_USE_AFTER_FREE_PARAM`
 The following code will generate C26811.
 
 ```cpp
-
 #include <experimental/generator>
 #include <future>
 

diff --git a/docs/code-quality/c26828.md b/docs/code-quality/c26828.md
@@ -20,7 +20,6 @@ Code analysis name: `MIXING_OVERLAPPING_ENUMS`
 The following sample code causes warning C26828:
 
 ```cpp
-
 enum BitWiseA
 {
     A = 1,
@@ -45,7 +44,6 @@ int overlappingBitwiseEnums(BitWiseA a)
 To fix the warning, make sure enumeration types designed for use together have no overlapping values. Or, make sure all the related options are in a single enumeration type.
 
 ```cpp
-
 enum BitWiseA
 {
     A = 1,

diff --git a/docs/code-quality/c6029.md b/docs/code-quality/c6029.md
@@ -23,7 +23,6 @@ Code analysis name: `USING_TAINTED_DATA`
 The following code generates this warning by calling the annotated function [`ReadFile`](/windows/desktop/api/fileapi/nf-fileapi-readfile) two times. After the first call, the Post attribute property marks the second parameter value untrusted. Therefore, passing an untrusted value in the second call to `ReadFile` generates this warning as shown in the following code:
 
 ```cpp
-
 #include "windows.h"
 
 bool f(HANDLE hFile)

diff --git a/docs/code-quality/c6053.md b/docs/code-quality/c6053.md
@@ -23,7 +23,6 @@ Code analysis name: `MISSING_ZERO_TERMINATION1`
 The following sample code generates this warning:
 
 ```cpp
-
 #include <string.h>
 #define MAX 15
 
@@ -40,7 +39,6 @@ size_t f( )
 To correct this warning, zero-terminate the string as shown in the following sample code:
 
 ```cpp
-
 #include <string.h>
 #define MAX 15
 
@@ -58,7 +56,6 @@ size_t f( )
 The following sample code corrects this warning using safe string manipulation `strncpy_s` function:
 
 ```cpp
-
 #include <string.h>
 #define MAX 15
 

diff --git a/docs/code-quality/c6387.md b/docs/code-quality/c6387.md
@@ -21,7 +21,6 @@ Code analysis name: `INVALID_PARAM_VALUE_1`
 The following code generates this warning because a null parameter is passed to `f(char *)`:
 
 ```cpp
-
 #include <sal.h>
 
 _Post_ _Null_ char * g();
@@ -38,7 +37,6 @@ void main()
 To correct this warning, use the following code:
 
 ```cpp
-
 #include <sal.h>
 
 _Post_ _Notnull_ char * g();

diff --git a/docs/code-quality/understanding-sal.md b/docs/code-quality/understanding-sal.md
@@ -20,7 +20,6 @@ Simply stated, SAL is an inexpensive way to let the compiler check your code for
 SAL can help you make your code design more understandable, both for humans and for code analysis tools. Consider this example that shows the C runtime function `memcpy`:
 
 ```cpp
-
 void * memcpy(
    void *dest,
    const void *src,
@@ -42,7 +41,6 @@ The documentation contains a couple of bits of information that suggest that you
 However, the compiler can't read the documentation or informal comments. It doesn't know that there is a relationship between the two buffers and `count`, and it also can't effectively guess about a relationship. SAL could provide more clarity about the properties and implementation of the function, as shown here:
 
 ```cpp
-
 void * memcpy(
    _Out_writes_bytes_all_(count) void *dest,
    _In_reads_bytes_(count) const void *src,
@@ -53,7 +51,6 @@ void * memcpy(
 Notice that these annotations resemble the information in the documentation, but they are more concise and they follow a semantic pattern. When you read this code, you can quickly understand the properties of this function and how to avoid buffer overrun security issues. Even better, the semantic patterns that SAL provides can improve the efficiency and effectiveness of automated code analysis tools in the early discovery of potential bugs. Imagine that someone writes this buggy implementation of `wmemcpy`:
 
 ```cpp
-
 wchar_t * wmemcpy(
    _Out_writes_all_(count) wchar_t *dest,
    _In_reads_(count) const wchar_t *src,
@@ -155,7 +152,6 @@ If you use Visual Studio Code Analysis on this example, it validates that the ca
 `_In_opt_` is the same as `_In_`, except that the input parameter is allowed to be NULL and, therefore, the function should check for this.
 
 ```cpp
-
 void GoodInOptCallee(_In_opt_ int *pInt)
 {
    if(pInt != NULL) {

diff --git a/docs/code-quality/using-rule-sets-to-specify-the-cpp-rules-to-run.md b/docs/code-quality/using-rule-sets-to-specify-the-cpp-rules-to-run.md
@@ -229,7 +229,6 @@ The following ruleset schema describes the XML schema of a ruleset file. The rul
   </xs:simpleType>
 
 </xs:schema>
-
 ```
 
 Schema element details:

diff --git a/docs/cpp/arrays-cpp.md b/docs/cpp/arrays-cpp.md
@@ -52,7 +52,6 @@ You may require an array that's too large to allocate on the stack, or whose siz
 The following example shows how to define an array on the heap at run time. It shows how to access the array elements using the subscript operator and by using pointer arithmetic:
 
 ```cpp
-
 void do_something(size_t size)
 {
     // Declare an array of doubles to be allocated on the heap
@@ -104,7 +103,6 @@ int main()
 {
     do_something(108);
 }
-
 ```
 
 ## Initializing arrays
-Original file line number
+Diff line change
@@ Expand Up @@
         }
       ]
     }
     ```
     The JSON file is placed in the *.vs* subfolder. To see that folder, click on the **Show All Files** button at the top of **Solution Explorer**. You can run this task by right-clicking on the root node in **Solution Explorer** and choosing **build hello**. When the task completes you should see a new file, *hello.exe* in **Solution Explorer**.
@@ Expand Down Expand Up @@
         }
       ]
     }
     ```
     To start debugging, choose the executable in the debug dropdown, then click the green arrow:
@@ Expand Down @@