(no commit message)

diff --git a/doc/enabling_client_certificate_auth_in_chrome.html b/doc/enabling_client_certificate_auth_in_chrome.html
index 4bf6bef6f2d386f30921d4d1a82364c9426083cb..1990896525726d36b0f88523ecb69adab2ddab5b 100644 (file)
--- 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 id="getting_certs">Installing Certificates</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).
 <h3 id="getting_certs">Installing Certificates</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 telling chrome to<a href="#using_certs">use certtificate by default</a>
+If this works, you should be able to skip to telling chrome to <a href="#using_certs">use certificate 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".
 
 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".