From 9078d821c8e758431c1d60bb1cbc6d22bd706b25 Mon Sep 17 00:00:00 2001
From: Carina Kothe <69976260+grischperl@users.noreply.github.com>
Date: Mon, 13 Nov 2023 14:27:06 +0100
Subject: [PATCH] Update documentation sidebar (#239)

* Update sidebar
Fix link

* Add review comments
---
 docs/user/README.md   | 2 +-
 docs/user/_sidebar.md | 6 ++++--
 2 files changed, 5 insertions(+), 3 deletions(-)

diff --git a/docs/user/README.md b/docs/user/README.md
index 540979b1..76a405f3 100644
--- a/docs/user/README.md
+++ b/docs/user/README.md
@@ -16,7 +16,7 @@ Kyma Eventing uses the following technology:
 
 Kyma Eventing follows the PubSub messaging pattern: Kyma publishes messages to a messaging backend, which filters these messages and sends them to interested subscribers. Kyma does not send messages directly to the subscribers as shown below:
 
-![PubSub](/docs/assets/evnt-pubsub.svg)
+![PubSub](../assets/evnt-pubsub.svg)
 
 Eventing in Kyma from a user’s perspective works as follows:
 
diff --git a/docs/user/_sidebar.md b/docs/user/_sidebar.md
index beca2d5c..23ab3f94 100644
--- a/docs/user/_sidebar.md
+++ b/docs/user/_sidebar.md
@@ -1,5 +1,7 @@
 * [Home](/README.md)
-* [Kyma module](README.md)
+* [Eventing module](README.md)
+* [Module lifecycle](01-manager.md)
+* [Configuration](02-configuration.md)
 * [Eventing architecture](evnt-architecture.md)
 * [Event names](evnt-event-names.md)
 * [Eventing metrics](evnt-eventing-metrics.md)
@@ -16,4 +18,4 @@
   * [NATS JetStream backend troubleshooting](./troubleshooting/evnt-02-jetstream-troubleshooting.md)
   * [Subscriber receives irrelevant events](./troubleshooting/evnt-03-type-collision.md)
   * [Eventing backend stopped receiving events due to full storage](./troubleshooting/evnt-04-free-jetstream-storage.md)
-  * [Published events are pending in the stream](./troubleshooting/evnt-05-fix-pending-messages.md)
\ No newline at end of file
+  * [Published events are pending in the stream](./troubleshooting/evnt-05-fix-pending-messages.md)