From 2f2788a140ede355334a12e4cb377e6c44ac3793 Mon Sep 17 00:00:00 2001
From: William Robinet <william.robinet@conostix.com>
Date: Tue, 31 Dec 2024 19:44:13 +0100
Subject: [PATCH] chg: [threat-actor-naming] accross -> across

---
 threat-actor-naming/raw.md                   | 2 +-
 threat-actor-naming/threat-actor-naming.html | 2 +-
 threat-actor-naming/threat-actor-naming.txt  | 2 +-
 threat-actor-naming/threat-actor-naming.xml  | 2 +-
 4 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/threat-actor-naming/raw.md b/threat-actor-naming/raw.md
index 6470b00..d06ddf5 100644
--- a/threat-actor-naming/raw.md
+++ b/threat-actor-naming/raw.md
@@ -96,7 +96,7 @@ The name of the threat actor **MUST NOT** be based on the tools, techniques, or
 
 ## 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].
 
 # Examples
 
diff --git a/threat-actor-naming/threat-actor-naming.html b/threat-actor-naming/threat-actor-naming.html
index 4825ac0..2764306 100644
--- a/threat-actor-naming/threat-actor-naming.html
+++ b/threat-actor-naming/threat-actor-naming.html
@@ -1452,7 +1452,7 @@ document are to be interpreted as described in RFC 2119 <span>[<a href="#RFC2119
         <h3 id="name-directory">
 <a href="#section-2.6" class="section-number selfRef">2.6. </a><a href="#name-directory" class="section-name selfRef">Directory</a>
         </h3>
-<p id="section-2.6-1">A reference registry of threat actors is <span class="bcp14">RECOMMENDED</span> to ensure consistency of names accross different parties such as the threat actor MISP galaxy <span>[<a href="#MISP-G" class="cite xref">MISP-G</a>]</span>.<a href="#section-2.6-1" class="pilcrow">¶</a></p>
+<p id="section-2.6-1">A reference registry of threat actors is <span class="bcp14">RECOMMENDED</span> to ensure consistency of names across different parties such as the threat actor MISP galaxy <span>[<a href="#MISP-G" class="cite xref">MISP-G</a>]</span>.<a href="#section-2.6-1" class="pilcrow">¶</a></p>
 </section>
 </div>
 </section>
diff --git a/threat-actor-naming/threat-actor-naming.txt b/threat-actor-naming/threat-actor-naming.txt
index 4c1cdf7..e44c74b 100644
--- a/threat-actor-naming/threat-actor-naming.txt
+++ b/threat-actor-naming/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
diff --git a/threat-actor-naming/threat-actor-naming.xml b/threat-actor-naming/threat-actor-naming.xml
index ede298c..a1b59a9 100644
--- a/threat-actor-naming/threat-actor-naming.xml
+++ b/threat-actor-naming/threat-actor-naming.xml
@@ -73,7 +73,7 @@ document are to be interpreted as described in RFC 2119 <xref target="RFC2119"><
 </section>
 
 <section anchor="directory"><name>Directory</name>
-<t>A reference registry of threat actors is <bcp14>RECOMMENDED</bcp14> to ensure consistency of names accross different parties such as the threat actor MISP galaxy <xref target="MISP-G"></xref>.</t>
+<t>A reference registry of threat actors is <bcp14>RECOMMENDED</bcp14> to ensure consistency of names across different parties such as the threat actor MISP galaxy <xref target="MISP-G"></xref>.</t>
 </section>
 </section>