rust-osdev
diff --git a/‎uefi-raw/src/protocol/mod.rs
Copy file name to clipboardExpand all lines: uefi-raw/src/protocol/mod.rs
+20-3Lines changed: 20 additions & 3 deletions b/‎uefi-raw/src/protocol/mod.rs
Copy file name to clipboardExpand all lines: uefi-raw/src/protocol/mod.rs
+20-3Lines changed: 20 additions & 3 deletions
diff --git a/‎uefi/src/proto/mod.rs
Copy file name to clipboardExpand all lines: uefi/src/proto/mod.rs
+26-5Lines changed: 26 additions & 5 deletions b/‎uefi/src/proto/mod.rs
Copy file name to clipboardExpand all lines: uefi/src/proto/mod.rs
+26-5Lines changed: 26 additions & 5 deletions
@@ -2,9 +2,26 @@
 
 //! Protocol definitions.
 //!
-//! Protocols are sets of related functionality identified by a unique
-//! ID. They can be implemented by a UEFI driver or occasionally by a
-//! UEFI application.
+//! # TL;DR
+//! Technically, a protocol is a `C` struct holding functions and/or data, with
+//! an associated [`GUID`].
+//!
+//! # About
+//! UEFI protocols are a structured collection of functions and/or data,
+//! identified by a [`GUID`], which defines an interface between components in
+//! the UEFI environment, such as between drivers, applications, or firmware
+//! services.
+//!
+//! Protocols are central to UEFI’s handle-based object model, and they provide
+//! a clean, extensible way for components to discover and use services from one
+//! another.
+//!
+//! Implementation-wise, a protocol is a `C` struct holding function pointers
+//! and/or data. Please note that some protocols may use [`core::ptr::null`] as
+//! interface. For example, the device path protocol can be implemented but
+//! return `null`.
+//!
+//! [`GUID`]: crate::Guid
 
 pub mod ata;
 pub mod block;
 
@@ -1,14 +1,35 @@
 // SPDX-License-Identifier: MIT OR Apache-2.0
 
-//! Protocol definitions.
+//! High-level wrappers for [UEFI protocols].
 //!
-//! Protocols are sets of related functionality identified by a unique
-//! ID. They can be implemented by a UEFI driver or occasionally by a
-//! UEFI application.
+//! # TL;DR
+//! Technically, a protocol is a `C` struct holding functions and/or data, with
+//! an associated [`GUID`].
 //!
-//! See the [`boot`] documentation for details of how to open a protocol.
+//! # About
+//! UEFI protocols are a structured collection of functions and/or data,
+//! identified by a [`GUID`], which defines an interface between components in
+//! the UEFI environment, such as between drivers, applications, or firmware
+//! services.
+//!
+//! Protocols are central to UEFI’s handle-based object model, and they provide
+//! a clean, extensible way for components to discover and use services from one
+//! another.
+//!
+//! Implementation-wise, a protocol is a `C` struct holding function pointers
+//! and/or data. Please note that some protocols may use [`core::ptr::null`] as
+//! interface. For example, the device path protocol can be implemented but
+//! return `null`.
+//!
+//! [`GUID`]: crate::Guid
+//!
+//! # More Info
+//! - See the [`boot`] documentation for details of how to open a protocol.
+//! - Please find additional low-level information in the
+//!   [protocol section of `uefi-raw`][[UEFI protocols]].
 //!
 //! [`boot`]: crate::boot#accessing-protocols
+//! [UEFI protocols]: uefi_raw::protocol
 
 #[cfg(feature = "alloc")]
 pub mod ata;