File tree Expand file tree Collapse file tree 1 file changed +2
-2
lines changed
docs/eventing/event-registry Expand file tree Collapse file tree 1 file changed +2
-2
lines changed Original file line number Diff line number Diff line change @@ -44,7 +44,7 @@ status:
44
44
` ` `
45
45
46
46
For the full specification for an EventType object, see the
47
- [EventType API reference](../eventing/reference/eventing-api.md#eventing.knative.dev/v1beta2.EventType).
47
+ [EventType API reference](../../ eventing/reference/eventing-api.md#eventing.knative.dev/v1beta2.EventType).
48
48
49
49
The ` metadata.name` field is advisory, that is, non-authoritative.
50
50
It is typically generated using `generateName` to avoid naming collisions.
@@ -295,6 +295,6 @@ Here are a some example Triggers that subscribe to events using exact matching o
295
295
296
296
# # Next steps
297
297
298
- [Knative code samples](../samples/eventing.md) is a useful resource to better understand
298
+ [Knative code samples](../../ samples/eventing.md) is a useful resource to better understand
299
299
some of the event sources. Remember, you must point the sources to a Broker if you want
300
300
automatic registration of EventTypes in the registry.
You can’t perform that action at this time.
0 commit comments