From 7a32df8f53a1969e14655f60e00467f3d8b99935 Mon Sep 17 00:00:00 2001
From: Konstantin Pereiaslov <perk11@perk11.info>
Date: Mon, 12 Feb 2024 21:25:35 +0300
Subject: [PATCH] Update README.md

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 4787760..2f2e61a 100644
--- a/README.md
+++ b/README.md
@@ -12,7 +12,7 @@ The simplest way to start using runwhenidle is just by putting it in front of th
 
 ## Example 2:
 
-    runwhenidle --start-monitor-after=10 --timeout=30 --quiet ffmpeg -i file.mp4 file.mkv
+    runwhenidle --start-monitor-after=1000 --timeout=30 --quiet ffmpeg -i file.mp4 file.mkv
 
 In this example `ffmpeg` will run for 10 seconds uninterrupted. After 10 seconds pass, 
 runwhenidle  will start monitoring user activity and pause ffmpeg  if user has been active within last 30 seconds.