fix: favor* -> favour*

Author: drupol

src/thesis/1-introduction.typ

@@ -355,7 +355,7 @@ acknowledging that a complete examination of every aspect of reproducibility is
 beyond our scope.
 
 I will explore a selection of tools and methodologies that promote
-reproducibility or, at least, create favorable conditions for facilitating it.
+reproducibility or, at least, create favourable conditions for facilitating it.
 Moreover, this document is intended to enlighten and hopefully convince the
 reader that the construction of reproducible software should be a fundamental
 principle, not merely a secondary consideration, within the software development

src/thesis/2-reproducibility.typ

@@ -1197,7 +1197,7 @@ There are multiple existing formats and standards, the most common ones are:
   emphasises simplicity and efficiency, supporting formats such as XML, JSON,
   and ProtoBuf, and is particularly tailored towards the identification of
   software components, their vulnerabilities, and risk assessments, making it a
-  favorite in the application security and #gls("DevSecOps") communities.
+  favourite in the application security and #gls("DevSecOps") communities.
 
 The key differences between the #gls("SPDX") and #gls("CycloneDX") formats lie
 primarily in their focus, structure, and community support. The choice between

src/thesis/4-conclusion.typ

@@ -167,7 +167,7 @@ also not reproducible.
   the system. This creates a strong likelihood of like environments diverging
   over time in a process known as #emph[configuration drift]. The declarative
   approach to configuration management reduces the possibility of configuration
-  drift by favoring idempotence, explicit dependency graphs, and maintaining a
+  drift by favouring idempotence, explicit dependency graphs, and maintaining a
   strong awareness of the current state of the environment
   #cite(<HunterGCP>,form:"normal", supplement: [p.348]).
 ]