Manual pages English looks good to me.

Manual page change LGTM. I can't speak to consistency with code.

Wording nit fixable on commit. (Sorry for the delay. I'm way behind in my email.)

Other than that typo (and maybe using "classified": "classed" looks unfamiliar to me but readily understandable), LGTM.

Maybe, now that the call for testing is out, add a link to https://lists.freebsd.org/archives/freebsd-accessibility/2023-August/000034.html at the end of the report so people know how to test?

With .Dd bumped (fixable on commit), manual page change LGTM.

Manual page nits fixable on commit if nothing else requires an updated diff.

Manual page English LGTM.

I like this new trend of getting reports earlier in the quarter.

Sorry for the delay.

In D35776#943183, @asiciliano wrote:

I am interested to take/continue this feature. Are others already working?

Other than these 2 nits and what others mentioned, manual page English LGTM.

Still waiting for feedback on how to reconcile incompatible requests, which I think is the only thing holding this at this time.

English LGTM.

Nits fixable on commit

Manual page LGTM now, will rereview once the source code is finalized.

English LGTM.

Minor nit, fixable on commit.

Other than bcr's suggestion, English LGTM.

English LGTM.

English LGTM.

English LGTM. (Was the added subscriber a request for manpages review, or just for information?)

In addition to the line edits, could you rewrap this so each sentence is on a single line of its own?

Manual page English LGTM. Can't attest to anything else.

In D40756#927547, @cperciva wrote:

Dumb question, am I supposed to commit this to the docs tree, or do I just leave the review hanging here and let someone else commit it?

• Address edit comments by riggs and grahamperrin
• More revisions after grahamperrin feedback.

English in manual page still LGTM.

ping @riggs @grahamperrin Is either of you waiting for more changes from me?

Some nits in the manual page, which can probably be fixed in a follow-up commit (with .Dd bumped) if the code still works.

English LGTM.

English LGTM now. Can't attest to consistency with source code.

English in changes LGTM.

English LGTM now.

Other than the missing "space", English LGTM, but I can't speak about correctness.

English LGTM other maybe than rpokala's wording nit.

Better UX FTW!

In D35754#903091, @hselasky wrote:

In D35754#857657, @pauamma_gundo.com wrote:

Expected: at steps 6 and 9, reading each line is aborted on successive control-B presses and vtspeakd skips to the next line.
Observed: at step 6, each line is read out in full (incorrect); at step 9, vtspeak aborts and skips to the next line on every control-B press (correct).

If the console is in input mode or not reading any text, then CTRL+B doesn't work, like reading a line. Maybe I should fix that?

LGTM.

Minor nits, fixable on commit if nothing else requires another round.

Don't want to delay this further. Nothing that can't be fixed on commit, if need be.

In D39168#892042, @rmacklem wrote:

Oops, I missed the reviewed by pauamma (manpages),
since it happened just when I did the commit.

Can a committer take this? My commit access was revoked.

English LGTM. Can't attest to consistency with source code.

English LGTM.

Very minor, fixable on commit.

Language LGTM.

Minor nits, fixable on commit if nothing else stands out.

Minor nits fixable on commit.

Fixable on commit.

@carlavilla, since you're working on the Handbook, do you plan to rereview and commit this? Otherwise I'd like to take it over and ready it for committing.

Over to @carlavilla @gjb for (preferrably fast) mentor approval.

Over to @carlavilla @gjb for mentor approval

Should take care of all comments.

• Fix nits salvadore pointed out and a few more I spotted meanwhile.

I completely forgot about that. Sorry.

• Remove unreferenced "as-needed" note.