Apply suggestions from code review

Co-authored-by: RD WebDesign <[email protected]>
Signed-off-by: Dominik <[email protected]>

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

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 )
 		{