From: David Abrahams <abrahams@[...]..> 
>  The only excuse for these acronyms, AFAICT, is that it gets cumbersome to
>  refer to a library as The Boost Foo Library over and over within the
>  library's own documentation. I didn't want an acronym for the Python lib,
>  but eventually found it hard to make the docs read easily without one. Can
>  anyone think of a good alternative?

We can take advantage of being within the Boost namespace within our docs
and just say things like See the Test library for me details, and look at
the cool Python library. I thinking capitalizing the name of the library
will make things clear enough.

Data point: When I posted my review with subject Review: Test library , was
there any ambiguity regarding what the review was of?