Skip to content

docs: fix small typos #2264

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 5, 2024
Merged

docs: fix small typos #2264

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/documentation/features.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -461,7 +461,7 @@ reschedule reconciliations.

There are few interesting points here:

The `CustomResourceEvenSource` event source is a special one, responsible for handling events
The `CustomResourceEventSource` event source is a special one, responsible for handling events
pertaining to changes affecting our primary resources. This `EventSource` is always registered
for every controller automatically by the SDK. It is important to note that events always relate
to a given primary resource. Concurrency is still handled for you, even in the presence of
Expand Down Expand Up @@ -493,7 +493,7 @@ related [method](https://github.com/java-operator-sdk/java-operator-sdk/blob/mai

To register event sources, your `Reconciler` has to implement the
[`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)
interface and initiliaze a list of event sources to register. One way to see this in action is
interface and initialize a list of event sources to register. One way to see this in action is
to look at the
[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)
(irrelevant details omitted):
Expand Down
2 changes: 1 addition & 1 deletion docs/documentation/glossary.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ permalink: /docs/glossary
- **Secondary Resource** - any resource that the controller needs to manage the reach the desired
state represented by the primary resource. These resources can be created, updated, deleted or
simply read depending on the use case. For example, the `Deployment` controller manages
`ReplicatSet` instances when trying to realize the state represented by the `Deployment`. In
`ReplicaSet` instances when trying to realize the state represented by the `Deployment`. In
this scenario, the `Deployment` is the primary resource while `ReplicaSet` is one of the
secondary resources managed by the `Deployment` controller.
- **Dependent Resource** - a feature of JOSDK, to make it easier to manage secondary resources. A
Expand Down