I haven't used CLR or researched it much, but as far as DML goes, surely CLR triggers would fall under the same logic as a traditional DML trigger:

1. do [action] AFTER insert/update/delete

OR

2. do [action] INSTEAD OF insert/update/delete

The CLR bit as far as I can see is just an alternative to T-SQL. Where it appears in BOL is not necessarily an indication of correctness as far as this QoD goes, seeing as CLR triggers can be either DML or DDL. Perhaps BOL should state 'DML|DDL triggers can be written in either T-SQL or CLR'.

/Edit: must stop using gt/lt brackets, they get stripped out.