docs(extreme-programming): update content

docs(extreme-programming): update content

apps/docs/content/docs/concepts/extreme-programming/index.mdx

@@ -70,17 +70,17 @@ mindmap
 
 ### Key Practices
 
-<Callout title='Key Practices of Extreme Programming (XP)'>
-1. **Pair Programming**: Two developers work together at one workstation, enhancing code quality and team collaboration.
-2. **Test-Driven Development (TDD)**: Write tests before writing code, ensuring every piece of code works as intended.
-3. **Continuous Integration**: Frequently integrate code into the main branch to detect issues early.
-4. **Small Releases**: Release working software frequently, often in small increments, to get feedback and improve based on customer needs.
-5. **Refactoring**: Regularly improve and optimize code without changing its functionality.
-6. **Sustainable Pace**: Avoid overworking the team to maintain a consistent and sustainable workflow.
-7. **Collective Code Ownership**: Everyone on the team is responsible for all the code. This encourages collaboration and reduces silos.
-8. **On-Site Customer**: Have someone from the customer side available to clarify requirements and provide immediate feedback.
+| Concept   | Description |
+|---------|-------------|
+| `Pair Programming`  | Two developers work together at one workstation, enhancing code quality and team collaboration |
+| `Test-Driven Development (TDD)`  | Write tests before writing code, ensuring every piece of code works as intended |
+| `Continuous Integration`  | Frequently integrate code into the main branch to detect issues early |
+| `Small Releases`  | Release working software frequently, often in small increments, to get feedback and improve based on customer needs |
+| `Refactoring` | Regularly improve and optimize code without changing its functionality |
+| `Sustainable Pace` |Avoid overworking the team to maintain a consistent and sustainable workflow |
+| `Collective Code Ownership` |  Everyone on the team is responsible for all the code. This encourages collaboration and reduces silos |
+| `On-Site Customer` | Have someone from the customer side available to clarify requirements and provide immediate feedback |
 
-</Callout>
 
 <Accordions>
     <Accordion title="What's Agile?">

apps/docs/content/docs/concepts/extreme-programming/team-responsibilities.mdx

@@ -31,7 +31,6 @@ flowchart
 - **Encourage testable deliverables** to meet exact user needs, prevent scope creep, and avoid design bankruptcy.
 - **Support pair programming** to maintain productivity, improve chemistry, and ensure a sustainable workflow.
 
-
 ### Software Development
 
 - **Write tests** from day one.
@@ -46,7 +45,7 @@ flowchart
 - **Seek feedback** on the usability and aesthetics of the product.
 - **Review designs** often to avoid wasted effort and pivot early.
 
-## User
+### User
 
 - **Provide examples** to improve communication.
 - **Provide frequent demos and reviews** to ensure the solution meets your needs.