Grasp
Public
Showcasesindresorhus/ky #870SourceMarkdown

docs: correct inaccurate Retry-After term ("timeout" → "delay")

The retry documentation describes the Retry-After header value as a "date, timeout, or timestamp".

MERGEDGrasp · Jul 30, 2026

Three explanations of the same brief

No jargon, about fifteen seconds

docs: correct inaccurate Retry-After term ("timeout" → "delay")

Someone changed how a program works. The retry documentation describes the Retry-After header value as a "date, timeout, or timestamp". The part to watch: Source changed with no test changed.

docs: correct inaccurate Re…Heaviest file
The one thing to take away

30 words · derived from the brief below, no model involved

The change is spread across 2 files in 2 areas, with no single file dominating.

2 files changed across 2 areas of sindresorhus/ky, 2 added and 2 removed.

The retry documentation describes the Retry-After header value as a "date, timeout, or timestamp".

heaviestky2 files, 4 linesDocs1 file, 2 linesSource1 file, 2 linesreadme.md+1 −1
Where the change landed. Node size is not to scale; the line counts are exact.Download for draw.io
Heaviest file

readme.md, +1 −1, which is 50% of the change.

No test changed

1 source file changed with no accompanying test edit.

Spread

2 files, 4 changed lines in total.

What this brief could not check

  • No language model read this change. Every statement here is computed from file paths, line counts, and CI status, so it describes the shape of the diff and not what the diff means.
  • No test file changed, so nothing here is evidence that the change works.