Fix up for policy listing

Policies.md

@@ -14,6 +14,7 @@ WHATWG participants operate under a number of policies:
 * [Invited Individual Policy](./Invited%20Individual%20Policy.md)
 * [Code of Conduct](./Code%20of%20Conduct.md)
 * [Working Mode](./Working%20Mode.md)
+* [Stages](./Stages.md)
 
 Additionally, the WHATWG Steering Group was created by the [Steering Group Agreement](./SG%20Agreement.md) and operates under the [Steering Group Policy](./SG%20Policy.md).
 

Stages.md

@@ -2,7 +2,7 @@
 
 The WHATWG's "document reality" approach has been effective for nailing down [fundamental parts of the platform](https://spec.whatwg.org/) and improving interoperability and developer satisfaction. However, our process can sometimes be daunting for newcomers, who don't know how to reliably get implementer feedback or editor time commitment. This can discourage contributions, and it can lead to frustration when implementer/editor feedback arrives late in the process after the contributor feels "close to done".
 
-The stage process described here is an additional tool designed to help provide a clear on-ramp for incubation efforts for contributors who aren't already editors, especially for additions to existing specs.  Stages are an optional, opt-in process that a feature proposer can use if they want to get more formal signals about how their feature is progressing. It asks for explicit implementer involvement at multiple stages, starting from notification that the problem is being worked on, then sign-off on the rough API and specification, and finally agreement on the full specification text. 
+The stage process described here is an additional policy tool designed to help provide a clear on-ramp for incubation efforts for contributors who aren't already editors, especially for additions to existing specs.  Stages are an optional, opt-in process that a feature proposer can use if they want to get more formal signals about how their feature is progressing. It asks for explicit implementer involvement at multiple stages, starting from notification that the problem is being worked on, then sign-off on the rough API and specification, and finally agreement on the full specification text. 
 
 Stage signals are also useful to the broader community, helping developers monitor the proposals that are moving through the various stages.  By explicitly signaling a proposal's progress, including implementer involvement, the community has a better idea of what is going on in the WHATWG.
 

policy-link-mapping.txt

@@ -8,6 +8,7 @@
 ./Privacy%20Policy.md=privacy-policy
 ./Policies.md=policies
 ./Working%20Mode.md=working-mode
+./Stages.md=stages
 ./db.json=https://github.com/whatwg/sg/blob/main/db.json
 ./ThirdPartyNotices/W3CLicenses.md=https://github.com/whatwg/sg/blob/main/ThirdPartyNotices/W3CLicenses.md
 ./LICENSE=https://github.com/whatwg/sg/blob/main/LICENSE