From 5b3e0298746b248eff103f5fe5c9f5654a0a0405 Mon Sep 17 00:00:00 2001 From: wiz Date: Wed, 14 May 2003 13:10:57 +0000 Subject: [PATCH] setup -> set up. --- crypto/dist/ssh/ssh-agent.1 | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/crypto/dist/ssh/ssh-agent.1 b/crypto/dist/ssh/ssh-agent.1 index 0e82a7e0a9e9..42b15897f46e 100644 --- a/crypto/dist/ssh/ssh-agent.1 +++ b/crypto/dist/ssh/ssh-agent.1 @@ -1,4 +1,4 @@ -.\" $NetBSD: ssh-agent.1,v 1.13 2003/04/03 06:21:35 itojun Exp $ +.\" $NetBSD: ssh-agent.1,v 1.14 2003/05/14 13:10:57 wiz Exp $ .\" $OpenBSD: ssh-agent.1,v 1.37 2003/03/28 10:11:43 jmc Exp $ .\" .\" Author: Tatu Ylonen @@ -134,7 +134,7 @@ However, the connection to the agent is forwarded over SSH remote logins, and the user can thus use the privileges given by the identities anywhere in the network in a secure way. .Pp -There are two main ways to get an agent setup: +There are two main ways to get an agent set up: Either the agent starts a new subcommand into which some environment variables are exported, or the agent prints the needed shell commands (either