Three fixes to the public pages, all reported from the live site.
landing.leaf carried its own copy of the get section, which /get
had been fixed and it had not: "The iPhone version is still being
prepared" and a tile reading "Not open yet". It now links the beta with
the same wording as /get. My earlier audit grepped for "Coming soon"
and "isn't out yet" and never saw this phrasing, which is the argument
for checking the rendered page rather than the terms I expected.
The Flamenet column said its availability twice. Every cell led with
the verdict ("Android & iPhone beta") and then repeated it as a closing
sentence. 470 words against Signal's 114; now 377. Three cells used that
clause mid-sentence, so removing it left "and you both need it..."
hanging; those read as sentences again.
A row header had become a fragment. My em-dash pass turned
"— and every message after that", which continued the row above, into
", and every message after that". It reads "And every message after
that", matching the glossary entry below the table.
697 tests pass; check-doc-pages agrees with the pin.
Three fixes to the public pages, all reported from the live site.
**landing.leaf carried its own copy of the get section**, which /get
had been fixed and it had not: "The iPhone version is still being
prepared" and a tile reading "Not open yet". It now links the beta with
the same wording as /get. My earlier audit grepped for "Coming soon"
and "isn't out yet" and never saw this phrasing, which is the argument
for checking the rendered page rather than the terms I expected.
**The Flamenet column said its availability twice.** Every cell led with
the verdict ("Android & iPhone beta") and then repeated it as a closing
sentence. 470 words against Signal's 114; now 377. Three cells used that
clause mid-sentence, so removing it left "and you both need it..."
hanging; those read as sentences again.
**A row header had become a fragment.** My em-dash pass turned
"— and every message after that", which continued the row above, into
", and every message after that". It reads "And every message after
that", matching the glossary entry below the table.
697 tests pass; check-doc-pages agrees with the pin.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Three fixes to the public pages, all reported from the live site.
landing.leaf carried its own copy of the get section, which /get
had been fixed and it had not: "The iPhone version is still being
prepared" and a tile reading "Not open yet". It now links the beta with
the same wording as /get. My earlier audit grepped for "Coming soon"
and "isn't out yet" and never saw this phrasing, which is the argument
for checking the rendered page rather than the terms I expected.
The Flamenet column said its availability twice. Every cell led with
the verdict ("Android & iPhone beta") and then repeated it as a closing
sentence. 470 words against Signal's 114; now 377. Three cells used that
clause mid-sentence, so removing it left "and you both need it..."
hanging; those read as sentences again.
A row header had become a fragment. My em-dash pass turned
"— and every message after that", which continued the row above, into
", and every message after that". It reads "And every message after
that", matching the glossary entry below the table.
697 tests pass; check-doc-pages agrees with the pin.
Co-Authored-By: Claude Opus 5 noreply@anthropic.com
assigned to @paulhitt
mentioned in commit
3587f18bc7