Remove metadata comments and fix formatting in docs

Author: Rastaban

docs/code-quality/c26132.md

@@ -1,12 +1,8 @@
 ---
-# Required metadata
-# For more information, see https://review.learn.microsoft.com/en-us/help/platform/learn-editor-add-metadata?branch=main
-# For valid values of ms.service, ms.prod, and ms.topic, see https://review.learn.microsoft.com/en-us/help/platform/metadata-taxonomies?branch=main
-
 title: Warning C26132
 description: Documentation on static analysis warning C26132
-author:      Rastaban # GitHub alias
-ms.author:   philc # Microsoft alias
+author:      Rastaban
+ms.author:   philc
 ms.service: visual-cpp
 ms.topic: article
 ms.date:     02/11/2025
@@ -21,13 +17,12 @@ Warning C26132 is issued when the analyzer detects that the lock that is annotat
 
 In the following example, C26132 is emitted when `data` is used.
 
-> warning C26132: Variable 'data' should be protected by 'customLock01', but '(&customLock01)->cs' is held instead. Possible annotation mismatch.
-
  The variable `data` is annotated to be protected by `customLock01`, but the locking function `CustomLockAcquire` is annotated to acquire the related lock `customLock01->cs`.
 
 ```cpp
 #include <sal.h>
-struct CustomLock {
+struct CustomLock 
+{
     int cs; // "Critical Section" lock
 };
 
@@ -48,11 +43,12 @@ void Initialize(_Guarded_by_(customLock01) int* data)
 }
 ```
 
-In this example the `Initialize` 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 `_Guarded_by_` annotation from `customLock01` to `customLock01.cs`.
+In this example, the `Initialize` 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 `_Guarded_by_` annotation from `customLock01` to `customLock01.cs`.
 
 ```cpp
 #include <sal.h>
-struct CustomLock {
+struct CustomLock 
+{
     int cs; // "Critical Section" lock
 };
 

docs/code-quality/c26133.md

@@ -1,12 +1,8 @@
 ---
-# Required metadata
-# For more information, see https://review.learn.microsoft.com/en-us/help/platform/learn-editor-add-metadata?branch=main
-# For valid values of ms.service, ms.prod, and ms.topic, see https://review.learn.microsoft.com/en-us/help/platform/metadata-taxonomies?branch=main
-
 title: Warning C26133
 description: Documentation on static analysis warning C26133
-author:      Rastaban # GitHub alias
-ms.author:   philc # Microsoft alias
+author:      Rastaban
+ms.author:   philc
 ms.service: visual-cpp
 ms.topic: article
 ms.date:     02/11/2025
@@ -26,7 +22,8 @@ In the following example, C26133 is emitted when `DoTaskWithCustomLock` is calle
 ```cpp
 #include <sal.h>
 
-struct CustomLock {
+struct CustomLock
+{
     int cs; // "Critical Section"
 };
 
@@ -48,12 +45,13 @@ 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 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`.
 
 ```cpp
 #include <sal.h>
 
-struct CustomLock {
+struct CustomLock
+{
     int cs; // "Critical Section"
 };