From 31915b4989162a71b27484eb833beeb3cd869560 Mon Sep 17 00:00:00 2001
From: Moritz Sanft <58110325+msanft@users.noreply.github.com>
Date: Mon, 5 Feb 2024 14:04:24 +0100
Subject: [PATCH] docs: fix typo

---
 docs/docs/workflows/troubleshooting.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/docs/workflows/troubleshooting.md b/docs/docs/workflows/troubleshooting.md
index 701bfe84d..bc0da6508 100644
--- a/docs/docs/workflows/troubleshooting.md
+++ b/docs/docs/workflows/troubleshooting.md
@@ -100,7 +100,7 @@ check if the encountered [issue is known](https://github.com/edgelesssys/constel
 To get started on diagnosing issues with Constellation, it often is helpful to collect logs from nodes, pods or other resources in the cluster. Most logs are available through Kubernetes' standard
 [logging interfaces](https://kubernetes.io/docs/concepts/cluster-administration/logging/).
 
-To debug issues occuring at boot time of the nodes, one can use the serial console interface of the CSP.
+To debug issues occurring at boot time of the nodes, one can use the serial console interface of the CSP.
 
 Apart from that, Constellation also offers further [observability integrations](../architecture/observability.md).