From f807f8a85156bac4ec3f881c73ca4a588f6ffa92 Mon Sep 17 00:00:00 2001
From: "Amy J. Ko" <ajko@uw.edu>
Date: Tue, 24 Sep 2019 14:18:36 -0700
Subject: [PATCH] Updated name.

---
 quality.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/quality.html b/quality.html
index dbbbc25..bafec54 100644
--- a/quality.html
+++ b/quality.html
@@ -26,7 +26,7 @@
 		<small>Credit: Anton Croos</small>
 		
 		<h1>Quality</h1>
-		<div class="lead">Andrew J. Ko</div>
+		<div class="lead">Amy 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>