From a72033023903ccb42622b28b6032b12590041b7a Mon Sep 17 00:00:00 2001 From: Dominik Date: Tue, 30 Jan 2024 19:14:50 +0100 Subject: [PATCH] Apply suggestions from code review Co-authored-by: RD WebDesign Signed-off-by: Dominik --- src/config/config.c | 2 +- src/database/query-table.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/config/config.c b/src/config/config.c index a0c4e0037..90f13e5a2 100644 --- a/src/config/config.c +++ b/src/config/config.c @@ -816,7 +816,7 @@ void initConfig(struct config *conf) // Note: We would not necessarily need to restart FTL when this setting // is changed, but we do it anyway as this ensures the database is // properly re-initialized and the new journal mode is used. As this is - // a setting that will be changed very rarely, this semms the better + // a setting that will be changed very rarely, this seems the better // compromise than adding special code that can transform the database // while being active. // The in-memory database is not affected by this setting as it uses a diff --git a/src/database/query-table.c b/src/database/query-table.c index 279cc253b..1d19250be 100644 --- a/src/database/query-table.c +++ b/src/database/query-table.c @@ -123,7 +123,7 @@ bool init_memory_database(void) // - WAL provides more concurrency as readers do not block writers and a // writer does not block readers. Reading and writing can proceed // concurrently. - // - Disk I/O operations tends to be more sequential using WAL. + // - Disk I/O operations tend to be more sequential using WAL. rc = sqlite3_exec(_memdb, "PRAGMA disk.journal_mode=WAL", NULL, NULL, NULL); if( rc != SQLITE_OK ) {