In the blurb, I can read:

When active, the braille display shows exactly what NVDA prepares to speak.

IMO, "prepare to speak" is not clear for end-users.

We may just write:
"When active, the braille display shows exactly what NVDA speaks."

For the blurb, it's not important to take into account corner cases such as the "speech off" case.

By the way, also for the subsequent change log item, we may remove "prepare to".

The User Guide is more precise and indicates:

When display speech output is selected, the braille display will show what NVDA speaks, or would have spoken if speech mode was set to "talk"

But this corner case does not need to be presented in the change log IMO.

By the way, if this PR gathers all minor changes needed in the documentation, in the User Guide, could you add a period at the end of the following sentence?

When display speech output is selected, the braille display will show what NVDA speaks, or would have spoken if speech mode was set to "talk"

thanks @CyrilleB79 for the catches

@seanbudd while at it, could you also fix here the table formatting issues described by @k-kolev1985 in this message on the translators mailing list?
Thanks.

Also, I've noticed that some heading titles (marked with ====) are missing a space between the text and the ==== sequence. I'm not sure if this causes a formatting breakage or not, but I'm reporting it just in case. Unfortunately, I did not wrote down on which lines in the documentations are those missing spaces.

@CyrilleB79 - I've fixed this up, thanks @k-kolev1985 for reporting this

@k-kolev1985 - I don't think this is causes any formatting issues, and also should be fixed when we migrate to markdown next week.