diff options
| author | Daniel Kahn Gillmor <dkg@fifthhorseman.net> | 2009-02-20 15:25:14 -0500 |
|---|---|---|
| committer | Daniel Kahn Gillmor <dkg@fifthhorseman.net> | 2009-02-20 15:25:14 -0500 |
| commit | 5d98461822dce7c8c0cfe1218decf2f6e7503f98 (patch) | |
| tree | 6b4e8287ef411167ade3bacdcf2b800847a373df | |
| parent | b876492913c3b1aabf08ff44250882d3b9c0b3ad (diff) | |
documentation tuning.
| -rw-r--r-- | website/advanced-user.mdwn | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/website/advanced-user.mdwn b/website/advanced-user.mdwn index ecb094b..138fd48 100644 --- 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 -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: |