From c57fd992595a215d447b963e493ed59664a87e12 Mon Sep 17 00:00:00 2001
From: Sean McArthur <sean@seanmonstar.com>
Date: Wed, 1 Nov 2023 15:56:14 -0400
Subject: [PATCH] docs: remove redundant link targets

---
 src/blocking/mod.rs       |  9 ++++-----
 src/blocking/multipart.rs |  4 ++--
 src/lib.rs                | 13 +++++++------
 src/tls.rs                |  4 ++--
 4 files changed, 15 insertions(+), 15 deletions(-)

diff --git a/src/blocking/mod.rs b/src/blocking/mod.rs
index 487387545..0a6867418 100644
--- a/src/blocking/mod.rs
+++ b/src/blocking/mod.rs
@@ -16,7 +16,7 @@
 //!
 //! # Making a GET request
 //!
-//! For a single request, you can use the [`get`](get) shortcut method.
+//! For a single request, you can use the [`get`] shortcut method.
 //!
 //! ```rust
 //! # use reqwest::{Error, Response};
@@ -30,19 +30,18 @@
 //! # }
 //! ```
 //!
-//! Additionally, the blocking [`Response`](Response) struct implements Rust's
+//! Additionally, the blocking [`Response`] struct implements Rust's
 //! `Read` trait, so many useful standard library and third party crates will
 //! have convenience methods that take a `Response` anywhere `T: Read` is
 //! acceptable.
 //!
 //! **NOTE**: If you plan to perform multiple requests, it is best to create a
-//! [`Client`](Client) and reuse it, taking advantage of keep-alive connection
-//! pooling.
+//! [`Client`] and reuse it, taking advantage of keep-alive connection pooling.
 //!
 //! # Making POST requests (or setting request bodies)
 //!
 //! There are several ways you can set the body of a request. The basic one is
-//! by using the `body()` method of a [`RequestBuilder`](RequestBuilder). This lets you set the
+//! by using the `body()` method of a [`RequestBuilder`]. This lets you set the
 //! exact raw bytes of what the body should be. It accepts various types,
 //! including `String`, `Vec<u8>`, and `File`. If you wish to pass a custom
 //! Reader, you can use the `reqwest::blocking::Body::new()` constructor.
diff --git a/src/blocking/multipart.rs b/src/blocking/multipart.rs
index 9e7dfd3c7..5014b3975 100644
--- a/src/blocking/multipart.rs
+++ b/src/blocking/multipart.rs
@@ -1,7 +1,7 @@
 //! multipart/form-data
 //!
-//! To send a `multipart/form-data` body, a [`Form`](crate::blocking::multipart::Form) is built up, adding
-//! fields or customized [`Part`](crate::blocking::multipart::Part)s, and then calling the
+//! To send a `multipart/form-data` body, a [`Form`] is built up, adding
+//! fields or customized [`Part`]s, and then calling the
 //! [`multipart`][builder] method on the `RequestBuilder`.
 //!
 //! # Example
diff --git a/src/lib.rs b/src/lib.rs
index 017cfea94..188ba4f02 100644
--- a/src/lib.rs
+++ b/src/lib.rs
@@ -12,8 +12,8 @@
 //! It handles many of the things that most people just expect an HTTP client
 //! to do for them.
 //!
-//! - Async and [blocking](blocking) Clients
-//! - Plain bodies, [JSON](#json), [urlencoded](#forms), [multipart](multipart)
+//! - Async and [blocking] Clients
+//! - Plain bodies, [JSON](#json), [urlencoded](#forms), [multipart]
 //! - Customizable [redirect policy](#redirect-policies)
 //! - HTTP [Proxies](#proxies)
 //! - Uses system-native [TLS](#tls)
@@ -138,7 +138,7 @@
 //! `HTTP_PROXY` or `http_proxy` provide http proxies for http connections while
 //! `HTTPS_PROXY` or `https_proxy` provide HTTPS proxies for HTTPS connections.
 //!
-//! These can be overwritten by adding a [`Proxy`](Proxy) to `ClientBuilder`
+//! These can be overwritten by adding a [`Proxy`] to `ClientBuilder`
 //! i.e. `let proxy = reqwest::Proxy::http("https://secure.example")?;`
 //! or disabled by calling `ClientBuilder::no_proxy()`.
 //!
@@ -155,16 +155,17 @@
 //! Security-Framework on macOS, and OpenSSL on Linux.
 //!
 //! - Additional X509 certificates can be configured on a `ClientBuilder` with the
-//!   [`Certificate`](Certificate) type.
+//!   [`Certificate`] type.
 //! - Client certificates can be added to a `ClientBuilder` with the
-//!   [`Identity`][Identity] type.
+//!   [`Identity`] type.
 //! - Various parts of TLS can also be configured or even disabled on the
 //!   `ClientBuilder`.
 //!
 //! ## WASM
+//!
 //! The Client implementation automatically switches to the WASM one when the target_arch is wasm32,
 //! the usage is basically the same as the async api. Some of the features are disabled in wasm
-//! : [`tls`](tls) [`cookie`](cookie) [`blocking`](blocking).
+//! : [`tls`], [`cookie`], [`blocking`].
 //!
 //!
 //! ## Optional Features
diff --git a/src/tls.rs b/src/tls.rs
index e873939ab..52cc12862 100644
--- a/src/tls.rs
+++ b/src/tls.rs
@@ -5,9 +5,9 @@
 //! Security-Framework on macOS, and OpenSSL on Linux.
 //!
 //! - Additional X509 certificates can be configured on a `ClientBuilder` with the
-//!   [`Certificate`](Certificate) type.
+//!   [`Certificate`] type.
 //! - Client certificates can be add to a `ClientBuilder` with the
-//!   [`Identity`][Identity] type.
+//!   [`Identity`] type.
 //! - Various parts of TLS can also be configured or even disabled on the
 //!   `ClientBuilder`.