Consider not using hard line-breaks in specification text

[glen-84]

• It creates unnecessary diffs where it's difficult to see what changed.
• It means that most GitHub-applied suggestions require the document to be reformatted afterwards.
• It makes it more difficult to search the source text – I just tried to search for but is not used by the, but it wasn't found because there was a hard line-break before the.
• It's just not natural for prose, and doesn't allow viewers to control the display width.
• etc.

An example (small) diff can be seen here.

I decided to create an issue first, to gather some interest before it's (potentially) brought to a meeting.