removed some unnecesary explanations

input-output-hk · Oct 27, 2024 · eaf3c0c · eaf3c0c
1 parent ea4c89a
commit eaf3c0c
Show file tree

Hide file tree

Showing 4 changed files with 4 additions and 66 deletions.
diff --git a/docs/quality-strategy/03-cost-of-poor-software.md b/docs/quality-strategy/03-cost-of-poor-software.md
diff --git a/docs/quality-strategy/04-complexity.md b/docs/quality-strategy/04-complexity.md
diff --git a/docs/quality-strategy/05-how-it-works.md b/docs/quality-strategy/05-how-it-works.md
@@ -3,7 +3,7 @@ title: How it works
 metaTitle: How it works
 ---
 
-This section provides instructions on how to develop and use quality strategies effectively, ensuring that your project teams are aligned and equipped to deliver high-quality products.
+This section provides guidance on how to develop and use quality strategies effectively, ensuring that the project teams are aligned and equipped to deliver high-quality products.
 
 The quality strategy tool is designed to foster a structured and proactive approach to quality in software development projects. It ensures that every phase of your product development adheres to high-quality standards, leaving _no detail unconsidered_, thereby improving both the efficiency and outcomes of your projects
 

diff --git a/docs/quality-strategy/resources/01-faqs.md b/docs/quality-strategy/resources/01-faqs.md
@@ -10,15 +10,15 @@ The following conversation is:
 
 ![Example conversation](/img/quality-strategy/conversation.png)
 
-### How do you prevent it?
+**How do you prevent it?**
 
 You write down - before you start - what “finishing Thing A” actually is, and you don’t start building Thing A until there’s agreement on that from the relevant parties.
 
-### So what is a ‘Quality Strategy/DoD’?
+**So what is a ‘Quality Strategy/DoD’?**
 
 It’s the minimum you need to write down up front to achieve the goal of never having this Terrible Conversation again.
 
-### So a ‘Quality Strategy/DoD’ is only a term for a really skeleton type of document, then?
+**So a ‘Quality Strategy/DoD’ is only a term for a skeleton type of document, then?**
 
 Let’s not be too dogmatic about it. If you start adding detailed Acceptance Criteria to your doc, it’s still a ‘Quality Strategy/DoD’, as long as it can prevent this Terrible Conversation.