Capitalization

SemVer

Rust capitalization

src/doc/src/faq.md

@@ -125,7 +125,7 @@ compatibility). If Cargo used all of the dependencies' `Cargo.lock` files,
 then multiple copies of the library could be used, and perhaps even a version
 conflict.
 
-In other words, libraries specify semver requirements for their dependencies but
+In other words, libraries specify SemVer requirements for their dependencies but
 cannot see the full picture. Only end products like binaries have a full
 picture to decide what versions of dependencies should be used.
 

src/doc/src/reference/environment-variables.md

@@ -316,7 +316,7 @@ let out_dir = env::var("OUT_DIR").unwrap();
 * `TARGET` — the target triple that is being compiled for. Native code should be
              compiled for this triple. See the [Target Triple] description
              for more information.
-* `HOST` — the host triple of the rust compiler.
+* `HOST` — the host triple of the Rust compiler.
 * `NUM_JOBS` — the parallelism specified as the top-level parallelism. This can
                be useful to pass a `-j` parameter to a system like `make`. Note
                that care should be taken when interpreting this environment

src/doc/src/reference/manifest.md

@@ -98,11 +98,11 @@ Versioning](https://semver.org/), so make sure you follow some basic rules:
 
 See the [Resolver] chapter for more information on how Cargo uses versions to
 resolve dependencies, and for guidelines on setting your own version. See the
-[Semver compatibility] chapter for more details on exactly what constitutes a
+[SemVer compatibility] chapter for more details on exactly what constitutes a
 breaking change.
 
 [Resolver]: resolver.md
-[Semver compatibility]: semver.md
+[SemVer compatibility]: semver.md
 
 <a id="the-authors-field-optional"></a>
 #### The `authors` field

src/doc/src/reference/unstable.md

@@ -207,7 +207,7 @@ generated if dev-dependencies are skipped.
 > versions for direct dependencies.
 
 When a `Cargo.lock` file is generated, the `-Z minimal-versions` flag will
-resolve the dependencies to the minimum semver version that will satisfy the
+resolve the dependencies to the minimum SemVer version that will satisfy the
 requirements (instead of the greatest version).
 
 The intended use-case of this flag is to check, during continuous integration,