diff --git a/content/post/kubedb-v2024.12.19/index.md b/content/post/kubedb-v2024.12.19/index.md
index ea62b5f4..94a58848 100644
--- a/content/post/kubedb-v2024.12.19/index.md
+++ b/content/post/kubedb-v2024.12.19/index.md
@@ -54,12 +54,9 @@ Archiver support has been enhanced for `MongoDBArchiver`, `MariaDBArchiver`, `My
 
 **FailedLogHistoryLimit**: FailedLogHistoryLimit defines the number of failed Logs backup that the incremental snapshot will retain for debugging purposes. It's default value is 5.
 
-You can find full spec [here](https://github.com/kubedb/apimachinery/blob/master/apis/archiver/v1alpha1/types.go#L74C1-L92C2)
+You can find full spec [here](https://github.com/kubedb/apimachinery/blob/master/apis/archiver/v1alpha1/types.go#L74C1-L92C2).
 
-So Incremental snapshots status field will store successful and failed log history according to these extra two fields. This will make easier our debugging process.
-
-We update start time and end time of continuous `oplog/wal/log` push in incremental snapshot status. From now on new fields in snapshot’s status field have been introduced.
-So the maximum `successfulLogHistoryLimit` successful `oplog/wal/log/binlog` push and maximum `failedLogHistoryLimit` failed `oplog/wal/log/binlog` push information will be stored in our incremental snapshot’s status.
+We update start time and end time of continuous oplog/wal/log/binlog push in incremental snapshot status. From now on new fields in snapshot’s status field have been introduced.  So the maximum `successfulLogHistoryLimit` successful oplog/wal/log/binlog push and maximum `failedLogHistoryLimit` failed oplog/wal/log/binlog push information will be stored in our incremental snapshot’s status.
 
 Here is a sample yaml for `MongoDBArchiver`. Changes in the field `.spec.logBackup` will be same for other archivers as well.
 ```yaml