From c34fe3dcab052ce435224507b0ec13a4cca1c718 Mon Sep 17 00:00:00 2001
From: Simplychee <simplychee@gmail.com>
Date: Wed, 25 Oct 2023 13:01:02 +0300
Subject: [PATCH 01/11] deploy

---
 .../user-guide/distributed-tracing/services.md    | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/_source/user-guide/distributed-tracing/services.md b/_source/user-guide/distributed-tracing/services.md
index fb919bf7e..ec02e83f8 100644
--- a/_source/user-guide/distributed-tracing/services.md
+++ b/_source/user-guide/distributed-tracing/services.md
@@ -71,6 +71,21 @@ Hovering over the graphs provides values for the specific time point, allowing y
 
 You can toggle your view between pods and nodes inside the service.
 
+## Track Deployment Data
+
+You can enrich your Service Overview graphs by adding an indication of recent deployments, helping you determine if a deployment has increased response times for end-users, altered your application's memory/CPU footprint, or introduced any other performance-related changes.
+
+To enbale deployment tracking ability, run the [**Telemetry Collector**](https://app.logz.io/#/dashboard/send-your-data/agent/new) on your Kubernetes clusters. You can also activate this process **manuallty**, by installing [Logz.io Kubernetes events Helm chart](https://app.logz.io/#/dashboard/integrations/Kubernetes:~:text=user%20guide.-,Send%20your%20deploy%20events%20logs,-This%20integration%20sends) and sending Kubernetes deploy events logs.
+
+Once enabled, navigate to [Services](https://app.logz.io/#/dashboard/spm/service-list/table?timeFrame=2h&compareTo=1d) and choose one of your running services. The deployment marker will appear in your graphs, marked by a dotted vertical line.
+
+![deployment popup](https://dytvr9ot2sszz.cloudfront.net/logz-docs/services/deplyment-popup.png)
+
+You can view additional deployment data by clicking on the line. This data includes the deployment time, the associated service and environment, and a quick link to view the commit in your logs.
+
+Click on the commit button to access and view your own code that's related to this deployment, allowing you to probe deeper into the relevant data.
+
+
 <!-- ### Logs overview
 
 All of the logs related to the service are shown at the bottom of the page. This view includes a graph view of the log levels and a table view with the following:

From 62883fef57ae2f757659c04f0b9520e1a2d75d37 Mon Sep 17 00:00:00 2001
From: Simplychee <simplychee@gmail.com>
Date: Wed, 25 Oct 2023 13:08:37 +0300
Subject: [PATCH 02/11] typo

---
 _source/user-guide/distributed-tracing/services.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/_source/user-guide/distributed-tracing/services.md b/_source/user-guide/distributed-tracing/services.md
index ec02e83f8..3593bf860 100644
--- a/_source/user-guide/distributed-tracing/services.md
+++ b/_source/user-guide/distributed-tracing/services.md
@@ -75,7 +75,7 @@ You can toggle your view between pods and nodes inside the service.
 
 You can enrich your Service Overview graphs by adding an indication of recent deployments, helping you determine if a deployment has increased response times for end-users, altered your application's memory/CPU footprint, or introduced any other performance-related changes.
 
-To enbale deployment tracking ability, run the [**Telemetry Collector**](https://app.logz.io/#/dashboard/send-your-data/agent/new) on your Kubernetes clusters. You can also activate this process **manuallty**, by installing [Logz.io Kubernetes events Helm chart](https://app.logz.io/#/dashboard/integrations/Kubernetes:~:text=user%20guide.-,Send%20your%20deploy%20events%20logs,-This%20integration%20sends) and sending Kubernetes deploy events logs.
+To enable deployment tracking ability, run the [**Telemetry Collector**](https://app.logz.io/#/dashboard/send-your-data/agent/new) on your Kubernetes clusters. You can also activate this process **manually** by installing [Logz.io Kubernetes events Helm chart](https://app.logz.io/#/dashboard/integrations/Kubernetes:~:text=user%20guide.-,Send%20your%20deploy%20events%20logs,-This%20integration%20sends) and sending Kubernetes deploy events logs.
 
 Once enabled, navigate to [Services](https://app.logz.io/#/dashboard/spm/service-list/table?timeFrame=2h&compareTo=1d) and choose one of your running services. The deployment marker will appear in your graphs, marked by a dotted vertical line.
 

From d76f7b660b6d1f3f130bf57b9275592f65edc73f Mon Sep 17 00:00:00 2001
From: Simplychee <simplychee@gmail.com>
Date: Wed, 25 Oct 2023 13:10:11 +0300
Subject: [PATCH 03/11] button

---
 _source/user-guide/distributed-tracing/services.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/_source/user-guide/distributed-tracing/services.md b/_source/user-guide/distributed-tracing/services.md
index 3593bf860..64d070098 100644
--- a/_source/user-guide/distributed-tracing/services.md
+++ b/_source/user-guide/distributed-tracing/services.md
@@ -83,7 +83,7 @@ Once enabled, navigate to [Services](https://app.logz.io/#/dashboard/spm/service
 
 You can view additional deployment data by clicking on the line. This data includes the deployment time, the associated service and environment, and a quick link to view the commit in your logs.
 
-Click on the commit button to access and view your own code that's related to this deployment, allowing you to probe deeper into the relevant data.
+Click **Go to commit** to access and view your own code related to this deployment, allowing you to probe deeper into the relevant data.
 
 
 <!-- ### Logs overview

From 889fdc6f01f875772351c6ce28965a0ba495436e Mon Sep 17 00:00:00 2001
From: Simplychee <simplychee@gmail.com>
Date: Mon, 30 Oct 2023 11:26:58 +0200
Subject: [PATCH 04/11] k360

---
 _source/user-guide/k360/index.md | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/_source/user-guide/k360/index.md b/_source/user-guide/k360/index.md
index 5b3c02f71..539b49d86 100644
--- a/_source/user-guide/k360/index.md
+++ b/_source/user-guide/k360/index.md
@@ -155,6 +155,22 @@ The **Metrics** tab presents useful data in graph form. These graphs provides a
 
 ![Stateful menu Overview](https://dytvr9ot2sszz.cloudfront.net/logz-docs/k360/metrics-quick-view.png)
 
+#### Track Deployment Data
+{:.no_toc}
+
+You can enrich your Kubernetes 360 graphs by adding an indication of recent deployments, helping you determine if a deployment has increased response times for end-users, altered your application's memory/CPU footprint, or introduced any other performance-related changes.
+
+To enable deployment tracking ability, run the [**Telemetry Collector**](https://app.logz.io/#/dashboard/send-your-data/agent/new) on your Kubernetes clusters. You can also activate this process **manually** by installing [Logz.io Kubernetes events Helm chart](https://app.logz.io/#/dashboard/integrations/Kubernetes:~:text=user%20guide.-,Send%20your%20deploy%20events%20logs,-This%20integration%20sends) and sending Kubernetes deploy events logs.
+
+Once enabled, the graphs will include a deployment marker, marked by a dotted vertical line.
+
+You can view additional deployment data by clicking on the line. This data includes the deployment time, the associated service and environment, and a quick link to view the commit in your logs.
+
+Click **Go to commit** to access and view your own code related to this deployment, allowing you to probe deeper into the relevant data.
+
+![deployment menu](https://dytvr9ot2sszz.cloudfront.net/logz-docs/k360/k360-deploy.png)
+
+
 ### Traces tab
 {:.no_toc}
 

From 5ac5a12fcbc634628b28e8160ecbbf7dd7de646b Mon Sep 17 00:00:00 2001
From: Simplychee <simplychee@gmail.com>
Date: Mon, 30 Oct 2023 11:48:59 +0200
Subject: [PATCH 05/11] go to commit

---
 _source/user-guide/distributed-tracing/services.md | 3 +++
 _source/user-guide/k360/index.md                   | 6 +++++-
 2 files changed, 8 insertions(+), 1 deletion(-)

diff --git a/_source/user-guide/distributed-tracing/services.md b/_source/user-guide/distributed-tracing/services.md
index 64d070098..76c3d3aff 100644
--- a/_source/user-guide/distributed-tracing/services.md
+++ b/_source/user-guide/distributed-tracing/services.md
@@ -85,6 +85,9 @@ You can view additional deployment data by clicking on the line. This data inclu
 
 Click **Go to commit** to access and view your own code related to this deployment, allowing you to probe deeper into the relevant data.
 
+The **Go to Commit** link is populated by adding an annotation **in your app**. Add the following annotation to the metadata of each resource its versioning you'd like to track. The URL structure is `https://github.com/<account>/<repository>/commit/<commit-hash>`. For example: `https://github.com/logzio/logzio-k8s-events/commit/069c75c95caeca58dd0776405bb8dfb4eed3acb2`.
+{:.info-box.note}
+
 
 <!-- ### Logs overview
 
diff --git a/_source/user-guide/k360/index.md b/_source/user-guide/k360/index.md
index 539b49d86..0c774e77d 100644
--- a/_source/user-guide/k360/index.md
+++ b/_source/user-guide/k360/index.md
@@ -160,7 +160,7 @@ The **Metrics** tab presents useful data in graph form. These graphs provides a
 
 You can enrich your Kubernetes 360 graphs by adding an indication of recent deployments, helping you determine if a deployment has increased response times for end-users, altered your application's memory/CPU footprint, or introduced any other performance-related changes.
 
-To enable deployment tracking ability, run the [**Telemetry Collector**](https://app.logz.io/#/dashboard/send-your-data/agent/new) on your Kubernetes clusters. You can also activate this process **manually** by installing [Logz.io Kubernetes events Helm chart](https://app.logz.io/#/dashboard/integrations/Kubernetes:~:text=user%20guide.-,Send%20your%20deploy%20events%20logs,-This%20integration%20sends) and sending Kubernetes deploy events logs.
+To enable deployment tracking ability, run the [**Telemetry Collector**](https://app.logz.io/#/dashboard/send-your-data/agent/new) on your Kubernetes clusters. You can also activate this process **manually** by installing [Logz.io Kubernetes events Helm chart](https://app.logz.io/#/dashboard/integrations/Kubernetes:~:text=user%20guide.-,Send%20your%20deploy%20events%20logs,-This%20integration%20sends). 
 
 Once enabled, the graphs will include a deployment marker, marked by a dotted vertical line.
 
@@ -168,6 +168,10 @@ You can view additional deployment data by clicking on the line. This data inclu
 
 Click **Go to commit** to access and view your own code related to this deployment, allowing you to probe deeper into the relevant data.
 
+
+The **Go to Commit** link is populated by adding an annotation **in your app**. Add the following annotation to the metadata of each resource its versioning you'd like to track. The URL structure is `https://github.com/<account>/<repository>/commit/<commit-hash>`. For example: `https://github.com/logzio/logzio-k8s-events/commit/069c75c95caeca58dd0776405bb8dfb4eed3acb2`.
+{:.info-box.note}
+
 ![deployment menu](https://dytvr9ot2sszz.cloudfront.net/logz-docs/k360/k360-deploy.png)
 
 

From 055581a481302eac89a0de9bf6214e44ad55c6b3 Mon Sep 17 00:00:00 2001
From: Simplychee <simplychee@gmail.com>
Date: Mon, 30 Oct 2023 12:02:00 +0200
Subject: [PATCH 06/11] break?

---
 _source/user-guide/distributed-tracing/services.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/_source/user-guide/distributed-tracing/services.md b/_source/user-guide/distributed-tracing/services.md
index 76c3d3aff..a1748efd4 100644
--- a/_source/user-guide/distributed-tracing/services.md
+++ b/_source/user-guide/distributed-tracing/services.md
@@ -85,7 +85,7 @@ You can view additional deployment data by clicking on the line. This data inclu
 
 Click **Go to commit** to access and view your own code related to this deployment, allowing you to probe deeper into the relevant data.
 
-The **Go to Commit** link is populated by adding an annotation **in your app**. Add the following annotation to the metadata of each resource its versioning you'd like to track. The URL structure is `https://github.com/<account>/<repository>/commit/<commit-hash>`. For example: `https://github.com/logzio/logzio-k8s-events/commit/069c75c95caeca58dd0776405bb8dfb4eed3acb2`.
+The **Go to Commit** link is populated by adding an annotation **in your app**. Add the following annotation to the metadata of each resource its versioning you'd like to track. The URL structure is `https://github.com/<account>/<repository>/commit/<commit-hash>`. </br> For example: `https://github.com/logzio/logzio-k8s-events/commit/069c75c95caeca58dd0776405bb8dfb4eed3acb2`.
 {:.info-box.note}
 
 

From 1e3a557e503d605fa7ed674a21a933748ad463d8 Mon Sep 17 00:00:00 2001
From: Simplychee <simplychee@gmail.com>
Date: Mon, 30 Oct 2023 12:08:44 +0200
Subject: [PATCH 07/11] no break

---
 _source/user-guide/distributed-tracing/services.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/_source/user-guide/distributed-tracing/services.md b/_source/user-guide/distributed-tracing/services.md
index a1748efd4..4bda750cd 100644
--- a/_source/user-guide/distributed-tracing/services.md
+++ b/_source/user-guide/distributed-tracing/services.md
@@ -85,7 +85,7 @@ You can view additional deployment data by clicking on the line. This data inclu
 
 Click **Go to commit** to access and view your own code related to this deployment, allowing you to probe deeper into the relevant data.
 
-The **Go to Commit** link is populated by adding an annotation **in your app**. Add the following annotation to the metadata of each resource its versioning you'd like to track. The URL structure is `https://github.com/<account>/<repository>/commit/<commit-hash>`. </br> For example: `https://github.com/logzio/logzio-k8s-events/commit/069c75c95caeca58dd0776405bb8dfb4eed3acb2`.
+The **Go to Commit** link is populated by adding an annotation **in your app**. Add the following annotation to the metadata of each resource its versioning you'd like to track. The URL structure is https://github.com/`<account>`/`<repository>`/commit/`<commit-hash>`. For example: `https://github.com/logzio/logzio-k8s-events/commit/069c75c95caeca58dd0776405bb8dfb4eed3acb2`.
 {:.info-box.note}
 
 

From 7662ae2702069f7b68f793695e2776d3c3258913 Mon Sep 17 00:00:00 2001
From: Simplychee <simplychee@gmail.com>
Date: Mon, 30 Oct 2023 12:15:00 +0200
Subject: [PATCH 08/11] updates

---
 _source/user-guide/distributed-tracing/services.md | 2 +-
 _source/user-guide/k360/index.md                   | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/_source/user-guide/distributed-tracing/services.md b/_source/user-guide/distributed-tracing/services.md
index 4bda750cd..2366114b9 100644
--- a/_source/user-guide/distributed-tracing/services.md
+++ b/_source/user-guide/distributed-tracing/services.md
@@ -85,7 +85,7 @@ You can view additional deployment data by clicking on the line. This data inclu
 
 Click **Go to commit** to access and view your own code related to this deployment, allowing you to probe deeper into the relevant data.
 
-The **Go to Commit** link is populated by adding an annotation **in your app**. Add the following annotation to the metadata of each resource its versioning you'd like to track. The URL structure is https://github.com/`<account>`/`<repository>`/commit/`<commit-hash>`. For example: `https://github.com/logzio/logzio-k8s-events/commit/069c75c95caeca58dd0776405bb8dfb4eed3acb2`.
+To activate the **Go to Commit** button, go to **your app or service** and add the following annotation to the metadata of each resource's versioning you want to track: https://github.com/`<account>`/`<repository>`/commit/`<commit-hash>`. For example: `https://github.com/logzio/logzio-k8s-events/commit/069c75c95caeca58dd0776405bb8dfb4eed3acb2`.
 {:.info-box.note}
 
 
diff --git a/_source/user-guide/k360/index.md b/_source/user-guide/k360/index.md
index 0c774e77d..acb26db0c 100644
--- a/_source/user-guide/k360/index.md
+++ b/_source/user-guide/k360/index.md
@@ -169,7 +169,7 @@ You can view additional deployment data by clicking on the line. This data inclu
 Click **Go to commit** to access and view your own code related to this deployment, allowing you to probe deeper into the relevant data.
 
 
-The **Go to Commit** link is populated by adding an annotation **in your app**. Add the following annotation to the metadata of each resource its versioning you'd like to track. The URL structure is `https://github.com/<account>/<repository>/commit/<commit-hash>`. For example: `https://github.com/logzio/logzio-k8s-events/commit/069c75c95caeca58dd0776405bb8dfb4eed3acb2`.
+To activate the **Go to Commit** button, go to **your app or service** and add the following annotation to the metadata of each resource's versioning you want to track: https://github.com/`<account>`/`<repository>`/commit/`<commit-hash>`. For example: `https://github.com/logzio/logzio-k8s-events/commit/069c75c95caeca58dd0776405bb8dfb4eed3acb2`.
 {:.info-box.note}
 
 ![deployment menu](https://dytvr9ot2sszz.cloudfront.net/logz-docs/k360/k360-deploy.png)

From eb23386956331fba960b24edad67eea96992883d Mon Sep 17 00:00:00 2001
From: Simplychee <simplychee@gmail.com>
Date: Mon, 30 Oct 2023 12:34:46 +0200
Subject: [PATCH 09/11] name

---
 _source/user-guide/distributed-tracing/services.md | 2 +-
 _source/user-guide/k360/index.md                   | 5 ++++-
 2 files changed, 5 insertions(+), 2 deletions(-)

diff --git a/_source/user-guide/distributed-tracing/services.md b/_source/user-guide/distributed-tracing/services.md
index 2366114b9..edf08d4aa 100644
--- a/_source/user-guide/distributed-tracing/services.md
+++ b/_source/user-guide/distributed-tracing/services.md
@@ -85,7 +85,7 @@ You can view additional deployment data by clicking on the line. This data inclu
 
 Click **Go to commit** to access and view your own code related to this deployment, allowing you to probe deeper into the relevant data.
 
-To activate the **Go to Commit** button, go to **your app or service** and add the following annotation to the metadata of each resource's versioning you want to track: https://github.com/`<account>`/`<repository>`/commit/`<commit-hash>`. For example: `https://github.com/logzio/logzio-k8s-events/commit/069c75c95caeca58dd0776405bb8dfb4eed3acb2`.
+To activate the **Go to Commit** button, go to **your app or service** and add the following annotation to the metadata of each resource's versioning you want to track: `logzio/commit_url: ""`, and the URL structure should be https://github.com/`<account>`/`<repository>`/commit/`<commit-hash>`. For example: `https://github.com/logzio/logzio-k8s-events/commit/069c75c95caeca58dd0776405bb8dfb4eed3acb2`. [Learn more](https://github.com/logzio/logzio-helm/tree/master/charts/logzio-k8s-events#deployment-events-versioning).
 {:.info-box.note}
 
 
diff --git a/_source/user-guide/k360/index.md b/_source/user-guide/k360/index.md
index acb26db0c..ad60c01fb 100644
--- a/_source/user-guide/k360/index.md
+++ b/_source/user-guide/k360/index.md
@@ -169,9 +169,12 @@ You can view additional deployment data by clicking on the line. This data inclu
 Click **Go to commit** to access and view your own code related to this deployment, allowing you to probe deeper into the relevant data.
 
 
-To activate the **Go to Commit** button, go to **your app or service** and add the following annotation to the metadata of each resource's versioning you want to track: https://github.com/`<account>`/`<repository>`/commit/`<commit-hash>`. For example: `https://github.com/logzio/logzio-k8s-events/commit/069c75c95caeca58dd0776405bb8dfb4eed3acb2`.
+To activate the **Go to Commit** button, go to **your app or service** and add the following annotation to the metadata of each resource's versioning you want to track: `logzio/commit_url: ""`, and the URL structure should be https://github.com/`<account>`/`<repository>`/commit/`<commit-hash>`. For example: `https://github.com/logzio/logzio-k8s-events/commit/069c75c95caeca58dd0776405bb8dfb4eed3acb2`. [Learn more](https://github.com/logzio/logzio-helm/tree/master/charts/logzio-k8s-events#deployment-events-versioning).
 {:.info-box.note}
 
+
+logzio/commit_url: ""
+
 ![deployment menu](https://dytvr9ot2sszz.cloudfront.net/logz-docs/k360/k360-deploy.png)
 
 

From 0ff1245111ede926a75281c15e5299dd27a75327 Mon Sep 17 00:00:00 2001
From: Simplychee <simplychee@gmail.com>
Date: Mon, 30 Oct 2023 12:47:18 +0200
Subject: [PATCH 10/11] url

---
 _source/user-guide/distributed-tracing/services.md | 2 +-
 _source/user-guide/k360/index.md                   | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/_source/user-guide/distributed-tracing/services.md b/_source/user-guide/distributed-tracing/services.md
index edf08d4aa..88752193e 100644
--- a/_source/user-guide/distributed-tracing/services.md
+++ b/_source/user-guide/distributed-tracing/services.md
@@ -85,7 +85,7 @@ You can view additional deployment data by clicking on the line. This data inclu
 
 Click **Go to commit** to access and view your own code related to this deployment, allowing you to probe deeper into the relevant data.
 
-To activate the **Go to Commit** button, go to **your app or service** and add the following annotation to the metadata of each resource's versioning you want to track: `logzio/commit_url: ""`, and the URL structure should be https://github.com/`<account>`/`<repository>`/commit/`<commit-hash>`. For example: `https://github.com/logzio/logzio-k8s-events/commit/069c75c95caeca58dd0776405bb8dfb4eed3acb2`. [Learn more](https://github.com/logzio/logzio-helm/tree/master/charts/logzio-k8s-events#deployment-events-versioning).
+To activate the **Go to Commit** button, go to **your app or service** and add the following annotation to the metadata of each resource's versioning you want to track: `logzio/commit_url: ""`, and the URL structure should be https://github.com/`<account>`/`<repository>`/commit/`<commit-hash>`. [Learn more](https://github.com/logzio/logzio-helm/tree/master/charts/logzio-k8s-events#deployment-events-versioning).
 {:.info-box.note}
 
 
diff --git a/_source/user-guide/k360/index.md b/_source/user-guide/k360/index.md
index ad60c01fb..8fa71d242 100644
--- a/_source/user-guide/k360/index.md
+++ b/_source/user-guide/k360/index.md
@@ -169,7 +169,7 @@ You can view additional deployment data by clicking on the line. This data inclu
 Click **Go to commit** to access and view your own code related to this deployment, allowing you to probe deeper into the relevant data.
 
 
-To activate the **Go to Commit** button, go to **your app or service** and add the following annotation to the metadata of each resource's versioning you want to track: `logzio/commit_url: ""`, and the URL structure should be https://github.com/`<account>`/`<repository>`/commit/`<commit-hash>`. For example: `https://github.com/logzio/logzio-k8s-events/commit/069c75c95caeca58dd0776405bb8dfb4eed3acb2`. [Learn more](https://github.com/logzio/logzio-helm/tree/master/charts/logzio-k8s-events#deployment-events-versioning).
+To activate the **Go to Commit** button, go to **your app or service** and add the following annotation to the metadata of each resource's versioning you want to track: `logzio/commit_url: ""`, and the URL structure should be https://github.com/`<account>`/`<repository>`/commit/`<commit-hash>`. [Learn more](https://github.com/logzio/logzio-helm/tree/master/charts/logzio-k8s-events#deployment-events-versioning).
 {:.info-box.note}
 
 

From f1f7a1b525723c8d9750e22913c5589de54b077d Mon Sep 17 00:00:00 2001
From: Simplychee <simplychee@gmail.com>
Date: Mon, 30 Oct 2023 12:48:51 +0200
Subject: [PATCH 11/11] we need to switch

---
 _source/user-guide/distributed-tracing/services.md | 2 +-
 _source/user-guide/k360/index.md                   | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/_source/user-guide/distributed-tracing/services.md b/_source/user-guide/distributed-tracing/services.md
index 88752193e..62934a54b 100644
--- a/_source/user-guide/distributed-tracing/services.md
+++ b/_source/user-guide/distributed-tracing/services.md
@@ -85,7 +85,7 @@ You can view additional deployment data by clicking on the line. This data inclu
 
 Click **Go to commit** to access and view your own code related to this deployment, allowing you to probe deeper into the relevant data.
 
-To activate the **Go to Commit** button, go to **your app or service** and add the following annotation to the metadata of each resource's versioning you want to track: `logzio/commit_url: ""`, and the URL structure should be https://github.com/`<account>`/`<repository>`/commit/`<commit-hash>`. [Learn more](https://github.com/logzio/logzio-helm/tree/master/charts/logzio-k8s-events#deployment-events-versioning).
+To activate the **Go to Commit** button, go to **your app or service** and add the following annotation to the metadata of each resource's versioning you want to track: `logzio/commit_url: ""`, and the URL structure should be: "https://github.com/`<account>`/`<repository>`/commit/`<commit-hash>`". [Learn more](https://github.com/logzio/logzio-helm/tree/master/charts/logzio-k8s-events#deployment-events-versioning).
 {:.info-box.note}
 
 
diff --git a/_source/user-guide/k360/index.md b/_source/user-guide/k360/index.md
index 8fa71d242..0f4a643c4 100644
--- a/_source/user-guide/k360/index.md
+++ b/_source/user-guide/k360/index.md
@@ -169,7 +169,7 @@ You can view additional deployment data by clicking on the line. This data inclu
 Click **Go to commit** to access and view your own code related to this deployment, allowing you to probe deeper into the relevant data.
 
 
-To activate the **Go to Commit** button, go to **your app or service** and add the following annotation to the metadata of each resource's versioning you want to track: `logzio/commit_url: ""`, and the URL structure should be https://github.com/`<account>`/`<repository>`/commit/`<commit-hash>`. [Learn more](https://github.com/logzio/logzio-helm/tree/master/charts/logzio-k8s-events#deployment-events-versioning).
+To activate the **Go to Commit** button, go to **your app or service** and add the following annotation to the metadata of each resource's versioning you want to track: `logzio/commit_url: ""`, and the URL structure should be: "https://github.com/`<account>`/`<repository>`/commit/`<commit-hash>`". [Learn more](https://github.com/logzio/logzio-helm/tree/master/charts/logzio-k8s-events#deployment-events-versioning).
 {:.info-box.note}