From 7b386f5af7ce2eb4d3206827b491d5dff0671310 Mon Sep 17 00:00:00 2001
From: Andy Ko <ajko@uw.edu>
Date: Tue, 9 Apr 2019 12:26:42 -0700
Subject: [PATCH] Consistent naming.

---
 index.html   | 4 ++--
 quality.html | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/index.html b/index.html
index 3c44c7c..260d3cb 100644
--- a/index.html
+++ b/index.html
@@ -48,10 +48,10 @@
 				<td>Chapter 4. <a href="productivity.html">Productivity</a></td>
 			</tr>
 			<tr>
-				<td>Chapter 5. <a href="quality.html">Software quality</a></td>
+				<td>Chapter 5. <a href="quality.html">Quality</a></td>
 			</tr>
 			<tr>
-				<td>Chapter 6. <a href="requirements.html">Requirements engineering</a></td>
+				<td>Chapter 6. <a href="requirements.html">Requirements</a></td>
 			</tr>
 			<tr>
 				<td>Chapter 7. <a href="architecture.html">Architecture</a></td>
diff --git a/quality.html b/quality.html
index 3f4514a..3f13149 100644
--- a/quality.html
+++ b/quality.html
@@ -26,7 +26,7 @@
 		<img src="images/pomegranate.jpg" class="img-responsive" />		
 		<small>Credit: Anton Croos</small>
 		
-		<h1>Software Quality</h1>
+		<h1>Quality</h1>
 		<div class="lead">Andrew J. Ko</div>
 
 		<p>There are numerous ways a software project can fail: projects can be over budget, they can ship late, they can fail to be useful, or they can simply not be useful enough. Evidence clearly shows that success is highly contextual and stakeholder-dependent: success might be financial, social, physical and even emotional, suggesting that software engineering success is a multifaceted variable that cannot explained simply by user satisfaction, profitability or meeting requirements, budgets and schedules (<a href="#ralph">Ralph & Kelly 2014</a>).</p>