docs(viewer): correct the full table search row count claim

The row count next to the table name is the capped count, not the total
number of matches. A search that matches more rows than DC_MAXOBS_WEBVIEW
returns the first 500 and reports 500, so the count does not rise above the
cap even when many more rows match.

docs/dcu-tableviewer.md

@@ -21,7 +21,7 @@ The search covers **every** column of the table at once, so you do not need to k
 - **Character search** (the default) is a case sensitive CONTAINS match against every character column, so `Smith` finds `Smithson` and `smith` finds `Goldsmith`, but `smith` will not find `Smithson`.
 - **Numeric search** (tick the Numeric box) is an exact match against every numeric column, so `42` will not find `420` or `4210`.
 - If a filter is applied, the search runs within the filtered rows rather than the whole table.
-- The result set is capped by the [`DC_MAXOBS_WEBVIEW`](/dcc-options/#dc_maxobs_webview) option (500 rows by default). The row count shown next to the table name is the number of rows the search matched, which can be higher than the number of rows displayed.
+- The result set is capped by the [`DC_MAXOBS_WEBVIEW`](/dcc-options/#dc_maxobs_webview) option (500 rows by default). A search that matches more rows than the cap returns the first 500, and the row count shown next to the table name is that capped count, not the total number of matches.
 - A search that matches nothing shows a "No data found with given conditions" panel rather than an empty grid.
 
 ![Full table search](img/full-table-search.png)