Some of the positive things I have to say about P6 doc are in my Perl 6 documentation post which I updated last month.

Larry Wall recently gained employment (with Craig's List) that frees him to focus on P6 spend (more) time on writing the P6 Camel. (In case it isn't clear, he's the one who said he'd write it, not me. I'm not promising. Just anticipatin'.)

To help him on his way, the P6 Camel draft, ie. the specs, got a lot of love in 2013:

• lizmat (who, to post something out of context, is a well loved winner of one of this year's White Camel awards) decided to spend 8 months (so far) systematically reading, correcting and clarifying the entire series of spec documents -- while learning and hacking on the core to boot. Thank you lizmat!

• FROGGS, lizmat, et al are most of the way through a nearly year long process of redoing/elaborating the design of, and fully implementing, S11: Units and Modules.

• lue recently drafted the all new S15: Unicode. (NB. Unlike with the new S11, S17, and S21, implementation in Rakudo of S15 has barely begun.)

• jnthn landed an entirely new (and almost entirely implemented on JVM) S17: Concurrency. It's a lot cleaner than its predecessor.

• S21: Calling foreign code was basically replaced this year by the much cleaner documentation for Rakudo's already implemented foreign code calling facility Zavolaj.

• etc.

I just remembered another significant doc improvement from 2013: the materials from the 2 day NQP workshop. With this we went from having very skimpy documentation of NQP, a key piece of the Rakudo compiler toolchain, to having sufficient documentation that folk who didn't attend the workshop can get up to speed on NQP.

I'm sure I'm missing some other stuff but I think I'm done with this current round of exchanges with you. Feel free to make some closing comments. :)