summaryrefslogtreecommitdiff
path: root/man/man1/monkeysphere-ssh-proxycommand.1
diff options
context:
space:
mode:
Diffstat (limited to 'man/man1/monkeysphere-ssh-proxycommand.1')
-rw-r--r--man/man1/monkeysphere-ssh-proxycommand.18
1 files changed, 4 insertions, 4 deletions
diff --git a/man/man1/monkeysphere-ssh-proxycommand.1 b/man/man1/monkeysphere-ssh-proxycommand.1
index 0e6d18d..a31a9d1 100644
--- a/man/man1/monkeysphere-ssh-proxycommand.1
+++ b/man/man1/monkeysphere-ssh-proxycommand.1
@@ -19,7 +19,7 @@ or by adding the following line to your ~/.ssh/config script:
.B ProxyCommand monkeysphere-ssh-proxycommand %h %p
The script can easily be incorporated into other ProxyCommand scripts
-by calling it with the "--no-connect" option, ie:
+by calling it with the "--no-connect" option, i.e.:
.B monkeysphere-ssh-proxycommand --no-connect "$HOST" "$PORT"
@@ -34,10 +34,10 @@ either the user's keyring or in the known_hosts file, then the
keyserver is queried for the host userID. If the host userID is found
in the user's keyring, then the keyserver is not checked. This
assumes that the keyring is kept up-to-date, in a cron job or the
-like, so that revokations are properly handled. If the host userID is
+like, so that revocations are properly handled. If the host userID is
not found in the user's keyring, but the host is listed in the
known_hosts file, then the keyserver is not checked. This last policy
-might change in the future, possibly by adding a defered check, so
+might change in the future, possibly by adding a deferred check, so
that hosts that go from non-monkeysphere-enabled to
monkeysphere-enabled will be properly checked.
@@ -57,6 +57,6 @@ Written by Jameson Rollins <jrollins@fifthhorseman.net>
.SH SEE ALSO
-.BR monkeypshere (1),
+.BR monkeysphere (1),
.BR ssh (1),
.BR gpg (1)