How Plugin Pages Are Written
Where a plugin's description comes from, and how we check it.
A plugin's product page is written to sell it. The manual is written to explain it: what each control is called, what it does, the real ranges and modes. So when a plugin has a manual, that's what we write its page from.
Written from the manual, then checked against it
The description and the feature list on a plugin's page are written from the maker's manual. Before the page goes up, every claim in them is checked against that same manual. If something isn't backed up there, the page doesn't go up. That means a feature the plugin doesn't have, a number that's wrong, a control that isn't there, or anything the manual contradicts.
Pages written this way say so, just under the description: Written from the manual and checked against it. You'll find a link to the manual itself in the panel beside it.
Pages without that line
Some plugins have no manual we could find. For others, the manual is still being worked through. Those pages are written from the maker's product page instead, get the same check against it, and don't carry the line.
“We're updating this plugin's details”
Sometimes we find a page was written from the wrong document, or its check no longer holds. We take that write-up down everywhere, including on the plugin's page in your library, until a corrected one passes the check. While that happens you'll see this line instead of the description and features. The plugin stays in your library, and your notes, tags and rating are untouched.
Spotted something wrong?
The rest of the page — which DAW a device comes with, where to get it, and its formats — comes from the catalog, not from the description.