Merge pull request #4539 from MicrosoftDocs/main638191639759544158sync_temp

For protected CLA branch, push strategy should use PR and merge to target branch method to work around git push error

Author: learn-build-service-prod[bot]

docs/code-quality/c6001.md

@@ -4,7 +4,6 @@ title: Warning C6001
 ms.date: 10/04/2022
 f1_keywords: ["C6001", "USING_UNINIT_VAR", "__WARNING_USING_UNINIT_VAR"]
 helpviewer_keywords: ["C6001"]
-ms.assetid: 55e779f1-7295-48f7-8ce1-b43898b36cd8
 ---
 # Warning C6001
 
@@ -18,7 +17,7 @@ Code analysis name: `USING_UNINIT_VAR`
 
 ## Example
 
-The following code generates this warning because variable `i` is only initialized if `b` is true; otherwise an uninitialized `i` is returned:
+The following code generates this warning because variable `i` is only initialized if `b` is true:
 
 ```cpp
 int f( bool b )
@@ -49,9 +48,7 @@ int f( bool b )
 
 ## Heuristics
 
-Variables are also considered initialized when they're passed by reference to
-another function. Thus, the following example would also consider `i` to be
-initialized.
+The following example shows that passing a variable to a function by reference causes the compiler to assume that it's initialized:
 
 ```cpp
 void init( int& i );
@@ -66,18 +63,13 @@ int f( bool b )
    {
       i = 0;
    }
-   return i; // i is assumed to be initialized by init(i)
+   return i; // i is assumed to be initialized because it's passed by reference to init()
 }
 ```
 
-This is to support the pattern of passing a pointer to a variable into
-an initialization function.
+This supports the pattern of passing a pointer to a variable into an initialization function.
 
-Since many functions expect pointers to point to initialized data already, this
-heuristic can lead to false negatives. [SAL annotations] such as `_In_` and
-`_Out_` can be used to more precisely describe a function's behavior. For
-example, in the following we call an external function that expects its argument
-to already be initialized and the warning is still generated.
+This heuristic can lead to false negatives because many functions expect pointers that point to initialized data. Use [SAL annotations](annotating-function-parameters-and-return-values.md), such as `_In_` and `_Out_`, to describe the function's behavior. The following example calls a function that expects its argument to be initialized, so a warning is generated:
 
 ```cpp
 void use( _In_ int& i );
@@ -86,7 +78,7 @@ int f( bool b )
 {
    int i;
 
-   use(i); // uninitialized variable warning because of _In_ annotation on use
+   use(i); // uninitialized variable warning because of the _In_ annotation on use()
 
    if ( b )
    {
@@ -96,8 +88,6 @@ int f( bool b )
 }
 ```
 
-[SAL annotations]: ./annotating-function-parameters-and-return-values.md
-
 ## See also
 
 [Compiler Warning (level 1 and level 4) C4700](../error-messages/compiler-warnings/compiler-warning-level-1-and-level-4-c4700.md)