Auto merge of #11794 - ehuss:doc-typos, r=epage

Fix some doc typos

Author: bors

src/doc/man/cargo-rustc.md

@@ -74,7 +74,7 @@ See the [the reference](../reference/profiles.html) for more details on profiles
 {{#option "`--crate-type` _crate-type_"}}
 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 `crate-type`
-field in the manifest for configurating a Cargo target. See
+field in the manifest for configuring a Cargo target. See
 [`crate-type` field](../reference/cargo-targets.html#the-crate-type-field)
 for possible values.
 

src/doc/man/generated_txt/cargo-rustc.txt

@@ -196,7 +196,7 @@ OPTIONS
        --crate-type crate-type
            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 crate-type field in the manifest for configurating a Cargo
+           same as crate-type field in the manifest for configuring a Cargo
            target. See crate-type field
            <https://doc.rust-lang.org/cargo/reference/cargo-targets.html#the-crate-type-field>
            for possible values.

src/doc/src/commands/cargo-rustc.md

@@ -230,7 +230,7 @@ information about timing information.</li>
 <dt class="option-term" id="option-cargo-rustc---crate-type"><a class="option-anchor" href="#option-cargo-rustc---crate-type"></a><code>--crate-type</code> <em>crate-type</em></dt>
 <dd class="option-desc">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 <code>crate-type</code>
-field in the manifest for configurating a Cargo target. See
+field in the manifest for configuring a Cargo target. See
 <a href="../reference/cargo-targets.html#the-crate-type-field"><code>crate-type</code> field</a>
 for possible values.</p>
 <p>If the manifest contains a list, and <code>--crate-type</code> is provided,

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].

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

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 <https://doc.rust\-lang.org/cargo/reference/cargo\-targets.html#the\-crate\-type\-field>
 for possible values.
 .sp