Corrections
A wrong number on a reference site is worth fixing fast. Here is how.
Check the stamp first
Every page carries a build stamp: the patch it was read from and the date it was read. If the game has patched since that date, the page is waiting on its next pull, and the value you are looking at is the last build's, not the current one. That is the most common "wrong number", and it fixes itself when the next build lands.
What a correction can fix
Every game fact is generated from the game files, so a genuine error there is almost always one of two things: a decode that read a column wrong, or a join that paired the wrong rows. Both are fixable at the source and, once fixed, correct every page that shares the fault. A value that simply differs from another fan site is not necessarily wrong: Deadlock Shop shows what the current client contains, and other sites are often a patch or two behind.
The "counters", "most-bought build" and "ability order" sections on each hero page, the "in matches" and "Heroes who buy" sections on each item page, the "in matches" section on each ability page, and the measured columns on the heroes and items lists are the exception: their rates are measured from matches by deadlock-api.com, not read from the files. If one looks wrong, it can be checked against the exact query and match counts recorded with the snapshot it came from, as the methodology describes.
How to report one
Email hello@vient.org. The most useful report names the entity, the field, the value shown, and the value you expected, so it can be traced back to the exact table and row. A fix ships with the site's next deploy, usually the day it is merged, and is listed in the log below with that date. The "Synced" date on a page only moves when a new game build is read, so it does not show a correction.
Corrections log
Every fix to a number, label or claim already live on this site, newest first, with the date it shipped.
Was: Slows and debuffs in ability tier bonuses and corrupted item bonuses printed with a plus sign or no sign, so a slow read as a buff (Fixation tier 1 read "+12% Move Speed").
Now: They print with their minus sign, as the game file writes it ("-12% Move Speed").
Was: Item and ability stat units and signs were read from one of the client's text files only, so some dropped their unit (Colossus showed "25 Base Health" where the client says "+25% Base Health").
Now: Units and signs are read from every client text file.
Was: Clip size could read one lower than the game's rule, because it rounded down where the rule rounds up (Abrams with Extended Magazine showed 11 where the rule gives 12).
Now: Clip size follows the rule the methodology page names.
Was: Solomon's spirit damage was missing: the matchup lab said "No spirit damage value in the file." for Setup Bishop, Rook Battery and Develop Queen, and their Damage cells on his hero page were blank.
Now: The lab and the hero page both count it.
Was: The about, privacy and corrections pages listed less Valve art and fewer measured match data sections than the site served.
Now: They name every art family and every measured section.
Was: The matchup lab said "No spirit damage value in the file." for abilities whose file does hold one, Scrap Grenade among them.
Now: The lab models those values, and lists any it cannot model under "Not modelled".
Was: Max Health, bullets to kill and shots to kill could be 1 off from floating-point rounding (Abrams with Extra Stamina showed 873 where the formula gives 872).
Now: Rounding trims the floating-point error first, so each value matches its formula.