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

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

diff --git a/specifications.html b/specifications.html
index 4894e71..8abc7b4 100644
--- a/specifications.html
+++ b/specifications.html
@@ -25,7 +25,7 @@
 		<small>Credit: public domain</small>
 		
 		<h1>Specifications</h1>
-		<div class="lead">Andrew J. Ko</div>
+		<div class="lead">Amy J. Ko</div>
 
 		<p>When you make something with code, you're probably used to figuring out a design as you go. You write a function, you choose some arguments, and if you don't like what you see, perhaps you add a new argument to that function and test again. This <a href="https://en.wikipedia.org/wiki/Cowboy_coding" target="_blank">cowboy coding</a> as some people like to call it can be great fun! It allows systems to emerge more organically, as you iteratively see your front-end design emerge, the design of your implementation emerges too, co-evolving with how you're feeling about the final product.</p>