docs: clarifications for conformance display badges

Author: shaneutt

geps/gep-1709.md

@@ -573,9 +573,9 @@ point to the new data.
 > conformance test suite. When PRs are created the Gateway API repositories'
 > CI will run linting and validation against the reports.
 
-CI will provide [badges][bdg] to contributors at the end of the process which
-link to the implementations page for that specific implementation and can be
-easily added via markdown to Git repositories.
+Maintainers will provide [badges][bdg] to contributors at the end of the process
+which link to the implementations page for that specific implementation and can
+be easily added via markdown to Git repositories.
 
 [impl]:https://gateway-api.sigs.k8s.io/implementations/
 [bdg]:https://shields.io
@@ -629,7 +629,7 @@ there's a technical reason or strong desire from implementers.
 The following are items that **MUST** be resolved to move this GEP to
 `Standard` status (and before the end of the probationary period):
 
-- [ ] some kind of basic level of display for the report data needs to exist.
+- [x] some kind of basic level of display for the report data needs to exist.
   It's OK for a more robust display layer to be part of a follow-up effort.
 - [ ] initially we were OK with storing reports in the Git repository as files.
   While this is probably sufficient during the `Experimental` phase, we need to