Grammar and punctuation fixes.

doc/window.doc

@@ -177,7 +177,7 @@ int nhgetch()	-- Returns a single character input from the user.
 		   changed and also return ASCII 033 in this case.
 int nh_poskey(int *x, int *y, int *mod)
 		-- Returns a single character input from the user or a
-		   a positioning event (perhaps from a mouse).  If the
+		   positioning event (perhaps from a mouse).  If the
 		   return value is non-zero, a character was typed, else,
 		   a position in the MAP window is returned in x, y and mod.
 		   mod may be one of
@@ -602,7 +602,7 @@ getmsghistory(init)
 		   If init is TRUE, start over again from most recent message.
 
 putmsghistory(msg)
-		-- The is the counterpart to getmsghistory() for restores
+		-- This is the counterpart to getmsghistory() for restores
 		   used to reload the port's message recall buffer.
 		   The routine is called repeatedly from the core restore 
 		   routine, starting with the oldest message first, and
@@ -693,7 +693,7 @@ when processing options, either in the config file, or by the 'O' command.
 
 You may be wondering what values your window port will find in the 
 iflags.wc_* and iflags.wc2_* fields for options that the user has not 
-specified in his/her config file. Put another way, how does you port code
+specified in his/her config file. Put another way, how does your port code
 tell if an option has not been set? The next paragraph explains that.
 
 If the core does not set an option, it will still be initialized 
@@ -1068,7 +1068,7 @@ When writing a new window-port, you need to follow the following guidelines:
    WINOBJ (if you want the NetHack binary to include them, that is).
 
 9) Look at your port's portmain.c (the file containing main()) and make
-   sure that all of the calls match the the requirements laid out in
+   sure that all of the calls match the requirements laid out in
    Section VII.
 
 Now, proceed with compilation and installation as usual.  Don't forget