diff --git a/docs/nmap-install.xml b/docs/nmap-install.xml index 71eae11d2..c034be50d 100644 --- a/docs/nmap-install.xml +++ b/docs/nmap-install.xml @@ -509,7 +509,7 @@ for the most common distributions. RPM-based Distributions (Red Hat, Mandrake, Suse, Fedora) RPM Linuxinstalling on, with RPM> -Red Hat (Linux distribtion)installing on, with RPM> +Red Hat (Linux distribution)installing on, with RPM> Mandrake (Linux distribution)installing on, with RPM Suse (Linux distribution)installing on, with RPM Fedora (Linux distribution)installing on, with RPM @@ -571,7 +571,7 @@ reason there are no Zenmap source RPMs. Updating Red Hat, Fedora, Mandrake, and Yellow Dog Linux with Yum Yum Linuxinstalling on, with Yum -Red Hat (Linux distribtion)installing on, with Yum +Red Hat (Linux distribution)installing on, with Yum Mandrake (Linux distribution)installing on, with Yum Yellow Dog (Linux distribution)installing on, with Yum Fedora (Linux distribution)installing on, with Yum @@ -1165,7 +1165,7 @@ chapter referenced above. NetBSD Binary Package Instructions NetBSD, installing on -NetBSD has packaged Nmap for an enormous number of platforms, from the normal i386 to Playstation 2, PowerPC, VAX, SPARC, MIPS, Amiga, ARM, and several platforms that I have never even heard of! Unfortunately they are not very up-to-date. A list of NetBSD Nmap packages is available from and a description of using their package system to install applications is available at . +NetBSD has packaged Nmap for an enormous number of platforms, from the normal i386 to PlayStation 2, PowerPC, VAX, SPARC, MIPS, Amiga, ARM, and several platforms that I have never even heard of! Unfortunately they are not very up-to-date. A list of NetBSD Nmap packages is available from and a description of using their package system to install applications is available at . diff --git a/docs/refguide.xml b/docs/refguide.xml index 40cb4c1b3..542a7210d 100644 --- a/docs/refguide.xml +++ b/docs/refguide.xml @@ -2719,7 +2719,7 @@ lists the relevant options and describes what they do. MEME (decoy address) as one of the decoys to represent the position for your real IP address. If you put - ME in the 6th position or later, some + ME in the sixth position or later, some common port scan detectors (such as Solar Designer'sSolar Designer excellent Scanlogd)Scanlogd diff --git a/docs/scripting.xml b/docs/scripting.xml index 43f28016d..62ccb9fbb 100644 --- a/docs/scripting.xml +++ b/docs/scripting.xml @@ -2668,14 +2668,14 @@ nmap.get_port_state({ip="127.0.0.1"}, {number="80", protocol="tcp"}) The receive_buf method reads data from the network until it encounters the given delimiter - string (or matches the function passsed in). Only data + string (or matches the function passed in). Only data which occurs before the delimiter is returned, and the delimiter is then erased. This function continues to read from the network until the delimiter is found or the function times out. If data is read beyond the delimiter, that data is saved in a buffer for the next call to receive_buf. This buffer is - cleared on subsequent calls to other Network I/O APY + cleared on subsequent calls to other Network I/O API functions. The receive_buf method takes @@ -2702,7 +2702,7 @@ nmap.get_port_state({ip="127.0.0.1"}, {number="80", protocol="tcp"}) to receive_buf is a boolean value which indicates whether the delimiting pattern should be returned along with the received data or - discarded. The delimiter is included if true is passed as the keeppatern argument. + discarded. The delimiter is included if true is passed as the keeppattern argument. The return values of receive_buf are the same as the other receive* functions. A (status, val) tuple is returned. The status is true if the request was successful. The val variable contains the returned data, or an error message if the call failed.