From 29441fd804c0bf37d7031dae3a6db570737c698d Mon Sep 17 00:00:00 2001 From: leynos Date: Tue, 14 Jul 2026 03:19:07 +0200 Subject: [PATCH 1/2] Use plaintext for prose fence blocks (#161) Replace every remaining `text` fence in project documentation with `plaintext`, which is the documented identifier for non-code output. Correct the existing `artefact` spelling in the design document so the Markdown quality gate passes under the configured en-GB policy. --- docs/users-guide.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/users-guide.md b/docs/users-guide.md index c077b8f7..e46a1f7f 100644 --- a/docs/users-guide.md +++ b/docs/users-guide.md @@ -118,7 +118,7 @@ all git-tracked `Cargo.lock` files are fresh under `--locked` mode. If any lockfile is stale — for example after a `lading bump` that regenerated a nested workspace lockfile — the command exits with code 1 and prints a repair command: -```text +```plaintext Tracked Cargo.lock files are stale after manifest version changes. Run the following to repair: cargo generate-lockfile --manifest-path /Cargo.toml @@ -162,7 +162,7 @@ even in dry-run mode. When two or more workspace crates are released together for the first time and one depends on another at a version that is not yet on crates.io, `cargo package` will fail with an error similar to: -```text +```plaintext error: failed to prepare local package for uploading Caused by: @@ -292,7 +292,7 @@ inconsistent: the manifests carry the new version but the affected lockfiles do not. When several lockfiles are regenerated, `lading` raises one aggregated error that lists every failed manifest with the exact repair command to run: -```text +```plaintext Cargo lockfile regeneration failed for 2 manifest(s). Manifests already carry the new version, so the workspace is inconsistent until each lockfile below is repaired: - Cargo lockfile regeneration failed for crates/a/Cargo.toml with exit code 101: cargo update --workspace --manifest-path crates/a/Cargo.toml From cff9ccc3bbaaf8ec6469f574f248feece66cb742 Mon Sep 17 00:00:00 2001 From: leynos Date: Tue, 21 Jul 2026 23:12:30 +0200 Subject: [PATCH 2/2] Refresh generated spelling configuration Synchronize the generated Oxford-spelling policy with the current authority. --- typos.toml | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/typos.toml b/typos.toml index 8c5efed1..3fb9200e 100644 --- a/typos.toml +++ b/typos.toml @@ -1699,6 +1699,24 @@ extend-ignore-re = [ "pluralizers" = "pluralizers" "pluralizes" = "pluralizes" "pluralizing" = "pluralizing" +"polymerisable" = "polymerizable" +"polymerisation" = "polymerization" +"polymerisations" = "polymerizations" +"polymerise" = "polymerize" +"polymerised" = "polymerized" +"polymeriser" = "polymerizer" +"polymerisers" = "polymerizers" +"polymerises" = "polymerizes" +"polymerising" = "polymerizing" +"polymerizable" = "polymerizable" +"polymerization" = "polymerization" +"polymerizations" = "polymerizations" +"polymerize" = "polymerize" +"polymerized" = "polymerized" +"polymerizer" = "polymerizer" +"polymerizers" = "polymerizers" +"polymerizes" = "polymerizes" +"polymerizing" = "polymerizing" "popularisable" = "popularizable" "popularisation" = "popularization" "popularisations" = "popularizations"