Fix a poor heading

[camerons]

Seemed to be a funny char in the heading text which caused it not to render properly. It was getting rendered as markdown:

What are you writing about?

I couldn't work out what it was, maybe a floating space or something (although i couldn't find it). Fixed by rewriting the line.

ALL Pull-Requests require an associated Issue as documented in How to contribute.

Purpose / why

Replace this text - Restate the purpose/justification of this work and include links to the issue inside of the purpose/why.

What changes were made?

Replace this text - State clearly the direct additions or modifications made in this change-request.

Verification

Replace this text - Document the details that help a reviewer understand what steps or actions should be taken in-order to verify the work is completed and satisfies the initial scope of work.

---

Checklist

Pull-request reviewer should ensure the following

• [ ] Are issues linked correctly?
• [ ] Is this PR labeled correctly?
• [ ] If template updates: do they align with developers.google.com/style/?
• [ ] Did the PR receive at least one :+1: and no :-1: from core-maintainers?
• [ ] On merging, did you complete the merge using keywords?
• [ ] On merging, did you add any applicable notes to a draft release and link to this PR?

[camerons]

Lana, feel free to merge this.

[Loquacity]

Ah, it would have been a non-breaking space, they slip in if I'm not careful. Thanks!