From b7b076577015a6356bd387221c6ea646a14251d0 Mon Sep 17 00:00:00 2001
From: Théo de la Hogue
Date: Wed, 20 Sep 2023 09:48:15 +0200
Subject: Improving gaze analysis pipeline chapters name. Replacing pictures.
 Improving hints and examples.

---
 .../gaze_analysis_pipeline/timestamped_gaze_positions_edition.md      | 4 ++--
 1 file changed, 2 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 493471e..93d2a65 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
@@ -68,7 +68,7 @@ start_time = time.time()
 	...
 ```
 
-!!! warning
-	**ArGaze doesn't impose any time unit.** Timestamps can either be integer or float, second, millisecond or what ever you need. The only concern is that all time values used in further configurations have to be all the same unit.
+!!! warning "Free time unit"
+	Timestamps can either be integer or float, second, millisecond or what ever you need. The only concern is that all time values used in further configurations have to be all the same unit.
 
 Now we have timestamped gaze positions at expected format, let's see how to analyze them.
\ No newline at end of file
-- 
cgit v1.1