Skip to content

Commit b880791

Browse files
authored
docs: fix small typos (#2264)
1 parent ed1aed5 commit b880791

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

docs/documentation/features.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -461,7 +461,7 @@ reschedule reconciliations.
461461
462462
There are few interesting points here:
463463
464-
The `CustomResourceEvenSource` event source is a special one, responsible for handling events
464+
The `CustomResourceEventSource` event source is a special one, responsible for handling events
465465
pertaining to changes affecting our primary resources. This `EventSource` is always registered
466466
for every controller automatically by the SDK. It is important to note that events always relate
467467
to a given primary resource. Concurrency is still handled for you, even in the presence of
@@ -493,7 +493,7 @@ related [method](https://github.com/java-operator-sdk/java-operator-sdk/blob/mai
493493
494494
To register event sources, your `Reconciler` has to implement the
495495
[`EventSourceInitializer`](https://github.com/java-operator-sdk/java-operator-sdk/blob/main/operator-framework-core/src/main/java/io/javaoperatorsdk/operator/api/reconciler/EventSourceInitializer.java)
496-
interface and initiliaze a list of event sources to register. One way to see this in action is
496+
interface and initialize a list of event sources to register. One way to see this in action is
497497
to look at the
498498
[tomcat example](https://github.com/java-operator-sdk/java-operator-sdk/blob/main/sample-operators/tomcat-operator/src/main/java/io/javaoperatorsdk/operator/sample/TomcatReconciler.java)
499499
(irrelevant details omitted):

docs/documentation/glossary.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ permalink: /docs/glossary
1313
- **Secondary Resource** - any resource that the controller needs to manage the reach the desired
1414
state represented by the primary resource. These resources can be created, updated, deleted or
1515
simply read depending on the use case. For example, the `Deployment` controller manages
16-
`ReplicatSet` instances when trying to realize the state represented by the `Deployment`. In
16+
`ReplicaSet` instances when trying to realize the state represented by the `Deployment`. In
1717
this scenario, the `Deployment` is the primary resource while `ReplicaSet` is one of the
1818
secondary resources managed by the `Deployment` controller.
1919
- **Dependent Resource** - a feature of JOSDK, to make it easier to manage secondary resources. A

0 commit comments

Comments
 (0)