From c65b7b2376bb3e4c38fae15a5842b7e3e90d80c2 Mon Sep 17 00:00:00 2001 From: Eric Huss Date: Thu, 13 Jun 2024 16:48:47 -0700 Subject: [PATCH] Fix some documentation misspellings --- src/doc/man/cargo-bench.md | 2 +- src/doc/man/cargo-metadata.md | 2 +- src/doc/man/cargo-vendor.md | 2 +- src/doc/man/generated_txt/cargo-bench.txt | 2 +- src/doc/man/generated_txt/cargo-metadata.txt | 2 +- src/doc/man/generated_txt/cargo-vendor.txt | 2 +- src/doc/src/commands/cargo-bench.md | 2 +- src/doc/src/commands/cargo-metadata.md | 2 +- src/doc/src/commands/cargo-vendor.md | 2 +- src/doc/src/reference/unstable.md | 2 +- src/etc/man/cargo-bench.1 | 2 +- src/etc/man/cargo-metadata.1 | 2 +- src/etc/man/cargo-vendor.1 | 2 +- 13 files changed, 13 insertions(+), 13 deletions(-) diff --git a/src/doc/man/cargo-bench.md b/src/doc/man/cargo-bench.md index 51e4ac10bd5..cd54fcee404 100644 --- a/src/doc/man/cargo-bench.md +++ b/src/doc/man/cargo-bench.md @@ -90,7 +90,7 @@ in the manifest settings. Setting examples to `bench = true` will build and run the example as a benchmark, replacing the example's `main` function with the libtest harness. -Setting targets to `bench = false` will stop them from being bencharmked by +Setting targets to `bench = false` will stop them from being benchmarked by default. Target selection options that take a target by name (such as `--example foo`) ignore the `bench` flag and will always benchmark the given target. diff --git a/src/doc/man/cargo-metadata.md b/src/doc/man/cargo-metadata.md index bb8fef077e3..f95ba7c5eec 100644 --- a/src/doc/man/cargo-metadata.md +++ b/src/doc/man/cargo-metadata.md @@ -27,7 +27,7 @@ for a Rust API for reading the metadata. Within the same output format version, the compatibility is maintained, except some scenarios. The following is a non-exhaustive list of changes that are not -considersed as incompatible: +considered as incompatible: * **Adding new fields** — New fields will be added when needed. Reserving this helps Cargo evolve without bumping the format version too often. diff --git a/src/doc/man/cargo-vendor.md b/src/doc/man/cargo-vendor.md index 5921cf26b69..8f0ea952113 100644 --- a/src/doc/man/cargo-vendor.md +++ b/src/doc/man/cargo-vendor.md @@ -25,7 +25,7 @@ Cargo treats vendored sources as read-only as it does to registry and git source If you intend to modify a crate from a remote source, use `[patch]` or a `path` dependency pointing to a local copy of that crate. Cargo will then correctly handle the crate on incremental rebuilds, -as it knowns that it is no longer a read-only dependency. +as it knows that it is no longer a read-only dependency. ## OPTIONS diff --git a/src/doc/man/generated_txt/cargo-bench.txt b/src/doc/man/generated_txt/cargo-bench.txt index aa0c4111428..ae26fae333c 100644 --- a/src/doc/man/generated_txt/cargo-bench.txt +++ b/src/doc/man/generated_txt/cargo-bench.txt @@ -124,7 +124,7 @@ OPTIONS build and run the example as a benchmark, replacing the example’s main function with the libtest harness. - Setting targets to bench = false will stop them from being bencharmked + Setting targets to bench = false will stop them from being benchmarked by default. Target selection options that take a target by name (such as --example foo) ignore the bench flag and will always benchmark the given target. diff --git a/src/doc/man/generated_txt/cargo-metadata.txt b/src/doc/man/generated_txt/cargo-metadata.txt index ce3907ffbb6..9785e005701 100644 --- a/src/doc/man/generated_txt/cargo-metadata.txt +++ b/src/doc/man/generated_txt/cargo-metadata.txt @@ -22,7 +22,7 @@ OUTPUT FORMAT Compatibility Within the same output format version, the compatibility is maintained, except some scenarios. The following is a non-exhaustive list of changes - that are not considersed as incompatible: + that are not considered as incompatible: o Adding new fields — New fields will be added when needed. Reserving this helps Cargo evolve without bumping the format version too often. diff --git a/src/doc/man/generated_txt/cargo-vendor.txt b/src/doc/man/generated_txt/cargo-vendor.txt index ab1e9a0f09b..771e75326d6 100644 --- a/src/doc/man/generated_txt/cargo-vendor.txt +++ b/src/doc/man/generated_txt/cargo-vendor.txt @@ -22,7 +22,7 @@ DESCRIPTION git sources. If you intend to modify a crate from a remote source, use [patch] or a path dependency pointing to a local copy of that crate. Cargo will then correctly handle the crate on incremental rebuilds, as - it knowns that it is no longer a read-only dependency. + it knows that it is no longer a read-only dependency. OPTIONS Vendor Options diff --git a/src/doc/src/commands/cargo-bench.md b/src/doc/src/commands/cargo-bench.md index 1605a15a319..d48e164e956 100644 --- a/src/doc/src/commands/cargo-bench.md +++ b/src/doc/src/commands/cargo-bench.md @@ -138,7 +138,7 @@ in the manifest settings. Setting examples to `bench = true` will build and run the example as a benchmark, replacing the example's `main` function with the libtest harness. -Setting targets to `bench = false` will stop them from being bencharmked by +Setting targets to `bench = false` will stop them from being benchmarked by default. Target selection options that take a target by name (such as `--example foo`) ignore the `bench` flag and will always benchmark the given target. diff --git a/src/doc/src/commands/cargo-metadata.md b/src/doc/src/commands/cargo-metadata.md index d4ac2b3a4ee..3326c44a1ef 100644 --- a/src/doc/src/commands/cargo-metadata.md +++ b/src/doc/src/commands/cargo-metadata.md @@ -27,7 +27,7 @@ for a Rust API for reading the metadata. Within the same output format version, the compatibility is maintained, except some scenarios. The following is a non-exhaustive list of changes that are not -considersed as incompatible: +considered as incompatible: * **Adding new fields** — New fields will be added when needed. Reserving this helps Cargo evolve without bumping the format version too often. diff --git a/src/doc/src/commands/cargo-vendor.md b/src/doc/src/commands/cargo-vendor.md index 12269570bb0..587da266ee1 100644 --- a/src/doc/src/commands/cargo-vendor.md +++ b/src/doc/src/commands/cargo-vendor.md @@ -25,7 +25,7 @@ Cargo treats vendored sources as read-only as it does to registry and git source If you intend to modify a crate from a remote source, use `[patch]` or a `path` dependency pointing to a local copy of that crate. Cargo will then correctly handle the crate on incremental rebuilds, -as it knowns that it is no longer a read-only dependency. +as it knows that it is no longer a read-only dependency. ## OPTIONS diff --git a/src/doc/src/reference/unstable.md b/src/doc/src/reference/unstable.md index d26e03b5148..625a823a20f 100644 --- a/src/doc/src/reference/unstable.md +++ b/src/doc/src/reference/unstable.md @@ -1812,5 +1812,5 @@ See [Registry Authentication](registry-authentication.md) documentation for deta The `-Z check-cfg` feature has been stabilized in the 1.80 release by making it the default behavior. -See the [build script documentation](build-scripts.md#rustc-check-cfg) for informations +See the [build script documentation](build-scripts.md#rustc-check-cfg) for information about specifying custom cfgs. diff --git a/src/etc/man/cargo-bench.1 b/src/etc/man/cargo-bench.1 index 5a39a16db2f..a9c3ba00387 100644 --- a/src/etc/man/cargo-bench.1 +++ b/src/etc/man/cargo-bench.1 @@ -148,7 +148,7 @@ in the manifest settings. Setting examples to \fBbench = true\fR will build and run the example as a benchmark, replacing the example\[cq]s \fBmain\fR function with the libtest harness. .sp -Setting targets to \fBbench = false\fR will stop them from being bencharmked by +Setting targets to \fBbench = false\fR will stop them from being benchmarked by default. Target selection options that take a target by name (such as \fB\-\-example foo\fR) ignore the \fBbench\fR flag and will always benchmark the given target. diff --git a/src/etc/man/cargo-metadata.1 b/src/etc/man/cargo-metadata.1 index 3e2ec312627..1357ad1f5d1 100644 --- a/src/etc/man/cargo-metadata.1 +++ b/src/etc/man/cargo-metadata.1 @@ -22,7 +22,7 @@ for a Rust API for reading the metadata. .SS "Compatibility" Within the same output format version, the compatibility is maintained, except some scenarios. The following is a non\-exhaustive list of changes that are not -considersed as incompatible: +considered as incompatible: .sp .RS 4 \h'-04'\(bu\h'+02'\fBAdding new fields\fR \[em] New fields will be added when needed. Reserving this diff --git a/src/etc/man/cargo-vendor.1 b/src/etc/man/cargo-vendor.1 index b739f2c8f88..eae728deaf7 100644 --- a/src/etc/man/cargo-vendor.1 +++ b/src/etc/man/cargo-vendor.1 @@ -23,7 +23,7 @@ Cargo treats vendored sources as read\-only as it does to registry and git sourc If you intend to modify a crate from a remote source, use \fB[patch]\fR or a \fBpath\fR dependency pointing to a local copy of that crate. Cargo will then correctly handle the crate on incremental rebuilds, -as it knowns that it is no longer a read\-only dependency. +as it knows that it is no longer a read\-only dependency. .SH "OPTIONS" .SS "Vendor Options" .sp