fix: formatting

Signed-off-by: Abhishek kushwaha <[email protected]>

versioned_docs/version-2.0.0/concepts/reference/glossary/error-guessing.md

@@ -10,33 +10,33 @@ keywords:
   - API
 ---
 
-### What is Error Guessing?
+## What is Error Guessing?
 
 Error guessing is an intuitive and experience-based software testing technique that relies on developer and tester's knowledge and creativity to identify potential defects in a system. This method involves anticipating where errors are likely to occur based on past experiences, common programming mistakes, and an understanding of the system's architecture.
 
 
-### Key aspects
+## Key aspects
 
-Intuition: Testers use their instincts and experience to predict where errors might lurk.
-Domain knowledge: Understanding the application's purpose and typical user behavior helps in identifying potential issues.
-Historical data: Past bugs and common error patterns inform the guessing process.
-Creativity: Testers think outside the box to imagine scenarios that might cause failures.
+- **Intuition:** Testers use their instincts and experience to predict where errors might lurk.
+- **Domain knowledge:** Understanding the application's purpose and typical user behavior helps in identifying potential issues.
+- **Historical data:** Past bugs and common error patterns inform the guessing process.
+- **Creativity:** Testers think outside the box to imagine scenarios that might cause failures.
 
 
-### Benefits
+## Benefits
 
-Uncovers unique defects: Can reveal issues missed by systematic testing approaches.
-Cost-effective: Requires minimal setup and can be performed quickly.
-Improves over time: The technique becomes more effective as testers gain experience.
-Adaptable: Can be applied to various types of software and testing phases.
+- **Uncovers unique defects:** Can reveal issues missed by systematic testing approaches.
+- **Cost-effective:** Requires minimal setup and can be performed quickly.
+- **Improves over time:** The technique becomes more effective as testers gain experience.
+- **Adaptable:** Can be applied to various types of software and testing phases.
 
-### Challenges
+## Challenges
 
-Subjectivity: Relies heavily on individual tester's skills and experience.
-Lack of structure: May not provide comprehensive coverage of all system aspects.
-Difficult to replicate: Success varies between testers and isn't easily standardized.
-Time-consuming: Can be inefficient if not guided by experience or historical data.
+- **Subjectivity:** Relies heavily on individual tester's skills and experience.
+- **Lack of structure:** May not provide comprehensive coverage of all system aspects.
+- **Difficult to replicate:** Success varies between testers and isn't easily standardized.
+- **Time-consuming:** Can be inefficient if not guided by experience or historical data.
 
-### Conclusion
+## Conclusion
 
 While error guessing is not systematic like other testing methods, it can be highly effective when combined with more structured approaches. It allows testers to explore edge cases and unusual scenarios that might be overlooked by conventional test cases. However, the success of error guessing largely depends on the tester's expertise and familiarity with the system. As such, it's often used as a complementary technique rather than a standalone method in comprehensive testing strategies.

versioned_docs/version-2.0.0/concepts/reference/glossary/microservice-testing.md

@@ -10,20 +10,20 @@ keywords:
   - API
 ---
 
-### What is Microservices Testing?
+## What is Microservices Testing?
 
 Microservice testing is the process of validating individual components of a microservices architecture to ensure they function correctly both in isolation and as part of the larger system. Unlike monolithic applications, microservices present unique challenges in testing due to their distributed nature and complex interactions.
 
 
-### Benefits of Microservices Testing:
+## Benefits of Microservices Testing:
 - **Improved fault isolation**: Testing individual services allows for easier identification and resolution of issues.
 - **Faster deployment cycles**: Independent testing of services enables faster release cycles.
 - **Enhanced scalability**: Testing services in isolation helps identify bottlenecks and optimize performance.
 - **Easier maintenance and updates**: Testing microservices independently reduces the risk of regressions.
 - **Better support for continuous integration and delivery (CI/CD)** : Microservices testing enables automated testing and deployment pipelines.
 
 
-### Challenges in Microservices Testing:
+## Challenges in Microservices Testing:
 
 - **Complex service dependencies** :
    - Microservices often rely on other services, databases, or third-party APIs, making it challenging to test in isolation.
@@ -38,7 +38,7 @@ Microservice testing is the process of validating individual components of a mic
     - Creating and managing test data for multiple services can be time-consuming and error-prone.
 
 
-### Overcoming Challenges with Keploy
+## Overcoming Challenges with Keploy
 
 Keploy is an innovative testing tool designed to address many of the challenges associated with microservices testing. Here's how it helps:
 <img src="https://keploy.io/docs/gif/record-replay.gif?raw=true"/>