[container.insert.return] Fix description of insert-return-type

[adr26]

Use "for exposition only" for consistency with usage elsewhere in the spec, and for the clarity/grammatical correctness of this sentence.

[tkoeppe]

I wouldn't really call this a "typo"; nothing is mispelled here. It's more of a stylistic choice.

[jensmaurer]

The existing phrasing needs a hyphen in my book, and I like consistency.
So, I'm for adding "for".

[jwakely]

Yeah, seems like an improvement, although the commit message could omit mentioning "typo" :)

[adr26]

I should have said a "typographical omission" but wrote "typo" for short, which has overloaded semantics with "spelling or punctuation error" :)

@jwakely - I have updated the PR title, but can't retroactively change the commit message without recreating the branch. Should I do that?

[jensmaurer]

Changing the title of the pull request does not change the title of the commit message.
You need to "git commit --amend", change it there, and then force-push.
(Yes, force-pushing is fine.)

[tkoeppe]

(We can also change that when squash-merging, but it might be good PR handling practice. Yes, you can modify the PR branch as much as you like, and push and force-push as you see fit.)

[adr26]

Thanks for the clarification @jensmaurer - I force-pushed to my fork with the commit message updated.

Is everything OK now (once the checks come back clean)?

[jwakely]

Looks good, thanks

[tkoeppe]

Thanks!