a couple very small tweaks to the web page.

diff --git a/website/index.mdwn b/website/index.mdwn
index a7d074e4445eabfd0000ef6c588eaa9c4d680ebe..137b90a2a917ee2879202fe0245cc32586a75db0 100644 (file)
--- a/website/index.mdwn
+++ b/website/index.mdwn
@@ -19,8 +19,8 @@ the first time you log in to a new server, asking if you want to trust
 the server's key by verifying the key fingerprint.  Unfortunately,
 unless you have access to the server's key fingerprint through a
 secure out-of-band channel, there is no way to verify that the
-fingerprint you are presented with is in fact that of the server your
-really trying to connect to.
+fingerprint you are presented with is in fact that of the server
+you're really trying to connect to.
 
 Many users also take advantage of OpenSSH's ability to use RSA or DSA
 keys for authenticating to a server (known as
@@ -42,7 +42,7 @@ expected.
 The basic idea of the Monkeysphere is to create a framework that uses
 [GnuPG](http://www.gnupg.org/)'s keyring manipulation capabilities and
 public keyserver communication to manage the keys that OpenSSH uses
-for connection authentication.  
+for connection authentication.
 
 The Monkeysphere therefore provides an effective PKI for OpenSSH,
 including the possibility for key transitions, transitive
@@ -55,11 +55,11 @@ Under the Monkeysphere, both parties to an OpenSSH connection (client
 and server) explicitly designate who they trust to certify the
 identity of the other party.  These trust designations are explicitly
 indicated with traditional GPG keyring trust models.  Monkeysphere
-then manages the keys in the `known_hosts` and `authorized_keys`
-files directly, in such a way that is completely transparent to SSH.
-No modification is made to the SSH protocol on the wire (it continues
-to use raw RSA public keys), and no modification is needed to the
-OpenSSH software.
+then manages the keys in the `known_hosts` and `authorized_keys` files
+directly, in such a way that is completely transparent to `ssh`.  No
+modification is made to the SSH protocol on the wire (it continues to
+use raw RSA public keys), and no modification is needed to the OpenSSH
+software.
 
 To emphasize: ***no modifications to SSH are required to use the
 Monkeysphere***.  OpenSSH can be used as is; completely unpatched and

diff --git a/website/why.mdwn b/website/why.mdwn
index 336643988abae643b51c514f079194884fb67cc8..c90df9a1b5266c97bf0b03c76c7ed790a35e6047 100644 (file)
--- a/website/why.mdwn
+++ b/website/why.mdwn
@@ -118,10 +118,10 @@ allows a very flexible trust model, ranging all over the map, at the
 choice of the user:
 
 * individual per-host certifications by each client (much like the
-  stock OpenSSH behavior),
+  stock OpenSSH behavior), or
 
 * strict centralized Certificate Authorities (much like proposed X.509
-  models), and
+  models), or
 
 * a more human-centric model that recognizes individual differences in
   ranges of trust and acceptance.