improve remarks about and inside the config file

README.markdown

@@ -32,7 +32,7 @@ Savegame directory
 
 If you don't want LambdaHack to write to the current directory,
 create a personal savegame directory (on Linux it's ~/.LambdaHack/).
-and also copy the LambdaHack.scores file there. You may also want to
+and copy the LambdaHack.scores file there. You may also want to
 copy the configuration file src/LambdaHack.config.default to
 ~/.LambdaHack/LambdaHack.config and modify it, but be careful changing
 gameplay options --- they can easily unbalance or break the game.

src/LambdaHack.config.default

@@ -4,10 +4,9 @@
 ; options are case-sensitive and permitting only ';' comments.
 
 ; If you contribute to LambdaHack, please create directory ~/.LambdaHack/
-; and move this example config file to ~/.LambdaHack/LambdaHack.config.
-; Optionally, also copy LambdaHack.scores to ~/.LambdaConfig/.
-; In this way, you won't accidentally commit your private high scores
-; (nor your save files) to LambdaHack git repository.
+; as described in README.markdown. In this way, you will not accidentally
+; commit your private high scores (nor your save files) to LambdaHack
+; git repository.
 
 [dungeon]
 ; the hardcoded default for levels with no specified layout:
@@ -41,9 +40,10 @@ extraHeroes: 0
 firstDeathEnds: False
 
 [macros]
-; throw a dart at the closest monster
+; TODO: the following does not work yet:
+; ; throw a dart at the closest monster
 ; t: asterisk Return t Return
-; TODO: the above does not work yet; in gtk can be done via unGetChan,
+; TODO: in gtk it could be implemented via unGetChan,
 ; unless we prefer an explicit command queue, with flushing, etc.
 ;
 ; NetHack compatibility