From 65dd99feae1202ed0a3a685931426daf31a1319c Mon Sep 17 00:00:00 2001
From: Sree Kuchibhotla <sreek@google.com>
Date: Thu, 6 Jul 2017 10:27:01 -0700
Subject: [PATCH] fix typos identified in code review
---
src/core/lib/iomgr/timer_manager.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/src/core/lib/iomgr/timer_manager.c b/src/core/lib/iomgr/timer_manager.c
index 35889b35dc..cb7998db97 100644
--- a/src/core/lib/iomgr/timer_manager.c
+++ b/src/core/lib/iomgr/timer_manager.c
@@ -51,7 +51,7 @@ static bool g_kicked;
// is there a thread waiting until the next timer should fire?
static bool g_has_timed_waiter;
// the deadline of the current timed waiter thread (only relevant if
-// g_has_timed_watier is true)
+// g_has_timed_waiter is true)
static gpr_timespec g_timed_waiter_deadline;
// generation counter to track which thread is waiting for the next timer
static uint64_t g_timed_waiter_generation;
@@ -137,7 +137,7 @@ static bool wait_until(gpr_timespec next) {
// If g_kicked is true at this point, it means there was a kick from the timer
// system that the timer-manager threads here missed. We cannot trust 'next'
- // here any longer (since there might be an eariler deadline). So if g_kicked
+ // here any longer (since there might be an earlier deadline). So if g_kicked
// is true at this point, we should quickly exit this and get the next
// deadline from the timer system
@@ -146,7 +146,7 @@ static bool wait_until(gpr_timespec next) {
// only until the next timer should expire. All other timers wait forever
//
// 'g_timed_waiter_generation' is a global generation counter. The idea here
- // is that the thread becoming a timed-waiter icrements and stores this
+ // is that the thread becoming a timed-waiter increments and stores this
// global counter locally in 'my_timed_waiter_generation' before going to
// sleep. After waking up, if my_timed_waiter_generation ==
// g_timed_waiter_generation, it can be sure that it was the timed_waiter
--
GitLab