actually ship new upstream changelog

[monkeysphere.git] / website / advanced-user.mdwn

diff --git a/website/advanced-user.mdwn b/website/advanced-user.mdwn
index ecb094b9ce97a7775e18358db1e60cbee2e4d19d..7969018b33598ff126877eb063e3699dec9fa95d 100644 (file)
--- a/website/advanced-user.mdwn
+++ b/website/advanced-user.mdwn
@@ -10,9 +10,9 @@ Keeping your `known_hosts` file in sync with your keyring
 If you want to keep your keyring updated without attempting
 connections to a remote host, you want to make sure that OpenSSH can
 still see the most recent trusted information about who the various
 If you want to keep your keyring updated without attempting
 connections to a remote host, you want to make sure that OpenSSH can
 still see the most recent trusted information about who the various

-hosts are.  You might also want the Monkeysphere to check on hosts
-that were not originally in the monkeysphere, to see if their host key
-is now published.
+hosts are.  You might also want to check on hosts that were not
+originally in the Monkeysphere, to see if their host key is now
+published.

 
 You can do this kind of independent update with the
 `update-known_hosts` command:
 
 You can do this kind of independent update with the
 `update-known_hosts` command:


@@ -105,19 +105,19 @@ Note: Due to a limitation with gnupg, it is not currently possible to
 limit the domain scope properly, which means that if you fully trust
 an admin, you'll trust all their certifications.
 
 limit the domain scope properly, which means that if you fully trust
 an admin, you'll trust all their certifications.
 

-Because the Monkeysphre relies on GPG's definition of the OpenPGP web
-of trust, it is important to understand [how GPG calculates User ID
-validity for a key](/trust-models).
+Because the Monkeysphere currently relies on GPG's definition of the
+OpenPGP web of trust, it is important to understand [how GPG
+calculates User ID validity for a key](/trust-models).

 
 
 Miscellaneous
 -------------
 
 Users can also maintain their own `~/.ssh/authorized_keys` files with
 
 
 Miscellaneous
 -------------
 
 Users can also maintain their own `~/.ssh/authorized_keys` files with

-the Monkeysphere.  This is primarily useful for accounts on hosts that
-are not already systematically using the Monkeysphere for user
-authentication.  If you're not sure whether this is the case for your
-host, ask your system administrator.
+the Monkeysphere directly.  This is primarily useful for accounts on
+hosts that are not already systematically using the Monkeysphere for
+user authentication.  If you're not sure whether this is the case for
+your host, ask your system administrator.

 
 If you want to do this as a regular user, use the
 `update-authorized_keys` command:
 
 If you want to do this as a regular user, use the
 `update-authorized_keys` command: