diff options
author | Aris Adamantiadis <aris@0xbadc0de.be> | 2010-01-06 21:12:00 +0100 |
---|---|---|
committer | Aris Adamantiadis <aris@0xbadc0de.be> | 2010-01-06 21:12:00 +0100 |
commit | 84e6aca5c523768653b751d2d770f0fedcbbe0a9 (patch) | |
tree | 7516d3c4306baf1783d9497d3e60c7ffd671a385 /libssh/channels1.c | |
parent | ebd09873768e872e765744bb07754fc9847e84d9 (diff) | |
download | libssh-84e6aca5c523768653b751d2d770f0fedcbbe0a9.tar.gz libssh-84e6aca5c523768653b751d2d770f0fedcbbe0a9.tar.xz libssh-84e6aca5c523768653b751d2d770f0fedcbbe0a9.zip |
Fixed typos from a* to error.c
Diffstat (limited to 'libssh/channels1.c')
-rw-r--r-- | libssh/channels1.c | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/libssh/channels1.c b/libssh/channels1.c index daa851c..54dc5a3 100644 --- a/libssh/channels1.c +++ b/libssh/channels1.c @@ -38,9 +38,9 @@ /* * This is a big hack. In fact, SSH1 doesn't make a clever use of channels. * The whole packets concerning shells are sent outside of a channel. - * Thus, an inside limitation of this behaviour is that you can't only + * Thus, an inside limitation of this behavior is that you can't only * request one shell. - * The question is stil how they managed to imbed two "channel" into one + * The question is still how they managed to embed two "channel" into one * protocol. */ @@ -276,7 +276,7 @@ int channel_handle1(ssh_session session, int type) { } break; default: - ssh_log(session, SSH_LOG_FUNCTIONS, "Unexepected message %d", type); + ssh_log(session, SSH_LOG_FUNCTIONS, "Unexpected message %d", type); } return 0; |