The old text failed the issue's prose rules: a 60-word sentence on the content security policy, a markdown table of settings, comma-chained lists of batch sizes and error codes, undefined jargon and an edge case in the opening. The new text leads with what RouteWatch is, why it exists and how to run it, then the pages, the API and the blocklists, then the settings, memory and upaas, and last the design and the development workflow. Every statement was checked against the code on next. The PR body lists where the old text disagreed with the code. Model: fable-5-1
This commit is contained in: