Skip to content
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

Jump to bottom

Fix broken links #6129

Merged
merged 1 commit into from
Sep 26, 2024
Merged

Fix broken links #6129

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/eventing/event-registry/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,7 @@ status:
```

For the full specification for an EventType object, see the
[EventType API reference](../eventing/reference/eventing-api.md#eventing.knative.dev/v1beta2.EventType).
[EventType API reference](../../eventing/reference/eventing-api.md#eventing.knative.dev/v1beta2.EventType).

The `metadata.name` field is advisory, that is, non-authoritative.
It is typically generated using `generateName` to avoid naming collisions.
Expand Down Expand Up @@ -295,6 +295,6 @@ Here are a some example Triggers that subscribe to events using exact matching o

## Next steps

[Knative code samples](../samples/eventing.md) is a useful resource to better understand
[Knative code samples](../../samples/eventing.md) is a useful resource to better understand
some of the event sources. Remember, you must point the sources to a Broker if you want
automatic registration of EventTypes in the registry.
Loading