From 18a48c16a0b1feb3e4111a213716070a74d86d7a Mon Sep 17 00:00:00 2001
From: AntoinePrv <AntoinePrv@users.noreply.github.com>
Date: Mon, 13 Nov 2023 18:40:02 +0100
Subject: [PATCH] Fix sphinx warnings

---
 docs/source/user_guide/troubleshooting.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/source/user_guide/troubleshooting.rst b/docs/source/user_guide/troubleshooting.rst
index ac4f2a3abf..3e3a900b9c 100644
--- a/docs/source/user_guide/troubleshooting.rst
+++ b/docs/source/user_guide/troubleshooting.rst
@@ -113,7 +113,7 @@ Windows API historically supports paths up to 260 characters. While it's now pos
 
 
 Long paths support has to be activated
-**************************************
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 source: Robocorp `troubleshooting documentation <https://robocorp.com/docs/troubleshooting/windows-long-path>`_
 
@@ -131,7 +131,7 @@ If the problem persists after those steps, try the following:
 
 
 cmd.exe does not support calls to long prefixes
-***********************************************
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 While ``cmd.exe`` shell support long paths prefixing for directory operations such as ``dir``, it doesn't allow to call an executable or a batch file located at a long path prefix.