From 8b2eb57fa462867d8cedee40f25487d53e8ee9e3 Mon Sep 17 00:00:00 2001
From: Andrew M Farrell <afarrell@mit.edu>
Date: Sat, 5 Dec 2009 00:05:42 -0500
Subject: [PATCH]

---
 doc/enabling_client_certificate_auth_in_chrome.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/enabling_client_certificate_auth_in_chrome.html b/doc/enabling_client_certificate_auth_in_chrome.html
index 4a00a42..c043778 100644
--- a/doc/enabling_client_certificate_auth_in_chrome.html
+++ b/doc/enabling_client_certificate_auth_in_chrome.html
@@ -9,7 +9,7 @@ if you're running Debian or Ubuntu, you can add "deb http://ppa.launchpad.net/ch
 <h3><a name="getting_certs">Installing Certificates</a></h3>
 <p> The simplest thing to do is go to the <a href="https://ca.mit.edu/ca/">usual web interface</a> and follow the instructions to install certs normally. 
 You may also want the <a href="http://ca.csail.mit.edu/cacert">CSAIL CA</a> (specifically, the Master CA).
-If this works, you should be able to skip to the second part <a href="#using_certs">
+If this works, you should be able to skip to telling chrome to<a href="#using_certs">use certtificate by default</a>
 
 Failing that, the next easiest way to install a client cert in the nss database is simply to install it on Firefox;
 At that point, it should be in the list of certificates you get when you run "certutil -d sql:$HOME/.pki/nssdb -L".
-- 
2.44.0