So, more feedbacks on the next scenarios (
based on the txt files! 
); these are mainly details, but may still be worth noticing.
8 AnzB:
Brief:
-> Could replace the "1SSF" by the "
1SSF (namely the 1st Special Service Force, also known as "The Devil’s Brigade")"
-> “The British 1 Division, 2 and 3 Brigades” or maybe “The British 1st Division, 2nd and 3rd Brigades”?
-> “by 1 Division” or maybe “by British 1st Division”?
Unit name:
-> ”3d BN, 504th PIR” -> the “BN” becomes “Bn” (as usual)
-> “1SSFArty (2)” -> “1SSF Arty (2)” (space!; as for the previous unit on txt file)
-> “spawn_name_482 =” and “spawn_name_548 =” with nothing after on txt file!?
Could it be that one of those (maybe the first) is actually the “3rd Bn 6651 Rangers”?

(This one being mentioned in the event “Rangers Ambushed”!)
And no “2nd Bn 6651 Rangers” right now? (the 1st and 4th are named on map, the 3rd shall as well ‘cause event, so…)
Map:
“hex_1589 = 7th next objective” -> “hex_1589 = 7th Next Objective” (
by coherence with the other names; by the way, 2nd time a “7th Next Objective” will appear on map – but two hexes can have exactly the same name, right?)
Minor & Major Victories text:
“3d ID salvaged the beachhead” -> a space can be removed after “salvaged”
*******
9 AnzS:
Well, add the briefings…
Map:
“hex_1589 = 7th next objective” -> “hex_1589 = 7th Next Objective” (as before)
Event:
In Ressuply, “British 1 Brigade” or “British 1st Brigade”?
Next titles could be a little long, therefore there is always these options:
“45th Division Committed” -> “45th Div Committed”
“E Flank Roads Are Secure” -> “E Flank Roads Secured”
Endings:
-> Minor Defeat: “Beachhead saved, offensive stalled” -> put the first letter of each of these words as uppercase (as for all the other possibilities)
-> Minor Victory: “VI Corps salvaged the” -> a double space not required…
*******
10 AnzBO:
Briefs:
-> Brief parts -> “S-1”, then “s-2” (small “s”?), then only “Gs” (like “G-2 (Cont)”, etc.) -> maybe only (big) S…
-> “3d ID and 1st Armored divisions” -> some “divisional” redundancy… what about either “Our 3d Infantry and the 1st Armored divisions” or “Our 3d ID and the 1st Armored Division”?
-> “along Highway 6 (Valmonte t0 Finocchio on your battle maps.)” -> t0 (“zero“) like “to“ of course; why a plural for “map(s)”?; close the bracket before putting the “.”
Map:
“hex_1223 = GiulIanello” -> should be (
according to the texts of two events at least) “= Giulianello” (or it may be – less likely - the opposite, but write the same thing everywhere anyway)
“hex_908 = Galllicana” -> there should be one “l” too much…
“hex_1591 = via Cassino” or rather “=Via Cassino“?
hex_583 = 3rd Div Left Boundary; hex_867 = 3rd Div; hex_926 = 3rd Div; hex_984 = 3rd Div; hex_1147 = 3rd Div Right Boundary; hex_1386 = 3rd Division
-> Well, it should be about our “3d ID”, right? Then why not putting each time our “classical” terminology, the “3d ID” instead of “3rd Div” or even “3rd Division”?
Same consideration of the text of the events “Task Force Howze” and “Attack Plans Change”. (The next event talks again about our “3d ID”.)
On various locations, there is (for example) as names the “7th" or the “7th Regt”. Well (although the “t” is optional and should more likely be removed according to the previous scenarios), what about putting the same form every time?
Names:
“spawn_name_13 = 10th Army escapees” vs “spawn_name_15 = 10th Army Escapees” -> “Escapees” with or without uppercase? Both time the same…
Event: “Attack Plans Change!”
Text begins like: “Gen Mark Clark has directed that the main attack be redirected northwest toward the Alban Hills.”
-> Directed, redirected… Maybe “[…] has decided […]” or “[…] has ordered […]”
-> There is no hex named “Alban Hills” on this map…

Is it normal (like too far away, as a general direction of assault) or should it be added for “crystalclearness”

sakes?
'Hope it helps a little. Those scenarios look awesome!
