1 files changed, 1 insertions, 1 deletions
diff --git a/doc/implementation_notes.md b/doc/implementation_notes.md
index 3b8e49d..cbf76ee 100644
--- a/doc/implementation_notes.md
+++ b/doc/implementation_notes.md
@@ -64,7 +64,7 @@ to the filesystem. This ensures that every metadata is removed.
 XML attacks
 -----------
-Since our thread model conveniently excludes files crafted to specifically
+Since our threat model conveniently excludes files crafted to specifically
 bypass MAT2, fileformats containing harmful XML are out of our scope.
 But since MAT2 is using [etree](https://docs.python.org/3/library/xml.html#xml-vulnerabilities)
 to process XML, it's "only" vulnerable to DoS, and not memory corruption:

diff --git a/doc/implementation_notes.md b/doc/implementation_notes.md index 3b8e49d..cbf76ee 100644 --- a/doc/implementation_notes.md +++ b/doc/implementation_notes.md
@@ -64,7 +64,7 @@ to the filesystem. This ensures that every metadata is removed.
64	XML attacks	64	XML attacks
65	-----------	65	-----------
66		66
67	Since our thread model conveniently excludes files crafted to specifically	67	Since our threat model conveniently excludes files crafted to specifically
68	bypass MAT2, fileformats containing harmful XML are out of our scope.	68	bypass MAT2, fileformats containing harmful XML are out of our scope.
69	But since MAT2 is using [etree](https://docs.python.org/3/library/xml.html#xml-vulnerabilities)	69	But since MAT2 is using [etree](https://docs.python.org/3/library/xml.html#xml-vulnerabilities)
70	to process XML, it's "only" vulnerable to DoS, and not memory corruption:	70	to process XML, it's "only" vulnerable to DoS, and not memory corruption: