From 5b349ce767822aef29b16474c219f9be795cd0ac Mon Sep 17 00:00:00 2001 From: Camila Macedo <7708031+camilamacedo86@users.noreply.github.com> Date: Wed, 18 Sep 2024 13:46:33 +0100 Subject: [PATCH] Update docs/book/src/reference/watching-resources.md Co-authored-by: Erik Mogensen --- docs/book/src/reference/watching-resources.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/book/src/reference/watching-resources.md b/docs/book/src/reference/watching-resources.md index da488b39dc3..0cf03d11433 100644 --- a/docs/book/src/reference/watching-resources.md +++ b/docs/book/src/reference/watching-resources.md @@ -100,7 +100,7 @@ and **Secondary Resources** remains the same: Therefore, regardless of whether the resource was defined by your project or by another project, your controller can watch, reconcile, and manage changes to these resources as needed. -## Why watch the secondary resources matters? +## Why does watching the secondary resources matter? When building a Kubernetes controller, it’s crucial to not only focus on **Primary Resources** but also to monitor **Secondary Resources**.