2 files changed, 7 insertions, 5 deletions

diff --git a/crates/test_utils/src/lib.rs b/crates/test_utils/src/lib.rs
index 09fc2e659..4d83af00c 100644
--- a/crates/test_utils/src/lib.rs
+++ b/crates/test_utils/src/lib.rs
@@ -113,9 +113,9 @@ pub struct FixtureEntry {
     pub text: String,
 }
 
-/// Parses text wich looks like this:
+/// Parses text which looks like this:
 ///
-///  ```notrust
+///  ```rust,ignore
 ///  //- some meta
 ///  line 1
 ///  line 2
diff --git a/crates/test_utils/src/marks.rs b/crates/test_utils/src/marks.rs
index d2a84643c..107432926 100644
--- a/crates/test_utils/src/marks.rs
+++ b/crates/test_utils/src/marks.rs
@@ -1,10 +1,10 @@
 //! This module implements manually tracked test coverage, which useful for
 //! quickly finding a test responsible for testing a particular bit of code.
 //!
-//! See https://matklad.github.io/2018/06/18/a-trick-for-test-maintenance.html
+//! See <https://matklad.github.io/2018/06/18/a-trick-for-test-maintenance.html>
 //! for details, but the TL;DR is that you write your test as
 //!
-//! ```no-run
+//! ```rust,no_run
 //! #[test]
 //! fn test_foo() {
 //!     covers!(test_foo);
@@ -13,7 +13,9 @@
 //!
 //! and in the code under test you write
 //!
-//! ```no-run
+//! ```rust,no_run
+//! # use test_utils::tested_by;
+//! # fn some_condition() -> bool { true }
 //! fn foo() {
 //!     if some_condition() {
 //!         tested_by!(test_foo);