The description is rewritten from scratch based on the reviewer understanding. It's a good approach, but you must consider that the author of that class has spend maybe an hour, maybe more creating a description - he doesn't do this often :)
The solution would be to insert at the bottom of the rewritten description something like: Author description (one, two sentences).
Manuel Lemos - 2011-10-26 21:34:46 - In reply to message 1 from Dan Negrea
That would be often redundant and confusing for the user.
The only case where the original description is kept is when it is not in English and the class does something specific for some country.
In most cases the descriptions entered by the author are not objective. Often they contain hype and big claims about what the class does, or do not tell what the class does in enough detail, and that is not helpful for the user because he the user needs to figure if the class is useful without looking at the code and often the original description of the author does not allow that.
For authors that want to keep their original descriptions for some reason, they are free to add read me files to the packages so what they want to pass to the user is preserved.
Manuel Lemos - 2011-10-27 00:49:03 - In reply to message 3 from Dan Negrea
If you feel that a class was approved with a description that needs to be improved somehow, you can always edit the description. Your description changes will be moderated and if they make the description better they will be approved.