Merge branch 'main' into PORT-16654

Author: dev-habib-nuhu

best_practices.md

@@ -1,5 +1,19 @@
 # Port documentation style guide
 
+___
+
+**Header capitalization rules:** Use sentence case for headers with only the first word capitalized.
+
+❌ "## Sync Approaches And Methods"  
+✅ "## Sync approaches and methods"
+
+Note: Well-known product names such as Lambda, Kubernetes, ArgoCD, etc. should follow their standard capitalization rules and styling.
+
+❌ "aws"  
+✅ "AWS"
+
+___
+
 This document details guidelines for contributing to Port's documentation, and demonstrates how to correctly write and review documentation content.
 
 <b>Pattern 1: Always standardize collapsible details with bold titles and "(click to expand)" for consistency and usability across docs.</b>
@@ -208,34 +222,6 @@ Example code after:
 
 ___
 
-<b>Pattern 8: Use sentence case for headers with only the first word capitalized, and ensure links follow capitalization rules based on their position in the sentence.</b>
-
-Example code before:
-
-```
-## Sync Approaches And Methods
-
-Check out our [Guide](docs/guide.md) for more information.
-```
-
-Example code after:
-
-```
-## Sync approaches and methods
-
-Check out our [guide](docs/guide.md) for more information.
-```
-
-Note: Well-known product names such as Lambda, Kubernetes, ArgoCD, etc. should follow their standard capitalization rules and styling.
-
-<details><summary>Examples for relevant past discussions:</summary>
-
-<!-- Add links to relevant PR discussions here -->
-
-</details>
-
-___
-
 <b>Pattern 9: Use "We" language instead of commanding "You" language to create a collaborative, guiding tone rather than issuing commands.</b>
 
 Example code before:
@@ -699,4 +685,4 @@ Before submitting your contribution, review it against this checklist:
 - [ ] Tone is consistent with Port's documentation style
 - [ ] Content is organized logically
 - [ ] Technical terms are explained or linked to definitions
-- [ ] No unnecessary jargon or marketing language
+- [ ] No unnecessary jargon or marketing language