Correction: the Charlotte dashboard said it had never been updated, and it had
Corrected a Charlotte section that described itself as a first edition after the page had already been refreshed, removed an internal work note that was rendering to readers on the Dallas-Fort Worth page, and made one Dallas-Fort Worth figure consistent across a chart, prose, and an FAQ. No market figure and no Balance Score changed.
Three defects went live on the July 26 refresh. None changed a market figure or a Balance Score, but the first was a false statement about the page itself and is logged here as a correction rather than a routine edit.
The Charlotte dashboard contradicted itself about being a refresh. Its “What changed this month” section opened by saying “this is the first edition of this dashboard”, while the data freshness block lower down on the same page correctly said the page was first published July 15 and last refreshed July 26. Both statements were live at once. The refresh had updated the mortgage rate inside that section without updating the framing around it. The section now records what it is: a refresh, what moved in it, and what did not. It also separates the mortgage rate, which is a July 23 figure, from the May 2026 Canopy figures it had been listed among.
An internal work note was rendering to readers on the Dallas-Fort Worth page. The source registry showed, across nine rows, a parenthetical instructing a future editor to check one of our source files against the live original. That is a note to ourselves, not information for a reader, and it is now recorded where it belongs, on our internal backlog. In its place the page says once, in the freshness section, the thing a reader actually benefits from knowing: our Texas source republishes prior months as its data settles, and this edition carries the April 2026 values as first transcribed.
One Dallas-Fort Worth number was stated three ways. The gap between what a median local household earns and the income needed to buy the median home appeared as $32,524 in a chart, roughly $32,000 in the prose, and roughly $33,000 in an answer. The engine value is $32,524, which rounds to $33,000, so the chart keeps the exact figure and everything else now says $33,000.
We would rather log a framing error publicly than fix it quietly, which is what our corrections policy commits us to.
Related
Back to the full changelog, or report an error via our corrections policy.