Update patterns/1-initial/transparent-catalog-privacy-controls-posture.md

Co-authored-by: Amburi Roy <amburi.roy@gmail.com>

Author: shrutibist

patterns/1-initial/transparent-catalog-privacy-controls-posture.md

@@ -6,7 +6,7 @@ Transparent Catalog of Privacy Controls and Posture
 
 Large organizations often have no standardized, discoverable set of privacy controls that engineering teams can implement against, and no reliable visibility into which teams actually comply with existing privacy requirements, so risk stays hidden until an audit or incident surfaces it. Publish a version-controlled Privacy Controls Catalog as the shared baseline (open to engineering-proposed refinements but authored by privacy/legal), and maintain a separate, access-tiered Privacy Posture Register through the same pull-request and trusted-committer workflow, so compliance becomes a continuously queryable property of the codebase instead of a periodic audit exercise.
 
-# Problem
+## Problem
 
 In a large enterprise, privacy requirements typically live in policy PDFs, wiki pages, or the heads of a small central privacy/legal team. Two distinct but related problems follow from this: