Signed-off-by: Akira Yokosawa <akiyks@xxxxxxxxx>
---
appendix/questions/ordering.tex | 2 +-
intro/intro.tex | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/appendix/questions/ordering.tex b/appendix/questions/ordering.tex
index c3015f73..298600f9 100644
--- a/appendix/questions/ordering.tex
+++ b/appendix/questions/ordering.tex
@@ -16,7 +16,7 @@ the other?
The answer, as is so often the case, is ``it depends''.
One approach is to construct a strongly ordered system, then examine
-its performance and scalablity.
+its performance and scalability.
If these suffice, the system is good and sufficient, and no more need
be done.
Otherwise, undertake careful analysis
diff --git a/intro/intro.tex b/intro/intro.tex
index b185a7f7..28c0bf50 100644
--- a/intro/intro.tex
+++ b/intro/intro.tex
@@ -934,7 +934,7 @@ However, partitioning the work requires great care.
For example, uneven partitioning can result in sequential execution
once the small partitions have completed~\cite{GeneAmdahl1967AmdahlsLaw}.
In less extreme cases, load balancing can be used to fully utilize
-available hardware and restore performance and scalabilty.
+available hardware and restore performance and scalability.
Although partitioning can greatly improve performance and scalability,
it can also increase complexity.
--
2.17.1
