Update docs/book/src/getting-started.md

docs/book/src/getting-started.md

@@ -42,7 +42,7 @@ This command's primary aim is to produce the Custom Resource (CR) and Custom Res
 
 Consider a typical scenario where the objective is to run an application and its database on a Kubernetes platform. In this context, one object might represent the App, while another denotes the DB. If we define one CRD for the App and another for the DB, we uphold essential concepts like encapsulation, the single responsibility principle, and cohesion. Breaching these principles might lead to complications, making extension, reuse, or maintenance challenging.
 
-In essence, the App CRD will have the DB CRD as its controller. Let's say, for instance, that the application requires a Deployment and Service to run. In this example, the App’s Controller will cater to these needs. Similarly, the DB’s controller will manage the business logic of its items.
+In essence, the App CRD and the DB CRD will have their controller. Let's say, for instance, that the application requires a Deployment and Service to run. In this example, the App’s Controller will cater to these needs. Similarly, the DB’s controller will manage the business logic of its items.
 
 Therefore, for each CRD, there should be one distinct controller, adhering to the design outlined by the [controller-runtime][controller-runtime]. For further information see [Groups and Versions and Kinds, oh my!][group-kind-oh-my].