acrolinx

Author: TylerMSFT

docs/code-quality/c26133.md

@@ -11,7 +11,7 @@ ms.date:     02/19/2025
 
 > Caller failing to hold lock '*lock 1*' before calling function '*function name*', but '*lock 2*' is held instead. Possible annotation mismatch.
 
-Warning C26133 is issued when the analyzer detects that the lock that is required to call a function isn't held when the function is called. However, another lock that appears to be related is held. It is possible the code is thread safe, and the annotations need to be updated.
+Warning C26133 is issued when the analyzer detects that the lock required to call a function isn't held when the function is called. However, another lock that appears to be related is held. It's possible the code is thread-safe, and the annotations need to be updated.
 
 ## Examples
 
@@ -45,7 +45,7 @@ void DoTask()
 }
 ```
 
-In this example, the `DoTask` function is thread-safe and behaves as designed, but that design is not correctly reflected in the concurrency SAL annotations. This is fixed by adjusting the annotations on the custom locking functions to use `criticalSection` rather than `criticalSection->cs`. This could also be fixed by changing the `_Requires_lock_held_` annotation from `customLock01` to `customLock01.cs`.
+In this example, the `DoTask` function is thread-safe and behaves as designed, but that design isn't correctly reflected in the concurrency SAL annotations. Fix by adjusting the annotations on the custom locking functions to use `criticalSection` rather than `criticalSection->cs`. This could also be fixed by changing the `_Requires_lock_held_` annotation from `customLock01` to `customLock01.cs`.
 
 ```cpp
 #include <sal.h>