From ae23554bc90ef4cee77c633a5b6943881305ceaf Mon Sep 17 00:00:00 2001 From: William Robinet Date: Tue, 31 Dec 2024 16:39:23 +0100 Subject: [PATCH] chg: [rfc] accross -> across --- rfc/threat-actor-naming.html | 2 +- rfc/threat-actor-naming.txt | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/rfc/threat-actor-naming.html b/rfc/threat-actor-naming.html index 4825ac0..2764306 100644 --- a/rfc/threat-actor-naming.html +++ b/rfc/threat-actor-naming.html @@ -1452,7 +1452,7 @@ document are to be interpreted as described in RFC 2119 [ 2.6. Directory -

A reference registry of threat actors is RECOMMENDED to ensure consistency of names accross different parties such as the threat actor MISP galaxy [MISP-G].

+

A reference registry of threat actors is RECOMMENDED to ensure consistency of names across different parties such as the threat actor MISP galaxy [MISP-G].

diff --git a/rfc/threat-actor-naming.txt b/rfc/threat-actor-naming.txt index 4c1cdf7..e44c74b 100644 --- a/rfc/threat-actor-naming.txt +++ b/rfc/threat-actor-naming.txt @@ -181,7 +181,7 @@ Internet-Draft Recommendations on Naming Threat Actors December 2024 2.6. Directory A reference registry of threat actors is RECOMMENDED to ensure - consistency of names accross different parties such as the threat + consistency of names across different parties such as the threat actor MISP galaxy [MISP-G]. 3. Examples