docs: Surround identifiers in backticks

This was mostly done by clippy via `clippy::doc_markdown`.
I then reviewed it to fix words that shouldn't have it or where `--fix`
put the backtick in the wrong location.

Author: epage

benches/benchsuite/src/bin/capture-last-use.rs

@@ -1,7 +1,7 @@
 //! Utility for capturing a global cache last-use database based on the files
 //! on a real-world system.
 //!
-//! This will look in the CARGO_HOME of the current system and record last-use
+//! This will look in the `CARGO_HOME` of the current system and record last-use
 //! data for all files in the cache. This is intended to provide a real-world
 //! example for a benchmark that should be close to what a real set of data
 //! should look like.

crates/cargo-test-support/src/compare.rs

@@ -621,7 +621,7 @@ macro_rules! impl_from_tuple_for_inmemorydir {
     };
 }
 
-/// Extend `impl_from_tuple_for_inmemorydir`` to generate for the specified tuple and all smaller
+/// Extend `impl_from_tuple_for_inmemorydir` to generate for the specified tuple and all smaller
 /// tuples
 macro_rules! impl_from_tuples_for_inmemorydir {
     ($var1:ident $path1:ident $data1:ident, $($var:ident $path:ident $data:ident),+) => {

crates/cargo-test-support/src/containers.rs

@@ -5,7 +5,7 @@
 //! with the running container.
 //!
 //! Tests using containers must use `#[cargo_test(container_test)]` to disable
-//! them unless the CARGO_CONTAINER_TESTS environment variable is set.
+//! them unless the `CARGO_CONTAINER_TESTS` environment variable is set.
 
 use cargo_util::ProcessBuilder;
 use std::collections::HashMap;
@@ -36,7 +36,7 @@ pub struct ContainerHandle {
     /// This can only be used on Linux. macOS and Windows docker doesn't allow
     /// direct connection to the container.
     pub ip_address: String,
-    /// Port mappings of container_port to host_port for ports exposed via EXPOSE.
+    /// Port mappings of `container_port` to `host_port` for ports exposed via EXPOSE.
     pub port_mappings: HashMap<u16, u16>,
 }
 

crates/cargo-test-support/src/cross_compile.rs

@@ -3,7 +3,7 @@
 //! Note that cross-testing is very limited. You need to install the
 //! "alternate" target to the host (32-bit for 64-bit hosts or vice-versa).
 //!
-//! Set CFG_DISABLE_CROSS_TESTS=1 environment variable to disable these tests
+//! Set `CFG_DISABLE_CROSS_TESTS=1` environment variable to disable these tests
 //! if you are unable to use the alternate target. Unfortunately 32-bit
 //! support on macOS is going away, so macOS users are out of luck.
 //!

crates/cargo-test-support/src/lib.rs

@@ -890,7 +890,7 @@ impl Execs {
     ///
     /// Prefer [`Execs::with_stdout_data`] where possible.
     /// - `with` cannot be snapshotted
-    /// - The absence of `without`` can either mean success or that the string being looked for
+    /// - The absence of `without` can either mean success or that the string being looked for
     ///   changed.
     ///
     /// </div>

crates/cargo-test-support/src/paths.rs

@@ -17,7 +17,7 @@ static CARGO_INTEGRATION_TEST_DIR: &str = "cit";
 static GLOBAL_ROOT: OnceLock<Mutex<Option<PathBuf>>> = OnceLock::new();
 
 /// This is used when running cargo is pre-CARGO_TARGET_TMPDIR
-/// TODO: Remove when CARGO_TARGET_TMPDIR grows old enough.
+/// TODO: Remove when `CARGO_TARGET_TMPDIR` grows old enough.
 fn global_root_legacy() -> PathBuf {
     let mut path = t!(env::current_exe());
     path.pop(); // chop off exe name

crates/cargo-test-support/src/publish.rs

@@ -166,7 +166,7 @@ fn read_new_post(new_path: &Path) -> (Vec<u8>, Vec<u8>) {
 ///
 /// - `expected_crate_name` should be something like `foo-0.0.1.crate`.
 /// - `expected_files` should be a complete list of files in the crate
-///   (relative to expected_crate_name).
+///   (relative to `expected_crate_name`).
 /// - `expected_contents` should be a list of `(file_name, contents)` tuples
 ///   to validate the contents of the given file. Only the listed files will
 ///   be checked (others will be ignored).

crates/cargo-util-schemas/src/manifest/mod.rs

@@ -1680,7 +1680,7 @@ impl<'de> de::Deserialize<'de> for InvalidCargoFeatures {
     }
 }
 
-/// A StringOrVec can be parsed from either a TOML string or array,
+/// This can be parsed from either a TOML string or array,
 /// but is always stored as a vector.
 #[derive(Clone, Debug, Serialize, Eq, PartialEq, PartialOrd, Ord)]
 #[cfg_attr(feature = "unstable-schema", derive(schemars::JsonSchema))]

crates/cargo-util/src/paths.rs

@@ -189,7 +189,7 @@ pub fn write<P: AsRef<Path>, C: AsRef<[u8]>>(path: P, contents: C) -> Result<()>
 
 /// Writes a file to disk atomically.
 ///
-/// write_atomic uses tempfile::persist to accomplish atomic writes.
+/// This uses `tempfile::persist` to accomplish atomic writes.
 pub fn write_atomic<P: AsRef<Path>, C: AsRef<[u8]>>(path: P, contents: C) -> Result<()> {
     let path = path.as_ref();
 

crates/home/src/env.rs

@@ -10,11 +10,11 @@ use std::{
 /// in-process unit testing by rustup.
 pub trait Env {
     /// Return the path to the users home dir, or None if any error occurs:
-    /// see home_inner.
+    /// see `home_inner`.
     fn home_dir(&self) -> Option<PathBuf>;
     /// Return the current working directory.
     fn current_dir(&self) -> io::Result<PathBuf>;
-    /// Get an environment variable, as per std::env::var_os.
+    /// Get an environment variable, as per `std::env::var_os`.
     fn var_os(&self, key: &str) -> Option<OsString>;
 }
 
@@ -47,7 +47,7 @@ pub fn home_dir_with_env(env: &dyn Env) -> Option<PathBuf> {
     env.home_dir()
 }
 
-/// Variant of cargo_home where the environment source is parameterized. This is
+/// Variant of `cargo_home` where the environment source is parameterized. This is
 /// specifically to support in-process testing scenarios as environment
 /// variables and user home metadata are normally process global state. See the
 /// [`Env`] trait.
@@ -56,10 +56,10 @@ pub fn cargo_home_with_env(env: &dyn Env) -> io::Result<PathBuf> {
     cargo_home_with_cwd_env(env, &cwd)
 }
 
-/// Variant of cargo_home_with_cwd where the environment source is
+/// Variant of `cargo_home_with_cwd` where the environment source is
 /// parameterized. This is specifically to support in-process testing scenarios
 /// as environment variables and user home metadata are normally process global
-/// state. See the OsEnv trait.
+/// state. See the `OsEnv` trait.
 pub fn cargo_home_with_cwd_env(env: &dyn Env, cwd: &Path) -> io::Result<PathBuf> {
     match env.var_os("CARGO_HOME").filter(|h| !h.is_empty()) {
         Some(home) => {
@@ -76,19 +76,19 @@ pub fn cargo_home_with_cwd_env(env: &dyn Env, cwd: &Path) -> io::Result<PathBuf>
     }
 }
 
-/// Variant of cargo_home_with_cwd where the environment source is
+/// Variant of `cargo_home_with_cwd` where the environment source is
 /// parameterized. This is specifically to support in-process testing scenarios
 /// as environment variables and user home metadata are normally process global
-/// state. See the OsEnv trait.
+/// state. See the `OsEnv` trait.
 pub fn rustup_home_with_env(env: &dyn Env) -> io::Result<PathBuf> {
     let cwd = env.current_dir()?;
     rustup_home_with_cwd_env(env, &cwd)
 }
 
-/// Variant of cargo_home_with_cwd where the environment source is
+/// Variant of `cargo_home_with_cwd` where the environment source is
 /// parameterized. This is specifically to support in-process testing scenarios
 /// as environment variables and user home metadata are normally process global
-/// state. See the OsEnv trait.
+/// state. See the `OsEnv` trait.
 pub fn rustup_home_with_cwd_env(env: &dyn Env, cwd: &Path) -> io::Result<PathBuf> {
     match env.var_os("RUSTUP_HOME").filter(|h| !h.is_empty()) {
         Some(home) => {