Use REF1 macro instead of OBJECTREF

[wilzbach]

The REF1 macro should have been used here instead.

See also: dlang/dlang.org#2191

edit: also fixed a few typos while I was at it.

[dlang-bot]

Thanks for your pull request, @wilzbach!

Bugzilla references

Your PR doesn't reference any Bugzilla issue.

If your PR contains non-trivial changes, please reference a Bugzilla issue or create a manual changelog.

[CyberShadow]

child process's standard streams

Not sure about this. There's 4 s letters in a row here.

Some commentary on Wikipedia:
https://en.wikipedia.org/wiki/Apostrophe#Singular_nouns_ending_with_an_%22s%22_or_%22z%22_sound

[wilzbach]

The Supreme Court of the United States is split on whether a possessive singular noun that ends with s should always have an additional s after the apostrophe, sometimes have an additional s after the apostrophe (for instance, based on whether the final sound of the original word is pronounced /s/ or /z/), or never have an additional s after the apostrophe. The informal majority view (5–4, based on past writings of the justices) has favoured the additional s, but a strong minority disagrees.

😱 - maybe we need a typography styleguide too 😕
Okay will drop the second commit for now.

[n8sh]

@wilzbach Don't be silly. Please add it back. Documentation should not without good reason use spellings that a majority of readers will perceive as an error.

[wilzbach]

Don't be silly.

In my experience, anything that is potentially controversial in a PR can (or will) block it.
Hence, it's better to move such things into separate PRs, s.t. the main PR can be merged quickly.
I submitted this because of the REF1 macro (sorry for screwing up the initial title) - that is/was my main concern.

Please add it back.

Sure. Let's have the discussion here: #6141

[CyberShadow]

Thanks! Looks like this fixes some broken HTML in DDox, though browsers treated it the same before and after.