Fix typo

Author: r4victor

docs/docs/concepts/dev-environments.md

@@ -460,7 +460,7 @@ retry:
 
 !!! info "Retry duration"
     The duration period is calculated as a run age for `no-capacity` event
-    and as a time passed since the last `interruption` and `error` for `interruption` and `error` events..
+    and as a time passed since the last `interruption` and `error` for `interruption` and `error` events.
 
 ### Inactivity duration
 

docs/docs/concepts/services.md

@@ -822,7 +822,7 @@ If one replica of a multi-replica service fails with retry enabled,
 `dstack` will resubmit only the failed replica while keeping active replicas running.
 
 !!! info "Retry duration"
-    The duration period is calculated as a run age for `no-capacity` event and as a time passed since the last `interruption` and `error` for `interruption` and `error` events..
+    The duration period is calculated as a run age for `no-capacity` event and as a time passed since the last `interruption` and `error` for `interruption` and `error` events.
 
 ### Spot policy
 

docs/docs/concepts/tasks.md

@@ -719,7 +719,7 @@ If one job of a multi-node task fails with retry enabled,
 `dstack` will stop all the jobs and resubmit the run.
 
 !!! info "Retry duration"
-    The duration period is calculated as a run age for `no-capacity` event and as a time passed since the last `interruption` and `error` for `interruption` and `error` events..
+    The duration period is calculated as a run age for `no-capacity` event and as a time passed since the last `interruption` and `error` for `interruption` and `error` events.
 
 ### Priority