From 0544f83225613ad718b2fb51e4a3009041373d37 Mon Sep 17 00:00:00 2001
From: revital <revital@allegro.ai>
Date: Mon, 17 Mar 2025 13:42:06 +0200
Subject: [PATCH] Edits

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

diff --git a/docs/getting_started/clearml_agent_scheduling.md b/docs/getting_started/clearml_agent_scheduling.md
index ed3c5948..358a72cd 100644
--- a/docs/getting_started/clearml_agent_scheduling.md
+++ b/docs/getting_started/clearml_agent_scheduling.md
@@ -82,7 +82,7 @@ Currently, these runtime properties can only be set using an ClearML REST API ca
 endpoint, as follows: 
 
 * The body of the request must contain the `worker-id`, and the runtime property to add.
-* An expiry date is optional. Use the format `"expiry":<time>`. For example,  `"expiry":86400` will set an expiry of 24 hours.
+* An expiry date is optional. Use the format `"expiry":<time>`. For example, `"expiry":86400` will set an expiry of 24 hours.
 * To delete the property, set the expiry date to zero, `"expiry":0`.
 
 For example, to force a worker on for 24 hours: