Skip to content

Commit ca5a061

Browse files
hunterlxtBusyJay
andauthored
Apply suggestions from code review
Co-authored-by: Jay <[email protected]>
1 parent f8ad795 commit ca5a061

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

src/lib.rs

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -79,7 +79,7 @@
7979
//! Fail points are managed by the registry which stores a map of the fail points
8080
//! names and actions. The registry is divided into local and global.
8181
//!
82-
//! When you don't specifically declare a registry, the global registry will be used
82+
//! When you don't declare a registry explicitly, the global registry will be used
8383
//! by default. You can pass the setting from environment variables to the global registry.
8484
//! Sometimes you need different tests to use different registries and don’t want their
8585
//! behavior to interfere with each other. You can create a local registry and then register
@@ -110,7 +110,7 @@
110110
//! }
111111
//! ```
112112
//!
113-
//! It should be noted that the local registry will will overwrite the global registry
113+
//! It should be noted that the local registry will overwrite the global registry
114114
//! if you register the current thread here. This means that the current thread can only
115115
//! use the fail points configuration of the local registry after registration.
116116
//!
@@ -133,7 +133,7 @@
133133
//! }
134134
//! println!("Global registry: {:?}", fail::list());
135135
//! ```
136-
//! When the example is run normally it prints out the contents of the registry used
136+
//! The example will print out the contents of the registry used
137137
//! at the time.
138138
//!
139139
//! ```sh

0 commit comments

Comments
 (0)