Skip to content

Commit f1bb22a

Browse files
Update docs/code-quality/c6101.md
Co-authored-by: dmitrykobets-msft <89153909+dmitrykobets-msft@users.noreply.github.com>
1 parent 8ce8f44 commit f1bb22a

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

docs/code-quality/c6101.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ The purpose of this warning is to avoid the use of uninitialized values by calle
1717

1818
If the initialization behavior is by design, then the warning is likely caused by incorrect or missing SAL annotations. You can typically resolve these cases by either changing `_Out_` to a more appropriate annotation, or by using the `_Success_()` annotation to help define the success/error states of the function. Having correct annotations on the function is important for the static analysis tools when analyzing the call sites of the function.
1919

20-
### Fix by changes to Parameter annotations
20+
### Fix by changes to parameter annotations
2121

2222
If the parameter is expected to already be in an initialized state and the function conditionally modifies it, then the `_Inout_` annotation may be more appropriate. Another option is to use lower level annotations such as `_Pre_null_`, `_Pre_satisfies_()`, and `_Post_satisfies_()` that provide extra flexibility and control over the expected state of the parameter. For more information on parameter annotations, see [Annotating function parameters and return values](./annotating-function-parameters-and-return-values.md).
2323

0 commit comments

Comments
 (0)