From acac4dc7f4b47d309a4de46c395bd48bf99f6961 Mon Sep 17 00:00:00 2001
From: Binu kumar <45959932+Binu42@users.noreply.github.com>
Date: Thu, 16 Jun 2022 07:02:39 +0530
Subject: [PATCH] Update article.md

---
 1-js/06-advanced-functions/08-settimeout-setinterval/article.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/1-js/06-advanced-functions/08-settimeout-setinterval/article.md b/1-js/06-advanced-functions/08-settimeout-setinterval/article.md
index e4203f57..fa1d98cb 100644
--- a/1-js/06-advanced-functions/08-settimeout-setinterval/article.md
+++ b/1-js/06-advanced-functions/08-settimeout-setinterval/article.md
@@ -297,6 +297,6 @@ Please note that all scheduling methods do not *guarantee* the exact delay.
 For example, the in-browser timer may slow down for a lot of reasons:
 - The CPU is overloaded.
 - The browser tab is in the background mode.
-- The laptop is on battery.
+- The laptop is on battery saving mode.
 
 All that may increase the minimal timer resolution (the minimal delay) to 300ms or even 1000ms depending on the browser and OS-level performance settings.