diff --git a/docs/book/src/reference/good-practices.md b/docs/book/src/reference/good-practices.md
index d09e20255b1..443bece4fc4 100644
--- a/docs/book/src/reference/good-practices.md
+++ b/docs/book/src/reference/good-practices.md
@@ -22,7 +22,7 @@ By developing Operator pattern solutions, we extend the Kubernetes api. Understa
 
 Avoid a design solution where the same controller reconciles more than one Kind. Having many Kinds (such as CRDs), that are all managed by the same controller, usually goes against the design proposed by controller-runtime. Furthermore, this might hurt concepts such as encapsulation, the Single Responsibility Principle, and Cohesion. Damaging these concepts may cause unexpected side effects and increase the difficulty of extending, reusing, or maintaining the operator.
 
-## How to use Status Conditionals
+## Why You Should Adopt Status Conditions
 
 We recommends you to manage your solutions using Status Conditionals. You can check the scaffold provided via the [deploy-image][deploy-image] as an example for its implementation.