XS✔ ◾ Adjust "be specific in communication" section title to reference PBIs as well as emails

[ncn-ssw]

1. What triggered this change? (PBI link, Email Subject, conversation + reason, etc)

While creating training material for Product Owners with @piers-sinclair, Pier's noted that the section title "One Email per Item" should mention PBIs as they are the preferred means of defining and allocating tasks.

2. What was changed?

• Section title "One Email per Item" changed to "One email (or Product Backlog Item) per task"
• Refactored spacing in communication-are-you-specific-in-your-requirements/rule.md
• Adjusted the capitalisation of section titles to use the "Sentence case" capitalisation style used for most modern rules

3. Did you do pair or mob programming (list names)?

No

[github-actions]

PR Metrics

✔ Thanks for keeping your pull request small.
✔ Thanks for adding tests.

	Lines
Product Code	-
Test Code	-
Subtotal	-
Ignored Code	9
Total	9

Metrics computed by PR Metrics. Add it to your Azure DevOps and GitHub PRs!

[github-actions]

Howzit @ncn-ssw,

This PR has been here a while.

Did you know you should avoid merge debt?

1. Please action (e.g. get a review) and merge or close

Thanks!