Guiding users to revocation

Regret: Given the challenges of permission annoyance and abuse, it is reasonable for user agents to suppress a site's future requests for the same capability when the first request is blocked. That said, our research shows that users can and do change their minds for good reasons. When they change their mind, the site can no longer offer an interface in web content and the user must search for the appropriate user agent surface. Our research shows that users often fail when trying to do so (see example 3).

It seems this problem will get worse for users who would like to revoke a permission. They will be even less likely to be aware of any user agent UI for managing permissions and sites often don't have any incentive to do so.
Even the examples are biased in this sense:


Shouldn't the second button be called "Unshare Location" or show a checked checkbox so users are aware that they can also remove the permissions here?

Inspect the PEPC explainer's permission examples and the two referenced UI images first. Determine how the second control should communicate that permission can be revoked, then update the example wording or checked state so the rendered explanation makes revocation discoverable.