From 9566dc49b694a32e68f664eedda00dde2031b810 Mon Sep 17 00:00:00 2001 From: Olivier 'reivilibre Date: Thu, 6 Nov 2025 09:20:20 +0000 Subject: [PATCH 1/2] Fix broken link in rustdoc --- crates/context/src/fmt.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/crates/context/src/fmt.rs b/crates/context/src/fmt.rs index f4c4981e1..47e72fcae 100644 --- a/crates/context/src/fmt.rs +++ b/crates/context/src/fmt.rs @@ -18,7 +18,7 @@ use tracing_subscriber::{ use crate::LogContext; -/// An event formatter usable by the [`tracing-subscriber`] crate, which +/// An event formatter usable by the [`tracing_subscriber`] crate, which /// includes the log context and the OTEL trace ID. #[derive(Debug, Default)] pub struct EventFormatter; From eda3eecc3ec24dae75250d66c8512427ad655f61 Mon Sep 17 00:00:00 2001 From: Olivier 'reivilibre Date: Thu, 6 Nov 2025 10:11:22 +0000 Subject: [PATCH 2/2] Fix another broken link in the rustdocs --- crates/storage/src/lib.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/crates/storage/src/lib.rs b/crates/storage/src/lib.rs index 7a19f05ac..c5d5d0b26 100644 --- a/crates/storage/src/lib.rs +++ b/crates/storage/src/lib.rs @@ -20,7 +20,7 @@ //! To define a new repository, you have to: //! 1. Define a new (async) repository trait, with the methods you need //! 2. Write an implementation of this trait for each storage backend you want -//! (currently only for [`mas-storage-pg`]) +//! (currently only for `mas-storage-pg`) //! 3. Make it accessible via the [`RepositoryAccess`] trait //! //! The repository trait definition should look like this: