Minor documentation fixes.

Author: ioquatix

context/documentation-guidelines.md

@@ -73,7 +73,7 @@ Every feature or concept should be introduced with clear context about why users
 1. **Problem statement**: What challenge does this solve?
 2. **Use cases**: When would users encounter this need?
 3. **Solution overview**: How does this feature address the problem?
-4. **Implementation**: Code examples and detailed usage
+4. **Implementation**: Code examples and detailed usage.
 
 #### Example
 
@@ -129,7 +129,7 @@ When documenting advanced features, follow this structure:
 4. **Best Practices**: When to use vs when not to use
 5. **Common Pitfalls**: What to watch out for
 
-#### Template
+####  Template
 
 ```markdown
 ## [Feature Name]
@@ -237,13 +237,15 @@ Help users understand when to choose between alternatives:
 
 Every code example should demonstrate a realistic scenario, not abstract operations:
 
-❌ **Abstract**:
+❌ Abstract:
+
 ```ruby
 client.set("key", "value")
 client.get("key")
 ```
 
-✅ **Contextual**:
+✅ Contextual:
+
 ```ruby
 # Store user session data:
 client.set("session:#{session_id}", user_data.to_json)

guides/documentation-guidelines/readme.md

@@ -237,13 +237,15 @@ Help users understand when to choose between alternatives:
 
 Every code example should demonstrate a realistic scenario, not abstract operations:
 
-❌ **Abstract**:
+❌ Abstract:
+
 ```ruby
 client.set("key", "value")
 client.get("key")
 ```
 
-✅ **Contextual**:
+✅ Contextual:
+
 ```ruby
 # Store user session data:
 client.set("session:#{session_id}", user_data.to_json)