Auto merge of #14229 - tianyeyouyou:chore, r=epage

chore: remove duplicate words

remove duplicate words to enhance readability.

Author: bors

crates/cargo-util-schemas/src/manifest/mod.rs

@@ -285,7 +285,7 @@ impl TomlPackage {
 #[derive(Serialize, Copy, Clone, Debug)]
 #[serde(untagged)]
 pub enum InheritableField<T> {
-    /// The type that that is used when not inheriting from a workspace.
+    /// The type that is used when not inheriting from a workspace.
     Value(T),
     /// The type when inheriting from a workspace.
     Inherit(TomlInheritedField),
@@ -582,7 +582,7 @@ impl From<WorkspaceValue> for bool {
 #[derive(Serialize, Clone, Debug)]
 #[serde(untagged)]
 pub enum InheritableDependency {
-    /// The type that that is used when not inheriting from a workspace.
+    /// The type that is used when not inheriting from a workspace.
     Value(TomlDependency),
     /// The type when inheriting from a workspace.
     Inherit(TomlInheritedDependency),

crates/mdman/Cargo.toml

@@ -3,7 +3,7 @@ name = "mdman"
 version = "0.0.0"
 edition.workspace = true
 license.workspace = true
-description = "Creates a man page page from markdown."
+description = "Creates a man page from markdown."
 publish = false
 
 [dependencies]

src/cargo/core/registry.rs

@@ -237,7 +237,7 @@ impl<'gctx> PackageRegistry<'gctx> {
             }
 
             // If the previous source has the same precise version as we do,
-            // then we're done, otherwise we need to need to move forward
+            // then we're done, otherwise we need to move forward
             // updating this source.
             Some((previous, _)) => {
                 if previous.has_same_precise_as(namespace) {

src/doc/contrib/src/process/unstable.md

@@ -77,7 +77,7 @@ and give feedback begins:
   - This could be on the tracking issue or in a dedicated issue for feedback
   - e.g. [workspace inheritance testing notes]
 2. Call for testing
-  - In the RFC, link to the test instructions and label it with with `call-for-testing` to be picked up by [This Week in Rust]
+  - In the RFC, link to the test instructions and label it with `call-for-testing` to be picked up by [This Week in Rust]
     - If there is not an RFC, a pull request should be made to the [TWiR repo]
       adding the feature to the `Call for Testing` section ([example]).
   - Post on various Rust communities ([rust subreddit], [users], [internals], etc)

tests/testsuite/git_shallow.rs

@@ -443,7 +443,7 @@ fn gitoxide_shallow_clone_followed_by_non_shallow_update() -> anyhow::Result<()>
 
     assert_eq!(
         max_history_depth, 3,
-        "we see the previous shallow checkout as well as new new unshallow one"
+        "we see the previous shallow checkout as well as new unshallow one"
     );
 
     Ok(())