From fdee149695c0346bed4520f45f8f299c780aa3af Mon Sep 17 00:00:00 2001
From: sn99 <42946112+sn99@users.noreply.github.com>
Date: Fri, 15 Mar 2024 09:57:54 +0530
Subject: [PATCH] Update README.md

---
 README.md | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/README.md b/README.md
index 4812583..4b37dfb 100644
--- a/README.md
+++ b/README.md
@@ -165,9 +165,6 @@ non-bootable.
     `nobarrier` option is safe as long you didn't expect sudden powerloss happens or has battery-backed.
    
     _On a device with a volatile battery-backed write-back cache, the nobarrier option will not lead to filesystem corruption as the pending blocks are supposed to make it to the permanent storage._ [man 5 btrfs](https://btrfs.readthedocs.io/en/latest/btrfs-man5.html)
-    
-On a device with a volatile battery-backed write-back cache, the nobarrier option will not lead to filesystem corruption as the pending blocks are supposed to make it to the permanent storage.
-
 
 2. `sudo systemctl daemon-reload`