From 8eea17bed0d4ab9bbfa6292b0bd69a528122a93d Mon Sep 17 00:00:00 2001
From: freeze <1615081+Vicente-Cheng@users.noreply.github.com>
Date: Tue, 26 Mar 2024 17:10:32 +0800
Subject: [PATCH] Apply suggestions from code review

Co-authored-by: Kiefer Chang <1691518+bk201@users.noreply.github.com>
---
 kb/2024-01-30/the_potential_risk_with_fstrim.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/kb/2024-01-30/the_potential_risk_with_fstrim.md b/kb/2024-01-30/the_potential_risk_with_fstrim.md
index 2b92e0d7..5e33ebee 100644
--- a/kb/2024-01-30/the_potential_risk_with_fstrim.md
+++ b/kb/2024-01-30/the_potential_risk_with_fstrim.md
@@ -27,7 +27,7 @@ A consequence of the IO errors caused by fstrim is that VMs using affected Longh
 
 Although the described system behavior does not affect data integrity, it might induce panic in some users. Consider the guest Kubernetes cluster scenario. In a stuck VM, the etcd service is unavailable. The effects of this failure cascade from the Kubernetes cluster becoming unavailable to services running on the cluster becoming unavailable.
 
-## How to Confirm the FSTRIM is enabled
+## How to Confirm the fstrim is enabled
 
 ### Linux