Sounds like a good idea to me.

I think ridding documentation of passive voice statements constitutes a good practice.

Passive voice, often performed using the "to be" verb, obscures actors and confuses the actor with the action. Additionally, in detailed program comments, using "to be" can confuse a variable, its type, and its contents or value. None of this confusion helps. We should banish passive voice, and "to be" along the way.