fix doc warnings by remove redundant explicit links

metno · Jan 22, 2025 · d6a098d · d6a098d
1 parent 0f1f7a6
commit d6a098d
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 4 deletions.
diff --git a/src/data_switch.rs b/src/data_switch.rs
@@ -1,8 +1,8 @@
-//! Utilities for creating and using [`DataConnector`](crate::data_switch::DataConnector)s
+//! Utilities for creating and using [`DataConnector`]s
 //!
-//! Implementations of the [`DataConnector`](crate::data_switch::DataConnector)
+//! Implementations of the [`DataConnector`]
 //! trait are how ROVE accesses to data for QC. For any data source you wish ROVE to be able to pull data from, you must write an implementation of
-//! [`DataConnector`](crate::data_switch::DataConnector) for it, and load that
+//! [`DataConnector`] for it, and load that
 //! connector into a [`DataSwitch`], which you then pass to
 //! [`start_server`](crate::start_server) if using ROVE in gRPC
 //! mode, or [`Scheduler::new`](crate::Scheduler::new)

diff --git a/src/scheduler.rs b/src/scheduler.rs
@@ -57,7 +57,7 @@ impl Scheduler {
     /// Run a set of QC tests on some data
     ///
     /// `data_source` is the key identifying a connector in the
-    /// [`DataSwitch`](data_switch::DataSwitch).
+    /// [`DataSwitch`].
     /// `backing_sources` a list of keys similar to `data_source`, but data
     /// from these will only be used to QC data from `data_source` and will not
     /// themselves be QCed.