We should take some extra care to polish the final document that we send out for publication.

To do so, I recommend that we make final, ad-hoc adjustments in a separate branch that we never merge into master and that contain changes that we wouldn't normally make since they are very brittle.

Specifically, I have something like this in mind:

1. Fork off the IS release branch
2. Change page headers and footers to match the intended final configuration, switch out the cover sheet, add the Foreword page from n4141 (see C++ Editors folder on Google Drive).
3. Remove all pagebreak-like breaks from the document: \newpage, \pagebreak, \clearpage. (Are there any more?)
4. Leaf through the entire document to make sure that the overall presentation is OK (e.g. avoid problems like in figure out what's wrong with the "Allocator requirements" table and prevent it ever happening again #1571), but also paying particular attention to vertical details:
   • Floats are not too dense and not too far from their reference point. Most of our floats have "h" placement, so we don't expect them to build up. If there's pressure, add a \clearpage. Here-floats should probably not leak into the next section.
   • Check if the TOC has a clause heading on the last line of the page. Not sure how we could fix this; perhaps we can add some leading whitespace before the beginning of the TOC.
   • Check if synopses have page breaks in them that split multiline declarations. Synopses often offer opportunities for whitespace insertion or removal to move things around a bit.
   • Check if footnote are split across multiple pages.
   • Least of all, see if other page elements are unduly separated by an intervening page break: itemdecls, itemdescrs, examples. We may not have a lot of options there, but a judicious page break here or there may well improve things.

The review work can probably be executed in parallel, one clause at a time, since there is no vertical correlation across clause boundaries.

Pre-fork ideas (work that can be done on the master branch):

• Double check overfull and underfull boxes.
• Spellcheck?
• Check all logs for errors and warnings.
• Think about font substitutions.