fix 6 typos

diff --git a/src/doc/src/faq.md b/src/doc/src/faq.md
index 2b89a7b2a35b36513871e44d8085324f611f40fc..5e0521882132d3d5eaa1362a92ec1e03410ed526 100644 (file)
--- a/src/doc/src/faq.md
+++ b/src/doc/src/faq.md
@@ -204,7 +204,7 @@ replacement][replace].
 ### Why is Cargo rebuilding my code?
 
 Cargo is responsible for incrementally compiling crates in your project. This
-means that if you type `cargo build` twice the second one shouldn't rebuild you
+means that if you type `cargo build` twice the second one shouldn't rebuild your
 crates.io dependencies, for example. Nevertheless bugs arise and Cargo can
 sometimes rebuild code when you're not expecting it!
 

diff --git a/src/doc/src/reference/features.md b/src/doc/src/reference/features.md
index 3277e5e614aa433b87b5e3ef2e1930e8997f7763..d36bdf08bd3fb6ae12861afee6d93809c43a7620 100644 (file)
--- a/src/doc/src/reference/features.md
+++ b/src/doc/src/reference/features.md
@@ -440,7 +440,7 @@ guide, consider adding the documentation there (for example, see [serde.rs]).
 If you have a binary project, consider documenting the features in the README
 or other documentation for the project (for example, see [sccache]).
 
-Clearly documenting the features can set expectations about features
+Clearly documenting the features can set expectations about features that are
 considered "unstable" or otherwise shouldn't be used. For example, if there is
 an optional dependency, but you don't want users to explicitly list that
 optional dependency as a feature, exclude it from the documented list.

diff --git a/src/doc/src/reference/overriding-dependencies.md b/src/doc/src/reference/overriding-dependencies.md
index 5700f5251479ba31cee0467617d5e580dcc321ca..9dd402a1fe5edd5cb0eef4374bada8782c325dfd 100644 (file)
--- a/src/doc/src/reference/overriding-dependencies.md
+++ b/src/doc/src/reference/overriding-dependencies.md
@@ -222,7 +222,7 @@ Note that this will actually resolve to two versions of the `uuid` crate. The
 `my-binary` crate will continue to use the 1.x.y series of the `uuid` crate but
 the `my-library` crate will use the `2.0.0` version of `uuid`. This will allow you
 to gradually roll out breaking changes to a crate through a dependency graph
-without being force to update everything all at once.
+without being forced to update everything all at once.
 
 ### Using `[patch]` with multiple versions
 

diff --git a/src/doc/src/reference/source-replacement.md b/src/doc/src/reference/source-replacement.md
index 80f363899c97d294e52d91bb7941a73e4cd25f31..3ee3e7f0e07c4b1d0ec48e03904b3eb6b7db3dfc 100644 (file)
--- a/src/doc/src/reference/source-replacement.md
+++ b/src/doc/src/reference/source-replacement.md
@@ -107,7 +107,7 @@ the crates that are present).
 
 A "directory source" is similar to a local registry source where it contains a
 number of crates available on the local filesystem, suitable for vendoring
-dependencies. Directory sources are primarily managed the `cargo vendor`
+dependencies. Directory sources are primarily managed by the `cargo vendor`
 subcommand.
 
 Directory sources are distinct from local registries though in that they contain

diff --git a/src/doc/src/reference/unstable.md b/src/doc/src/reference/unstable.md
index 0c4f0bcb03f5ee3dfbeebed8fbd675d9dc3b84df..e6057f3ff413ae1cf5b5e83a85d05f213d44aee0 100644 (file)
--- a/src/doc/src/reference/unstable.md
+++ b/src/doc/src/reference/unstable.md
@@ -847,7 +847,7 @@ Other possible string values of `strip` are `none`, `symbols`, and `off`. The de
 
 You can also configure this option with the two absolute boolean values
 `true` and `false`. The former enables `strip` at its higher level, `symbols`,
-whilst the later disables `strip` completely.
+while the latter disables `strip` completely.
 
 ### rustdoc-map
 * Tracking Issue: [#8296](https://github.com/rust-lang/cargo/issues/8296)
@@ -1153,7 +1153,7 @@ cargo logout -Z credential-process
 * RFC: [#2495](https://github.com/rust-lang/rfcs/blob/master/text/2495-min-rust-version.md)
 * rustc Tracking Issue: [#65262](https://github.com/rust-lang/rust/issues/65262)
 
-The `-Z rust-version` flag enables the reading the `rust-version` field in the
+The `-Z rust-version` flag enables the reading of the `rust-version` field in the
 Cargo manifest `package` section. This can be used by a package to state a minimal
 version of the compiler required to build the package. An error is generated if
 the version of rustc is older than the stated `rust-version`. The