fix some typos

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

@@ -9,7 +9,7 @@ with the Cargo team first.
 
 For features that require behavior changes or new syntax in `Cargo.toml`, then
 it will need a `cargo-features` value placed at the top of `Cargo.toml` to
-enable it. The process for doing adding a new feature is described in the
+enable it. The process for adding a new feature is described in the
 [`features` module]. Code that implements the feature will need to manually
 check that the feature is enabled for the current manifest.
 

src/doc/src/reference/build-scripts.md

@@ -172,7 +172,7 @@ native library using [FFI].
 
 The `LIB` string is passed directly to rustc, so it supports any syntax that
 `-l` does. \
-Currently the full supported syntax for `LIB` is `[KIND[:MODIFIERS]=]NAME[:RENAME]`.
+Currently the fully supported syntax for `LIB` is `[KIND[:MODIFIERS]=]NAME[:RENAME]`.
 
 The `-l` flag is only passed to the library target of the package, unless
 there is no library target, in which case it is passed to all targets. This is

src/doc/src/reference/registry-index.md

@@ -179,7 +179,7 @@ explaining the format of the entry.
     // An unsigned 32-bit integer value indicating the schema version of this
     // entry.
     //
-    // If this not specified, it should be interpreted as the default of 1.
+    // If this is not specified, it should be interpreted as the default of 1.
     //
     // Cargo (starting with version 1.51) will ignore versions it does not
     // recognize. This provides a method to safely introduce changes to index

src/doc/src/reference/resolver.md

@@ -501,7 +501,7 @@ solutions.
 
 ### Why was a dependency included?
 
-Say you see dependency `rand` in the `cargo check` output but don't think its needed and want to understand why its being pulled in.
+Say you see dependency `rand` in the `cargo check` output but don't think it's needed and want to understand why it's being pulled in.
 
 You can run
 ```console

src/doc/src/reference/semver.md

@@ -356,7 +356,7 @@ fn main() {
 #### Minor: Adding `repr(C)` to a default representation {#repr-c-add}
 
 It is safe to add `repr(C)` to a struct, union, or enum with [the default representation].
-This is safe because users should not make assumptions about the alignment, layout, or size of types with with the default representation.
+This is safe because users should not make assumptions about the alignment, layout, or size of types with the default representation.
 
 ```rust,ignore
 // MINOR CHANGE
@@ -1010,7 +1010,7 @@ fn main() {
 ```
 
 Mitigation strategies:
-* Do not add new new fields to all-public field structs.
+* Do not add new fields to all-public field structs.
 * Mark structs as [`#[non_exhaustive]`][non_exhaustive] when first introducing
   a struct to prevent users from using struct literal syntax, and instead
   provide a constructor method and/or [Default] implementation.

src/doc/src/reference/unstable.md

@@ -594,7 +594,7 @@ cargo +nightly -Ztarget-applies-to-host build --target x86_64-unknown-linux-gnu
 * Original Pull Request: [#9322](https://github.com/rust-lang/cargo/pull/9322)
 * Tracking Issue: [#9452](https://github.com/rust-lang/cargo/issues/9452)
 
-The `host` key in a config file can be used pass flags to host build targets
+The `host` key in a config file can be used to pass flags to host build targets
 such as build scripts that must run on the host system instead of the target
 system when cross compiling. It supports both generic and host arch specific
 tables. Matching host arch tables take precedence over generic host tables.
@@ -614,7 +614,7 @@ rustflags = ["-Clink-arg=--verbose"]
 linker = "/path/to/target/linker"
 ```
 
-The generic `host` table above will be entirely ignored when building on a
+The generic `host` table above will be entirely ignored when building on an
 `x86_64-unknown-linux-gnu` host as the `host.x86_64-unknown-linux-gnu` table
 takes precedence.