Presuming that the embedded, dev, and security docs will all be available as part of their respective code (javadocs and examples), that leaves admin, caching, and client-dev as the remaining books that need a spring specific spin.

Most of the admin guide is not applicable - but we do need to capture somewhere all of the information related to system/env properties

Most of the caching guide is TBD - but the sections on result set and other caching are still applicable.

Most of the client guide is applicable to spring.