Mention that it's usually best to just treat ikeywords as a "transparent alias" for the plain keyword counterpart.
Explain how to seamlessly integrate ikeywords support in definitions-systems that the user is then free to use or not (using plain keywords instead).
Point out that ikeywords can be used in loop, avoiding both the use of plain keywords (which look unaesthetic to some (but not to me)) and the use of non-keyword symbols (which tends to intern arbitrary symbols in arbitrary packages).
Illustrate the various potential definition conflicts scenarios with examples.
Add while and unless built-in ikeywords with their obvious macro definitions. ikeywords normally never have any definitions in the standard namespaces but this would be a very convenient exception. Many DSLs could make good use of while and unless ikeywords, including loop, and being able to use the aforementioned macros without conflicts or additional effort would be a definite plus. It would be possible to make a library just for while and unless and I've been known to make some micro-libraries but in this case I think it would be a bit much, especially considering this convenient solution. It helps that there's only one obvious canonical definition of while and unless ((condition &body body), block nil, tagbody). Include a cleaned up version of this rationale in the documentation.