From 9d7d42c1bcac5bc1442e6ce1d516d345aa6dff9e Mon Sep 17 00:00:00 2001
From: Sajiyah Salat <109643863+Sajiyah-Salat@users.noreply.github.com>
Date: Mon, 8 May 2023 07:16:03 +0530
Subject: [PATCH] Update docs/book/src/reference/good-practices.md

Co-authored-by: Camila Macedo <7708031+camilamacedo86@users.noreply.github.com>
---
 docs/book/src/reference/good-practices.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/docs/book/src/reference/good-practices.md b/docs/book/src/reference/good-practices.md
index 30a59877c09..d09e20255b1 100644
--- a/docs/book/src/reference/good-practices.md
+++ b/docs/book/src/reference/good-practices.md
@@ -2,7 +2,9 @@
 
 ## What is "Reconciliation" in Operators?
 
-The reconciliation is a continuos  loop that performs necessary actions on the current state to ensure that the Custom Resource reaches the desired state as specified by the user.
+When you create a project using Kubebuilder, see the scaffolded code generated under `cmd/main.go`. This code initializes a [Manager][controller-runtime-manager], and the project relies on the [controller-runtime][controller-runtime] framework. The Manager manages [Controllers][controllers], which offer a reconcile function that synchronizes resources until the desired state is achieved within the cluster.
+
+Reconciliation is an ongoing loop that executes necessary operations to maintain the desired state, adhering to Kubernetes principles, such as the [control loop][k8s-control-loop]. For further information, check out the [Operator patterns][k8s-operator-pattern] documentation from Kubernetes to better understand those concepts. 
 
 ## Why should reconciliations be idempotent?