Thomas -
How about (for example):
This chapter addresses migration concerns for users of VisualAge Smalltalk V5.5 or earlier who are migrating to the current release of VA Smalltalk.
or:
This chapter addresses migration concerns for users of VisualAge Smalltalk V5.5, and users of earlier versions who have completed the previous migration steps, who are migrating to the current release of VA Smalltalk
which I don't think reads as well, but is more accurate, and:
After you complete any needed migration steps described in this chapter, you should continue to the subsequent chapters of this document to review further migration requirements.
as a near-term 'course correction'?
For a longer-term approach, perhaps we could try turning each of the existing chapter introduction pages into a checklist that would include a list of all migration steps needed when migrating from that release to the current release (with links to the details as is there now). Them we could collect all the detail pages in a single chapter, arranged in some useful way. This reorg (or something similar) would not be a high-priority change (in my mind, at least) and is not something I can promise, but something we could evaluate.
John O'Keefe [|], Principal Smalltalk Architect, Instantiations Inc.