From 441c9692939ed33705e21c714c17e557d1a2cd80 Mon Sep 17 00:00:00 2001
From: Eric Huss --crate-type
crate-typecrate-type
-field in the manifest for configurating a Cargo target. See
+field in the manifest for configuring a Cargo target. See
crate-type
field
for possible values.
If the manifest contains a list, and --crate-type
is provided,
diff --git a/src/doc/src/reference/config.md b/src/doc/src/reference/config.md
index b826beb75cc..135c03cada7 100644
--- a/src/doc/src/reference/config.md
+++ b/src/doc/src/reference/config.md
@@ -196,7 +196,7 @@ Environment variables will take precedence over TOML configuration files.
Currently only integer, boolean, string and some array values are supported to
be defined by environment variables. [Descriptions below](#configuration-keys)
indicate which keys support environment variables and otherwise they are not
-supported due to [technicial issues](https://github.com/rust-lang/cargo/issues/5416).
+supported due to [technical issues](https://github.com/rust-lang/cargo/issues/5416).
In addition to the system above, Cargo recognizes a few other specific
[environment variables][env].
diff --git a/src/doc/src/reference/registry-index.md b/src/doc/src/reference/registry-index.md
index ceba14808ea..bc760e5c8e0 100644
--- a/src/doc/src/reference/registry-index.md
+++ b/src/doc/src/reference/registry-index.md
@@ -222,7 +222,7 @@ The sparse protocol uses the `sparse+` protocol prefix in the registry URL. For
the sparse index URL for [crates.io] is `sparse+https://index.crates.io/`.
The sparse protocol downloads each index file using an individual HTTP request. Since
-this results in a large number of small HTTP requests, performance is signficiantly
+this results in a large number of small HTTP requests, performance is significantly
improved with a server that supports pipelining and HTTP/2.
##### Caching
@@ -245,7 +245,7 @@ or 451 "Unavailable For Legal Reasons" code.
##### Sparse Limitations
Since the URL of the registry is stored in the lockfile, it's not recommended to offer
a registry with both protocols. Discussion about a transition plan is ongoing in issue
-[#10964]. The [crates.io] registry is an exception, since Cargo internally substitues
+[#10964]. The [crates.io] registry is an exception, since Cargo internally substitutes
the equivalent git URL when the sparse protocol is used.
If a registry does offer both protocols, it's currently recommended to choose one protocol
diff --git a/src/etc/man/cargo-rustc.1 b/src/etc/man/cargo-rustc.1
index 63796c5065a..8916a70a8d7 100644
--- a/src/etc/man/cargo-rustc.1
+++ b/src/etc/man/cargo-rustc.1
@@ -229,7 +229,7 @@ information about timing information.
.RS 4
Build for the given crate type. This flag accepts a comma\-separated list of
1 or more crate types, of which the allowed values are the same as \fBcrate\-type\fR
-field in the manifest for configurating a Cargo target. See
+field in the manifest for configuring a Cargo target. See
\fI\f(BIcrate\-type\fI field\fR