doc(lib): resolve rustdoc warning (hyperium#3361)

.github/workflows/CI.yml

@@ -227,7 +227,7 @@ jobs:
       - uses: Swatinem/rust-cache@v2
 
       - name: cargo doc
-        run: cargo rustdoc --features full,ffi -- --cfg docsrs --cfg hyper_unstable_ffi -D broken-intra-doc-links
+        run: cargo rustdoc --features full,ffi -- --cfg docsrs --cfg hyper_unstable_ffi -D rustdoc::broken-intra-doc-links
 
   check-external-types:
     name: Check exposed types

src/body/mod.rs

@@ -7,10 +7,10 @@
 //!
 //! There are two pieces to this in hyper:
 //!
-//! - **The [`Body`](Body) trait** describes all possible bodies.
+//! - **The [`Body`] trait** describes all possible bodies.
 //!   hyper allows any body type that implements `Body`, allowing
 //!   applications to have fine-grained control over their streaming.
-//! - **The [`Incoming`](Incoming) concrete type**, which is an implementation
+//! - **The [`Incoming`] concrete type**, which is an implementation
 //!   of `Body`, and returned by hyper as a "receive stream" (so, for server
 //!   requests and client responses).
 //!

src/client/mod.rs

@@ -1,6 +1,6 @@
 //! HTTP Client
 //!
-//! hyper provides HTTP over a single connection. See the [`conn`](conn) module.
+//! hyper provides HTTP over a single connection. See the [`conn`] module.
 //!
 //! ## Example
 //!

src/server/mod.rs

@@ -5,5 +5,5 @@
 //!
 //! How exactly you choose to listen for connections is not something hyper
 //! concerns itself with. After you have a connection, you can handle HTTP over
-//! it with the types in the [`conn`](conn) module.
+//! it with the types in the [`conn`] module.
 pub mod conn;

src/service/mod.rs

@@ -1,6 +1,6 @@
 //! Asynchronous Services
 //!
-//! A [`Service`](Service) is a trait representing an asynchronous
+//! A [`Service`] is a trait representing an asynchronous
 //! function of a request to a response. It's similar to
 //! `async fn(Request) -> Result<Response, Error>`.
 //!
@@ -17,7 +17,7 @@
 //! to a single connection. It defines how to respond to **all** requests that
 //! connection will receive.
 //!
-//! The helper [`service_fn`](service_fn) should be sufficient for most cases, but
+//! The helper [`service_fn`] should be sufficient for most cases, but
 //! if you need to implement `Service` for a type manually, you can follow the example
 //! in `service_struct_impl.rs`.
 

src/upgrade.rs

@@ -73,7 +73,7 @@ pub struct OnUpgrade {
     rx: Option<oneshot::Receiver<crate::Result<Upgraded>>>,
 }
 
-/// The deconstructed parts of an [`Upgraded`](Upgraded) type.
+/// The deconstructed parts of an [`Upgraded`] type.
 ///
 /// Includes the original IO type, and a read buffer of bytes that the
 /// HTTP state machine may have already read before completing an upgrade.