From c0be3f2dbfd15087c60dadf2e746bf3a0b44f42b Mon Sep 17 00:00:00 2001
From: Srinadh Penugonda <55261736+spenugondaa@users.noreply.github.com>
Date: Sun, 14 Nov 2021 08:31:42 -0800
Subject: [PATCH] Update event-alarm-framework.md

---
 doc/event-alarm-framework/event-alarm-framework.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/event-alarm-framework/event-alarm-framework.md b/doc/event-alarm-framework/event-alarm-framework.md
index fee86b7425..87b10e9493 100644
--- a/doc/event-alarm-framework/event-alarm-framework.md
+++ b/doc/event-alarm-framework/event-alarm-framework.md
@@ -134,7 +134,7 @@ In addition to the above tables, the framework maintains various statisitcs.
 
 As mentioned above, each event has an important characteristic: severity. SONiC uses following severities for events and alarms as defined in opeconfig alarm yang.
 
-- CRITICAL : Requires immediate action. An critical event may trigger if one or more hardware components fail, or one or more hardware components exceed temperature thresholds.
+- CRITICAL : Requires immediate action. A critical event may trigger if one or more hardware components fail, or one or more hardware components exceed temperature thresholds.
   ( maps to log-alert )
 - MAJOR : Requires escalation or notification. For example, a major alarm may trigger if an interface failure occurs, such as a port channel being down.
   ( maps to log-critical )