Merge branch 'NetHack-3.6.2-beta01' into NetHack-3.6.2

DEVEL/Developer.txt

@@ -62,7 +62,7 @@ NOTE: The following instructions require perl.  If you do not have perl on
 A. If you have never set up git on this machine before:
    (This assumes you will only be using git for NetHack.  If you are going to
    use it for other projects as well, think before you type.)
-	Tell git what name (or nicname) and email address to use for you:
+	Tell git what name (or nickname) and email address to use for you:
 		git config --global user.name "MY NAME"
 		git config --global user.email USER@EXAMPLE.COM
    You probably want to set up a credential cache.

DEVEL/code_features.txt

@@ -20,7 +20,7 @@ Here's how to do it:
      - The example above will alert the users for a new feature
        added in 3.6.0 via a one-liner via pline(), but you
        could get more elaborate (just make sure it is all done
-       in the 'if' code block..
+       in the 'if' code block.
 
 Once the user finds the alert no longer useful, or becoming 
 annoying, they can set the "suppress_alert" option.
@@ -75,7 +75,7 @@ There is a fqn_prefix[] entry for holding the path to each of the following:
 To recap, they are about enabling "different paths for different things", and
 separation of:
 - read-only stuff from read-write stuff.
-- sysadmin stuff from user-writeable stuff.
+- sysadmin stuff from user-writable stuff.
 etc.
 
 ==============================================

DEVEL/code_style.txt

@@ -16,7 +16,7 @@ declarations. Due to some incompatibilities, the patch is not publicly
 available and clang-format is not expected to be regularly used.
 
 Developers should do their best to adhere to the coding style to promote
-legibile, easy-to-edit code. Legibility is paramount, so in some cases, it may
+legible, easy-to-edit code. Legibility is paramount, so in some cases, it may
 be better not to fully adhere to the style guidelines.
 
 Recipes for common text editors can be found at the end of this file.
@@ -30,7 +30,7 @@ characters, not tabs.
 Lines should be at most 78 characters wide. If a line would be longer than the
 limit, the line should be wrapped and the wrapped portion should be aligned
 with the parentheses or brackets containing the wrap. If there is no set of
-parenthese or brackets, the line should be indented four spaces. Wrapping
+parentheses or brackets, the line should be indented four spaces. Wrapping
 should normally occur after a comma or before a binary operator, when
 possible:
 
@@ -43,7 +43,7 @@ possible:
 
 Single blank lines should be used wherever convenient to improve readability.
 
-Functions and Control Satements
+Functions and Control Statements
 -------------------------------
 
 For a function definition, the return type, declarator, and opening brace
@@ -183,10 +183,10 @@ many entries that reproducing them here is impractical. Fortunately, the
 options are in plain English, so walking through them with a copy of 
 this Guide handy and making changes as required will suffice.
 
-emacs Configuration
+Emacs Configuration
 ===================
 
-There are no doubt umpteen different ways to handle this in emacs.
+There are no doubt umpteen different ways to handle this in Emacs.
 Putting the following in ~/.emacs.el is one
 
 (defun hook-c ()