diff --git a/crates/storage/libmdbx-rs/src/environment.rs b/crates/storage/libmdbx-rs/src/environment.rs
index 218196c49e..03afb47843 100644
--- a/crates/storage/libmdbx-rs/src/environment.rs
+++ b/crates/storage/libmdbx-rs/src/environment.rs
@@ -976,7 +976,7 @@ mod tests {
         }
 
         // Insert more data in the database, so we hit the DB size limit error, and MDBX tries to
-        // kick long-lived readers and delete their static_files
+        // kick long-lived readers and delete their snapshots
         {
             let tx = env.begin_rw_txn().unwrap();
             let db = tx.open_db(None).unwrap();
diff --git a/crates/storage/libmdbx-rs/src/flags.rs b/crates/storage/libmdbx-rs/src/flags.rs
index e6b2697a85..843ae161c0 100644
--- a/crates/storage/libmdbx-rs/src/flags.rs
+++ b/crates/storage/libmdbx-rs/src/flags.rs
@@ -25,7 +25,7 @@ pub enum SyncMode {
     ///
     /// [SyncMode::UtterlyNoSync] the [SyncMode::SafeNoSync] flag disable similarly flush system
     /// buffers to disk when committing a transaction. But there is a huge difference in how
-    /// are recycled the MVCC static_files corresponding to previous "steady" transactions (see
+    /// are recycled the MVCC snapshots corresponding to previous "steady" transactions (see
     /// below).
     ///
     /// With [crate::EnvironmentKind::WriteMap] the [SyncMode::SafeNoSync] instructs MDBX to use