X-Git-Url: http://winboard.nl/cgi-bin?a=blobdiff_plain;f=data%2Ffmax.ini;h=1eeb76af64a05c49c100a54186e1743e7cfdf638;hb=53a644a2c385aa2476f0d171ce997c818dfb7639;hp=4c7544830d6a2673d6edff6536ddba3369e6ffe9;hpb=4dd94d58a1a7f109ab9b77d73a9e3e028ae859ee;p=fairymax.git

diff --git a/data/fmax.ini b/data/fmax.ini
index 4c75448..1eeb76a 100644
--- a/data/fmax.ini
+++ b/data/fmax.ini
@@ -141,12 +141,12 @@ and the 2nd and 7th rank of the opening setup will be filled with them.
 These pieces will automatically promote to piece number 7 when they 
 reach last rank. So in normal Chess, piece 7 should be programmed as Queen.
 
-Castling currently can be done only with a piece number 6 in the corner,
-so in normal Chess you should program piece 6 as Rook. Any royal piece
-can in principle castle. (Subject to the normal restrictions on castling,
-i.e. not passing through check etc.) If you don't want that, remove the 
-castling moves from the King desription. If the castling initiator does 
-not start in a central file, the results are currently undefined.
+Castling can be done only with the original corner piece as specified
+by line 2 and 3. Any royal piece can in principle castle. (Subject to 
+the normal restrictions on castling, i.e. not passing through check etc.)
+If you don't want that, remove the castling moves from the King description. 
+If the castling initiator does not start in a central file, the results are 
+currently undefined.
 
 Most variant definitions can be seen at the end of this file.
 Other lines in this file (i.e. those not recognized as belonging to a