Update 07-relayer.md

Update 07-relayer.md

Update 07-relayer.md

Update 07-relayer.md

Update 07-relayer.md

Update 07-relayer.md

Author: gap-editor

docs/docs/01-ibc/07-relayer.md

@@ -21,7 +21,7 @@ slug: /ibc/relayer
 Events are emitted for every transaction processed by the base application to indicate the execution
 of some logic clients may want to be aware of. This is extremely useful when relaying IBC packets.
 Any message that uses IBC will emit events for the corresponding TAO logic executed as defined in
-the [IBC events document](/events/events).
+the [IBC events document](/docs/events/events.md).
 
 In the SDK, it can be assumed that for every message there is an event emitted with the type `message`,
 attribute key `action`, and an attribute value representing the type of message sent

docs/versioned_docs/version-v10.1.x/01-ibc/07-relayer.md

@@ -21,7 +21,7 @@ slug: /ibc/relayer
 Events are emitted for every transaction processed by the base application to indicate the execution
 of some logic clients may want to be aware of. This is extremely useful when relaying IBC packets.
 Any message that uses IBC will emit events for the corresponding TAO logic executed as defined in
-the [IBC events document](/events/events).
+the [IBC events document](/docs/events/events.md).
 
 In the SDK, it can be assumed that for every message there is an event emitted with the type `message`,
 attribute key `action`, and an attribute value representing the type of message sent

docs/versioned_docs/version-v4.6.x/01-ibc/07-relayer.md

@@ -21,7 +21,7 @@ slug: /ibc/relayer
 Events are emitted for every transaction processed by the base application to indicate the execution
 of some logic clients may want to be aware of. This is extremely useful when relaying IBC packets.
 Any message that uses IBC will emit events for the corresponding TAO logic executed as defined in
-the [IBC events document](/events/events).
+the [IBC events document](/docs/events/events.md).
 
 In the SDK, it can be assumed that for every message there is an event emitted with the type `message`,
 attribute key `action`, and an attribute value representing the type of message sent

docs/versioned_docs/version-v5.4.x/01-ibc/07-relayer.md

@@ -21,7 +21,7 @@ slug: /ibc/relayer
 Events are emitted for every transaction processed by the base application to indicate the execution
 of some logic clients may want to be aware of. This is extremely useful when relaying IBC packets.
 Any message that uses IBC will emit events for the corresponding TAO logic executed as defined in
-the [IBC events document](/events/events).
+the [IBC events document](/docs/events/events.md).
 
 In the SDK, it can be assumed that for every message there is an event emitted with the type `message`,
 attribute key `action`, and an attribute value representing the type of message sent

docs/versioned_docs/version-v6.3.x/01-ibc/07-relayer.md

@@ -21,7 +21,7 @@ slug: /ibc/relayer
 Events are emitted for every transaction processed by the base application to indicate the execution
 of some logic clients may want to be aware of. This is extremely useful when relaying IBC packets.
 Any message that uses IBC will emit events for the corresponding TAO logic executed as defined in
-the [IBC events document](/events/events).
+the [IBC events document](/docs/events/events.md).
 
 In the SDK, it can be assumed that for every message there is an event emitted with the type `message`,
 attribute key `action`, and an attribute value representing the type of message sent

docs/versioned_docs/version-v7.8.x/01-ibc/07-relayer.md

@@ -21,7 +21,7 @@ slug: /ibc/relayer
 Events are emitted for every transaction processed by the base application to indicate the execution
 of some logic clients may want to be aware of. This is extremely useful when relaying IBC packets.
 Any message that uses IBC will emit events for the corresponding TAO logic executed as defined in
-the [IBC events document](/events/events).
+the [IBC events document](/docs/events/events.md).
 
 In the SDK, it can be assumed that for every message there is an event emitted with the type `message`,
 attribute key `action`, and an attribute value representing the type of message sent