tidy-up: avoid word 'simply'

Cherry-picked from #1017

docs/INSTALL_AUTOTOOLS

@@ -37,7 +37,7 @@ file `config.log' containing compiler output (useful mainly for
 debugging `configure').
 
    It can also use an optional file (typically called `config.cache'
-and enabled with `--cache-file=config.cache' or simply `-C') that saves
+and enabled with `--cache-file=config.cache' or shortly `-C') that saves
 the results of its tests to speed up reconfiguring.  (Caching is
 disabled by default to prevent problems with accidental use of stale
 cache files.)

docs/libssh2_sftp_readdir_ex.3

@@ -30,7 +30,7 @@ truncated to fit.
 \fIlongentry_maxlen\fP bytes to read data into. The format of the `longname'
 field is unspecified by SFTP protocol. It MUST be suitable for use in the
 output of a directory listing command (in fact, the recommended operation for
-a directory listing command is to simply display this data).
+a directory listing command is to display this data).
 
 \fIlongentry_maxlen\fP - is the length of longentry in bytes. If the length of
 the full directory entry is longer than the space provided by

docs/libssh2_sftp_seek.3

@@ -21,8 +21,8 @@ Deprecated function. Use \fIlibssh2_sftp_seek64(3)\fP instead!
 Move the file handle's internal pointer to an arbitrary location.
 Note that libssh2 implements file pointers as a localized concept to make
 file access appear more POSIX like. No packets are exchanged with the server
-during a seek operation. The localized file pointer is simply used as a
+during a seek operation. The localized file pointer is used as a convenience
-convenience offset during read/write operations.
+offset during read/write operations.
 .SH SEE ALSO
 .BR libssh2_sftp_open_ex(3),
 .BR libssh2_sftp_seek64(3)

docs/libssh2_sftp_seek64.3

@@ -19,8 +19,8 @@ libssh2_sftp_seek64(LIBSSH2_SFTP_HANDLE *handle,
 Move the file handle's internal pointer to an arbitrary location. libssh2
 implements file pointers as a localized concept to make file access appear
 more POSIX like. No packets are exchanged with the server during a seek
-operation. The localized file pointer is simply used as a convenience offset
+operation. The localized file pointer is used as a convenience offset during
-during read/write operations.
+read/write operations.
 
 You MUST NOT seek during writing or reading a file with SFTP, as the internals
 use outstanding packets and changing the "file position" during transit will

docs/libssh2_sftp_write.3

@@ -56,8 +56,7 @@ otherwise block. While LIBSSH2_ERROR_EAGAIN is a negative number, it is not
 really a failure per se.
 
 If this function returns 0 (zero) it should not be considered an error, but
-simply that there was no error but yet no payload data got sent to the other
+that there was no error but yet no payload data got sent to the other end.
-end.
 .SH ERRORS
 \fILIBSSH2_ERROR_ALLOC\fP -  An internal memory allocation call failed.
 

src/transport.c

@@ -696,7 +696,7 @@ int _libssh2_transport_read(LIBSSH2_SESSION * session)
             numbytes -= numdecrypt;
         }
 
-        /* if there are bytes to copy that aren't decrypted, simply
+        /* if there are bytes to copy that aren't decrypted,
            copy them as-is to the target buffer */
         if(numbytes > 0) {
 

src/userauth.c

@@ -1475,9 +1475,8 @@ _libssh2_userauth_publickey(LIBSSH2_SESSION *session,
             session->userauth_pblc_method_len = _libssh2_ntohu32(pubkeydata);
 
             if(session->userauth_pblc_method_len > pubkeydata_len - 4)
-                /* the method length simply cannot be longer than the entire
+                /* the method length cannot be longer than the entire passed
-                   passed in data, so we use this to detect crazy input
+                   in data, so we use this to detect crazy input data */
-                   data */
                 return _libssh2_error(session,
                                       LIBSSH2_ERROR_PUBLICKEY_UNVERIFIED,
                                       "Invalid public key");