[PATCH] Fix some typos

[Kris Katterjohn <kjak () ispwest com>]

There are two patches attached. spelling-comments.patch fixes some typos
in the comments of the sources. spelling-docs.patch fixes typos in
HACKING and docs/nmap.1

I figured typos in the docs would be fixed but nobody really cares about
typos in the comments, hence the separate patches.

(The typo in nmap.1 is "octects" instead of "octets". It's a big line so
I thought I'd save you the trouble of finding the word.)

They're diffs against 4.20ALPHA5

Thanks,
Kris Katterjohn

--- x/idle_scan.cc      2006-08-28 22:26:10.000000000 -0500
+++ y/idle_scan.cc      2006-09-01 14:17:33.000000000 -0500
@@ -5,7 +5,7 @@
  * completely blind scanning (eg no packets sent to the target from your   *
  * own IP address) and can also be used to penetrate firewalls and scope   *
  * out router ACLs.  This is one of the "advanced" scans meant for         *
- * epxerienced Nmap users.                                                 *
+ * experienced Nmap users.                                                 *
  *                                                                         *
  ***********************IMPORTANT NMAP LICENSE TERMS************************
  *                                                                         *

--- x/idle_scan.h       2006-08-24 20:47:58.000000000 -0500
+++ y/idle_scan.h       2006-09-01 14:17:36.000000000 -0500
@@ -5,7 +5,7 @@
  * completely blind scanning (eg no packets sent to the target from your   *
  * own IP address) and can also be used to penetrate firewalls and scope   *
  * out router ACLs.  This is one of the "advanced" scans meant for         *
- * epxerienced Nmap users.                                                 *
+ * experienced Nmap users.                                                 *
  *                                                                         *
  ***********************IMPORTANT NMAP LICENSE TERMS************************
  *                                                                         *

--- x/protocols.cc      2006-08-24 20:47:59.000000000 -0500
+++ y/protocols.cc      2006-09-01 14:17:16.000000000 -0500
@@ -195,7 +195,7 @@ struct protoent *nmap_getprotbynum(int n
   
 }
 
-/* Be default we do all prots 0-255. */
+/* By default we do all prots 0-255. */
 struct scan_lists *getdefaultprots(void) {
   int protindex = 0;
   struct scan_lists *scanlist;

--- x/service_scan.cc   2006-08-28 23:03:13.000000000 -0500
+++ y/service_scan.cc   2006-09-02 20:00:41.000000000 -0500
@@ -983,7 +983,7 @@ void ServiceProbe::setPortVector(vector<
   // SERVICE_TUNNEL_SSL.  Otherwise use SERVICE_TUNNEL_NONE.  The line
   // number is requested because this function will bail with an error
   // (giving the line number) if it fails to parse the string.  Ports
-  // are a comma seperated list of ports and ranges
+  // are a comma separated list of ports and ranges
   // (e.g. 53,80,6000-6010).
 void ServiceProbe::setProbablePorts(enum service_tunnel_type tunnel,
                                    const char *portstr, int lineno) {
@@ -1053,7 +1053,7 @@ void ServiceProbe::addMatch(const char *
 }
 
 // Parses the given nmap-service-probes file into the AP class
-/* Must NOT be static because I have externam maintenance tools (servicematch)
+/* Must NOT be static because I have external maintenance tools (servicematch)
   which use this */
 void parse_nmap_service_probe_file(AllProbes *AP, char *filename) {
   ServiceProbe *newProbe;

--- x/service_scan.h    2006-08-24 20:47:59.000000000 -0500
+++ y/service_scan.h    2006-09-02 20:00:51.000000000 -0500
@@ -253,7 +253,7 @@ class ServiceProbe {
   // SERVICE_TUNNEL_SSL.  Otherwise use SERVICE_TUNNEL_NONE.  The line
   // number is requested because this function will bail with an error
   // (giving the line number) if it fails to parse the string.  Ports
-  // are a comma seperated list of ports and ranges
+  // are a comma separated list of ports and ranges
   // (e.g. 53,80,6000-6010).
   void setProbablePorts(enum service_tunnel_type tunnel,
                        const char *portstr, int lineno);

--- x/tcpip.h   2006-08-28 22:26:10.000000000 -0500
+++ y/tcpip.h   2006-09-02 20:01:06.000000000 -0500
@@ -505,7 +505,7 @@ bool route_dst(const struct sockaddr_sto
    be set to 1 if dst is directly connected on the ifentry network and
    0 if it requires routing.  If nexthop_ip is not NULL, and routing
    is required, the next hop is filled into nexthop_ip.  This function
-   returns false if no apporpiate interface or route was found and
+   returns false if no appropiate interface or route was found and
    true if it succeeds. */
 bool routethrough(const struct sockaddr_storage * const dest, 
                  struct intf_entry *ifentry, 

--- x/utils.cc  2006-08-28 22:26:10.000000000 -0500
+++ y/utils.cc  2006-09-02 20:00:00.000000000 -0500
@@ -195,7 +195,7 @@ char *strerror(int errnum) {
 }
 #endif
 
-/* Like the perl equivialent -- It removes the terminating newline from string
+/* Like the perl equivalent -- It removes the terminating newline from string
    IF one exists.  It then returns the POSSIBLY MODIFIED string */
 char *chomp(char *string) {
   int len = strlen(string);
@@ -388,7 +388,7 @@ unsigned int gcd_n_uint(int nvals, unsig
  }
 
 /* This function takes a command and the address of an uninitialized
-   char ** .  It parses the command (by seperating out whitespace)
+   char ** .  It parses the command (by separating out whitespace)
    into an argv[] style char **, which it sets the argv parameter to.
    The function returns the number of items filled up in the array
    (argc), or -1 in the case of an error.  This function allocates

--- x/HACKING   2005-12-29 22:26:54.000000000 -0600
+++ y/HACKING   2006-09-02 20:21:47.000000000 -0500
@@ -32,7 +32,7 @@ to track down and patch a problem, bug r
 Hackers interested in something more major, such as a new feature, are
 encouraged to send a mail describing their plans to
 nmap-dev () insecure org .  This is a good way to solicit feedback on
-your proposals.  List members or often very willing to help.  You
+your proposals.  List members are often very willing to help.  You
 might want to subscribe to that mailing list as well -- send a blank
 email to nmap-dev-subscribe () insecure org .  While you are at it, you
 might also want to subscribe to nmap-hackers via the same mechanism.

--- x/docs/nmap.1       2006-08-31 19:50:33.000000000 -0500
+++ y/docs/nmap.1       2006-09-02 20:21:19.000000000 -0500
@@ -195,7 +195,7 @@ are the same as for the reference IP or 
 11000000 10101000 00001010 00000000) and 192.168.10.255 (binary:
 11000000 10101000 00001010 11111111), inclusive. 192.168.10.40/24 would do exactly the same thing. Given that the host 
scanme.nmap.org is at the IP address 205.217.153.62, the specification scanme.nmap.org/16 would scan the 65,536 IP 
addresses between 205.217.0.0 and 205.217.255.255. The smallest allowed value is /1, which scans half the Internet. The 
largest value is 32, which scans just the named host or IP address because all address bits are fixed.
 .PP
-CIDR notation is short but not always flexible enough. For example, you might want to scan 192.168.0.0/16 but skip any 
IPs ending with .0 or .255 because they are commonly broadcast addresses. Nmap supports this through octet range 
addressing. Rather than specify a normal IP address, you can specify a comma separated list of numbers or ranges for 
each octet. For example, 192.168.0\-255.1\-254 will skip all addresses in the range that end in .0 and or .255. Ranges 
need not be limited to the final octects: the specifier 0\-255.0\-255.13.37 will perform an Internet\-wide scan for all 
IP addresses ending in 13.37. This sort of broad sampling can be useful for Internet surveys and research.
+CIDR notation is short but not always flexible enough. For example, you might want to scan 192.168.0.0/16 but skip any 
IPs ending with .0 or .255 because they are commonly broadcast addresses. Nmap supports this through octet range 
addressing. Rather than specify a normal IP address, you can specify a comma separated list of numbers or ranges for 
each octet. For example, 192.168.0\-255.1\-254 will skip all addresses in the range that end in .0 and or .255. Ranges 
need not be limited to the final octets: the specifier 0\-255.0\-255.13.37 will perform an Internet\-wide scan for all 
IP addresses ending in 13.37. This sort of broad sampling can be useful for Internet surveys and research.
 .PP
 IPv6 addresses can only be specified by their fully qualified IPv6 address or hostname. CIDR and octet ranges aren't 
supported for IPv6 because they are rarely useful.
 .PP


_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org