Land recovered "it is possible to" copyedits on unity/v6.1 and v6.0

[allister-beamable]

A 2026-04-02 stash based on the now-retired unity/v5.0 held a copyediting pass replacing passive it is possible to / it is recommended to / it is important to constructions. The work never landed anywhere: 11 of the 19 phrasings it fixes are still live on unity/v6.1 today.

The stash has been recovered onto copyedit/it-is-possible-unity-6.1 (commit ad2544da6, branched from origin/unity/v6.1), and the stash itself dropped. 13 files, +13/-17.

What is needed

1. Review copyedit/it-is-possible-unity-6.1 and open a PR into unity/v6.1, with Vitor Balbio as reviewer. Squash-and-merge.
2. Cherry-pick the same commit onto unity/v6.0 — verified to apply cleanly with git apply --3way.

Notes for the reviewer

• docs/cli/guides/ms-logging.md is deliberately excluded. The stash touched it, but it is a core-owned path and both of its hunks had already landed on core. Do not re-add it.
• Three hunks needed hand-merging where the prose had moved on since April:
  • stores-overview.md — v6.1 had already changed "features" to "services"; that wording is preserved
  • groups.md — the stash predates the !!! info "Learning Fundamentals" admonition conversion. The v6.1 admonition structure is kept; only the passive recommendation inside it is reworded
  • autogenerated-sdk.md — the stash draft introduced "isn't"; changed to "is not" per the no-contractions house style
• hats.md drops two copies of a garbled line ("Related Guides: It is recommended to read the guide before continuing with the sample steps below.") that duplicated its own admonition title.
• One hunk is more than a style fix and deserves a factual check: stores-overview.md now says to declare StoreRef / ListingRef as serialized fields on your MonoBehaviour so the Inspector renders a drop-down, replacing the vaguer "create a StoreRef and ListingRef".