chg: [rfc] accross -> across

pull/7/head
William Robinet 2024-12-31 16:39:23 +01:00
parent 3096b5c838
commit ae23554bc9
No known key found for this signature in database
GPG Key ID: 003FA3DF74C7A949
2 changed files with 2 additions and 2 deletions

View File

@ -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>

View File

@ -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