[dwalend]

I spotted two typos (through section 5)

2.01.1 no need for quotes around "clear" .

3.02 no need for quotes around “battlesuits” . Future Combat System articles used the term in the mainstream press.

The rest is bigger edits and just suggestions.

In p1's Section Numbering block - do you want to mention that some rules leave out information that does not apply tan-map Ogre?

If you've got room, consider adding MkIV Attack. It'd be an easy thing to add to the box. (And if you've got a lot of room, maybe even MkII Attack. It plays really fast.) (Will also change 3.04 Ogres section. And "Ogre types playable in this game:" And 3.4.2 will need missle rack rules. And 6.05. Ug. A MkIV will fill about a 1/4 page.)

Will there be terrain overlays in the box?

3.01 "Howitzer (HWZ). A non-self-propelled heavy missile cannon. " Maybe "A large immobile railgun" ? If you can avoid "missile" then you'll bypass confusion with ogre missiles. "Non-self-propelled" is pretty awkward, and almost implies it can be towed or something.

"GEVs may move twice per turn." Mabye "GEVs move both before and after their fire phase. See 5.05"

Consider dropping "Terrain affects GEVs differently from other units; in particular, they can cross water (though there is no water on the basic Ogre map)." if you need an extra 1/4" .

3.04 "Note that the two Mark III Ogres have different colors on
the sensor sphere at the top of the tower to make them easy to
distinguish." - How about printing names on the models so they can be distinguished very easily? Or one has a red tower (not just the sphere) and one has a gold or black tower ?

4.02 - For the disabled phase - is it worth adding a note that a disabled unit must spend an entire next enemy fire phase disabled? it's pretty well covered in 7.11.

4.03 "Multiplayer sequencing. A scenario with more than one
player on a side will use a similar sequence; players move in the
same order each turn. Each player on side A, in turn, moves and
resolves combat; then each player on side B, in turn, moves and
resolves combat. Players on the same side may take a single fire
phase together, after the last one moves, in order to combine fire." - I've only ever done it the later way - Players on the same side share a movement phase, then a fire phase. Does everyone else do it as 4.03 says?

"5.05 GEV double movement." Change to "Second (GEV) movement phase." to exactly match 4.02.

Maybe drop the box about " change the facing on each unit as you move it" if you need the space. Same recommendation for 7.03. It's the same picture, twice. A roll of pennies works better.

Time to rescue the babysitter... now the kids are in their cages again...

"6.02 ... An Ogre loses two tread units (see 3.04.2) for ramming a Heavy
Tank, and one tread unit for ramming any other armor unit." It might be better to list out the other units in this set - GEV, MSL and HWZ - to be a bit more compatible with the full set of units.

"7.13.3 Destroying Ogres. An Ogre is not destroyed until all
its firable weapons and tread units are gone. However, a lone,
immobile Ogre is helpless; at that point, the game is as good as over." Maybe rephrase as positive: "An Ogre is destroyed when all of its firable weapons and tread units are gone." Maybe drop the "however" sentence. The players will figure that out. An M0 Ogre might just be in SB range of the command post.

page 11 example of play. How the heck is the Ogre half way through M2, missing two SBs and 3 APs, but still has its main gun? Shouldn't a master sergeant offer the defense commander some stern advice before that?