Skip to content

Commit d32b374

Browse files
authored
Merge pull request #600 from montaro/patch-1
Fix some phrases in what_is_a_controller.md
2 parents aaddf9f + 8602652 commit d32b374

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

docs/book/basics/what_is_a_controller.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ A Kubernetes Controller is a routine running in a Kubernetes cluster that watche
99
update / delete events on Resources, and triggers a Reconcile function in response. Reconcile
1010
is a function that may be called at any time with the Namespace and Name of an object (Resource
1111
instance), and it will make the cluster state match the state declared in the object Spec.
12-
Upon completion, Reconcile updates the object Status the new actual state.
12+
Upon completion, Reconcile updates the object Status to the new actual state.
1313

1414
It is common for Controllers to watch for changes to the Resource type that they Reconcile
1515
*and* Resource types of objects they create. e.g. a ReplicaSet Controller watches for
@@ -69,11 +69,11 @@ rollout before starting the next.
6969

7070
## Watching Events
7171

72-
The Controller Reconcile is triggered both by cluster events.
72+
The Controller Reconcile is triggered by cluster events.
7373

7474
##### Watching Resources
7575

76-
Controllers must watch for events for the Resource they Reconcile. The ReplicaSetController
76+
Controllers must watch for events for the Resource they Reconcile. The ReplicaSetController
7777
watches for changes to ReplicaSets and triggers a Reconcile in response.
7878

7979
###### ReplicaSet Creation
@@ -157,7 +157,7 @@ Instead the Controller must write back the Status of the object at each Reconcil
157157
users must check the object Status.
158158

159159
{% panel style="info", title="Status" %}
160-
The controller will keep Status up-to-date both in response to user initiated events, but also
160+
The controller will keep Status up-to-date not only in response to user initiated events, but also
161161
in response to non-user initiated events, such as Node failures.
162162
{% endpanel %}
163163

0 commit comments

Comments
 (0)