From 350cbb2a0b2ca673c6c72df6bf4dd1ab562b2ade Mon Sep 17 00:00:00 2001
From: Théo de la Hogue
Date: Thu, 25 Apr 2024 21:04:19 +0200
Subject: Improving documentation.

---
 .../gaze_analysis_pipeline/timestamped_gaze_positions_edition.md     | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

(limited to 'docs/user_guide/gaze_analysis_pipeline/timestamped_gaze_positions_edition.md')

diff --git a/docs/user_guide/gaze_analysis_pipeline/timestamped_gaze_positions_edition.md b/docs/user_guide/gaze_analysis_pipeline/timestamped_gaze_positions_edition.md
index 022899e..026d287 100644
--- a/docs/user_guide/gaze_analysis_pipeline/timestamped_gaze_positions_edition.md
+++ b/docs/user_guide/gaze_analysis_pipeline/timestamped_gaze_positions_edition.md
@@ -66,9 +66,10 @@ start_time = time.time()
 	Timestamps can either be integers or floats, seconds, milliseconds or what ever you need. The only concern is that all time values used in further configurations have to be in the same unit.
 
 <!--
-!!! Note "Eyetracker connectors"
+!!! note "Eyetracker connectors"
 
 	[Read the use cases section to discover examples using specific eyetrackers](./user_cases/introduction.md).
 !-->
 
-Now we have timestamped gaze positions at expected format, let's see how to analyze them.
\ No newline at end of file
+!!! note ""
+	Now we have timestamped gaze positions at expected format, read the next chapter to start learning [how to analyze them](./configuration_and_execution.md).
\ No newline at end of file
-- 
cgit v1.1