remove redundant sections

policy/tpa-rfc-33-monitoring.md

@@ -445,6 +445,10 @@ Python and [grafanalib][]. She directly participates in the
 She would love to get [alerts over Matrix][], but currently receives
 notifications by email, sometimes to a Mailman mailing list.
 
+Jackie absolutely needs to have certain dashboards completely private,
+but would love if some dashboards can be made public. She can live
+with those being accessible only to tor-internal.
+
 [prometheus-alerts]: https://gitlab.torproject.org/tpo/tpa/prometheus-alerts
 [grafanalib]: https://github.com/weaveworks/grafanalib
 [alerts over Matrix]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/40216
@@ -682,10 +686,13 @@ two entirely different time series datasets, which would be too hard
 to reliably separate. That would also impose a cardinal explosion of
 servers if we want to provide high availability.
 
+TODO: review https://gitlab.torproject.org/tpo/tpa/team/-/issues/41280
+https://gitlab.torproject.org/tpo/tpa/team/-/issues/30023
+
 ## Trending: Grafana
 
 TODO: document how dashboards get
-provisioned... grafana-dashboards.git + grafanalib?
+provisioned... grafana-dashboards.git + grafanalib? review [tpo/tpa/team#41312](https://gitlab.torproject.org/tpo/tpa/team/-/issues/41312)
 
 TODO: do we really need a grafana server per host? or can we afford
 Grafana outages so we manage a single grafana server?
@@ -790,15 +797,6 @@ email / gitlab incidents for pages?
 
 TODO: review https://gitlab.com/gitlab-com/gl-infra/helicopter
 
-### Dashboard management
-
-TODO: see [tpo/tpa/team#41312](https://gitlab.torproject.org/tpo/tpa/team/-/issues/41312)
-
-### Access control
-
-TODO: see
-[tpo/tpa/team#40124](https://gitlab.torproject.org/tpo/tpa/team/-/issues/40124) https://gitlab.torproject.org/tpo/tpa/team/-/issues/30023
-
 ## Migration plan
 
  * deploy Alertmanager on prometheus1