From cca2015920f20f7a8f65db95e7024990c766f265 Mon Sep 17 00:00:00 2001 From: Quentin Gliech Date: Thu, 4 Dec 2025 16:32:13 +0100 Subject: [PATCH] Fix typos Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- crates/storage-pg/src/lib.rs | 2 +- docs/development/database.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/crates/storage-pg/src/lib.rs b/crates/storage-pg/src/lib.rs index b133e83a4..ea2029475 100644 --- a/crates/storage-pg/src/lib.rs +++ b/crates/storage-pg/src/lib.rs @@ -324,7 +324,7 @@ async fn migration_table_exists(conn: &mut PgConnection) -> Result Result<(), MigrateError> { - // Get the database name and use it to derivate an advisory lock key. This + // Get the database name and use it to derive an advisory lock key. This // is the same lock key used by SQLx default migrator, so that it works even // with older versions of MAS, and when running through `cargo sqlx migrate run` let database_name = sqlx::query_scalar!(r#"SELECT current_database() as "current_database!""#) diff --git a/docs/development/database.md b/docs/development/database.md index 91bd7f9fa..43c2b33fe 100644 --- a/docs/development/database.md +++ b/docs/development/database.md @@ -53,7 +53,7 @@ Note that migrations are embedded in the final binary and can be run from the se ### Removing migrations -For various reason, we may want to delete migrations. +For various reasons, we may want to delete migrations. In case we do, we *must* declare that migration version as it is fine to be missing. This is because on startup, MAS will validate that all the applied migrations are known, and warn if some are missing.