diff --git a/Documentation/process/embargoed-hardware-issues.rst b/Documentation/process/embargoed-hardware-issues.rst
index cb686238f21d..43f96ed709ba 100644
--- a/Documentation/process/embargoed-hardware-issues.rst
+++ b/Documentation/process/embargoed-hardware-issues.rst
@@ -95,13 +95,15 @@ The Linux kernel community has a dedicated hardware security team for
 initial contact, which oversees the process of handling such issues under
 embargo rules.
 
-The hardware security team identifies the developers (domain experts) who
-will form the initial response team for a particular issue. The initial
-response team can bring in further developers (domain experts) to address
-the issue in the best technical way.
-
-All involved developers pledge to adhere to the embargo rules and to keep
-the received information confidential. Violation of the pledge will lead to
+The hardware security team identifies the domain experts who will form the
+initial response team for a particular issue. The initial response team can
+bring in further members to address the issue in the best technical way.
+These members can be experts in a particular area of the kernel like a
+subsystem (PCI, scheduler, memory management, etc...) or an aspect of
+kernel development like testing.
+
+All those involved pledge to adhere to the embargo rules and to keep the
+received information confidential. Violation of the pledge will lead to
 immediate exclusion from the current issue and removal from all related
 mailing-lists. In addition, the hardware security team will also exclude
 the offender from future issues. The impact of this consequence is a highly