difficultly -> difficulty

Author: katrinafyi

notes/architecture/content.tex

@@ -9,7 +9,7 @@ \section{Introduction}
 exploration into the term `software architecture'.
 The term is often overloaded to describe a number of completely separate concepts.
 The overloaded nature of the term makes an introduction quite challenging.
-Martin Fowler wrestles with this difficultly in his talk on \link{``Making Architecture Matter''}{https://www.youtube.com/watch?v=DngAZyWMGR0}.
+Martin Fowler wrestles with this difficulty in his talk on \link{``Making Architecture Matter''}{https://www.youtube.com/watch?v=DngAZyWMGR0}.
 In the talk Fowler settles on the slightly vague definition from Ralph Johnson \cite{fowler-what-is-architecture}:
 
 \begin{definition}[Software Architecture]
@@ -144,14 +144,14 @@ \section{Attributes in Tension}
 and to design an architecture and implement principles which ensure the quality attributes are achieved.
 
 \filbreak
-The first law of software architecture, as defined by Richards \cite{richards2020fundamentals}, reflects the difficultly in supporting multiple quality attributes.
+The first law of software architecture, as defined by Richards \cite{richards2020fundamentals}, reflects the difficulty in supporting multiple quality attributes.
 
 \begin{definition}[The First Law of Software Architecture]
 Everything in software architecture is a trade-off.
 \end{definition}
 
 Galster and Angelov \cite{wicked-architecture} define this as `wicked architecture'.
-They identify the `wicked' nature of architecture as the main difficultly in teaching the subject.
+They identify the `wicked' nature of architecture as the main difficulty in teaching the subject.
 
 \begin{definition}[Wicked Architecture]
 There are often no clear problem descriptions, no clear solutions, good or bad solutions, no clear rules when to ``stop'' architecting
@@ -161,7 +161,7 @@ \section{Attributes in Tension}
 They stress that ``In contrast, other software engineering topics such as programming lead to solutions that can be checked and measured for correctness.
 Architecture may be the worst-case scenario when it comes to fuzziness in software engineering''.
 
-Despite this difficultly, in this course we intend to expose you to a number of case studies, architectures,
+Despite this difficulty, in this course we intend to expose you to a number of case studies, architectures,
 and tools which aim to give you experience in tackling the trade-offs involved in software architecture.
 
 \section{The World Today}