Description: spelling errors in binary (lintian)
 fix spelling errors / typos
Author: Roberto Lumbreras

Index: iperf-2.1.8+dfsg1/src/socket_io.c
===================================================================
--- iperf-2.1.8+dfsg1.orig/src/socket_io.c	2023-01-04 11:49:13.416510204 +0100
+++ iperf-2.1.8+dfsg1/src/socket_io.c	2023-01-04 11:49:13.412510220 +0100
@@ -211,7 +211,7 @@
 	case SOCKET_ERROR :
 	    if (!(errno == EINTR) || (errno == EAGAIN) || (errno == EWOULDBLOCK)) {
 		nwritten = inLen - nleft;
-		WARN_errno(1, "writen fatal");
+		WARN_errno(1, "written fatal");
 		sInterupted = 1;
 		goto DONE;
 	    }
Index: iperf-2.1.8+dfsg1/man/iperf.1
===================================================================
--- iperf-2.1.8+dfsg1.orig/man/iperf.1	2023-01-04 11:49:13.416510204 +0100
+++ iperf-2.1.8+dfsg1/man/iperf.1	2023-01-04 11:49:13.412510220 +0100
@@ -64,7 +64,8 @@
 output the report or error message to this specified file
 .TP
 .BR "    \-\-permit\-key [=" \fI<value>\fR "]"
-Set a key value that must match for the server to accept traffic on a connection. If the option is given without a value on the server a key value will be autogenerated and displayed in its initial settings report. The lifetime of the key is set using \-\-permit\-key\-timeout and defaults to twenty seconds. The value is required on clients. The value will also be used as part of the transfer id in reports. The option set on the client but not the server will also cause the server to reject the client's traffic. TCP only, no UDP support.
+Set a key value that must match for the server to accept traffic on a connection. If the option is given without a value on the server a key value will be autogenerated and displayed in its initial settings report. The lifetime of the key is set using \-\-permit\-key\-timeout and defaults to twenty seconds. The value is required on clients. The value will also be used as part of the transfer id in reports.
+The option set on the client but not the server will also cause the server to reject the client's traffic. TCP only, no UDP support.
 .TP
 .BR \-p ", " \-\-port " \fIm\fR[\-\fIn\fR]"
 set client or server port(s) to send or listen on per \fIm\fR (default 5001) w/optional port range per m\-n (e.g. \-p 6002\-6008) (see NOTES)
@@ -819,7 +820,7 @@
 .P
 .B Histograms and non\-parametric statisitics:
 The \-\-histograms option provides the raw data where nothing is averaged. This is useful for non\-parametric
-distribtions, e.g. latency. The standard output does use the central limit theorem to produce average,
+distributions, e.g. latency. The standard output does use the central limit theorem to produce average,
 mininimum, maximum and variation. This loses information when the underlining distribution is not gaussian.
 Histograms are supported so this information is made available.
 .P
@@ -827,7 +828,7 @@
 Binding
 is done at the logical level of port and ip address (or layer 3) using the \-B option
 and a colon as the separator between port and the ip addr. Binding at the
-device (or layer 2) level requires the percent (%) as the delimeter (for both the client and the server.)
+device (or layer 2) level requires the percent (%) as the delimiter (for both the client and the server.)
 An example for src port and ip address is \-B 192.168.1.1:6001. To \fBbind the src port only\fR and
 let the operating system choose the source ip address use 0.0.0.0, e.g.
 \fB\-B 0.0.0.0:6001\fR. On the client, the \-B option affects the \fBbind\fR(2)
@@ -895,7 +896,8 @@
 shows the 3WHS took 1.84 milliseconds.
 .P
 .B Port\-range
-Port ranges are supported using the hyphen notation, e.g. 6001\-6009. This will cause multiple threads, one per port, on either the listener/server or the client. The user needs to take care that the ports in the port range are available and not already in use per the operating system. The \-P is supported on the client and will apply to each destination port within the port range. Finally, this can be used for a workaround for Windows UDP and \-P > 1 as Windows doesn't dispatch UDP per a server's connect and the quintuple.
+Port ranges are supported using the hyphen notation, e.g. 6001\-6009. This will cause multiple threads, one per port, on either the listener/server or the client. The user needs to take care that the ports in the port range are available and not already in use per the operating system. The \-P is supported on the client and will apply to each destination port within the port range.
+Finally, this can be used for a workaround for Windows UDP and \-P > 1 as Windows doesn't dispatch UDP per a server's connect and the quintuple.
 .P
 .B Packet per second (pps) calculation
 The packets per second calculation is done as a derivative, i.e. number of packets divided by
Index: iperf-2.1.8+dfsg1/src/Client.cpp
===================================================================
--- iperf-2.1.8+dfsg1.orig/src/Client.cpp	2023-01-04 11:49:13.416510204 +0100
+++ iperf-2.1.8+dfsg1/src/Client.cpp	2023-01-04 12:06:42.387285102 +0100
@@ -1,6 +1,6 @@
 /*---------------------------------------------------------------
  * Copyright (c) 1999,2000,2001,2002,2003
- * The Board ofraTrustees of the University of Illinois
+ * The Board of Trustees of the University of Illinois
  * All Rights Reserved.
  *---------------------------------------------------------------
  * Permission is hereby granted, free of charge, to any person
@@ -953,7 +953,7 @@
 	    reportstruct->sentTime = reportstruct->packetTime;
 	    reportstruct->packetLen = writen(mySocket, mSettings->mBuf, writelen, &reportstruct->writecnt);
 	    if (reportstruct->packetLen <= 0) {
-		WARN_errno((reportstruct->packetLen < 0), "event writen()");
+		WARN_errno((reportstruct->packetLen < 0), "event written()");
 		if (reportstruct->packetLen == 0) {
 		    peerclose = true;
 		}
