resolve comments

versioned_docs/version-8.2/self-managed/zeebe-deployment/operations/metrics.md

@@ -93,8 +93,6 @@ The health of partitions in a broker can be monitored by the metric `zeebe_healt
 Zeebe comes with a pre-built dashboard, available in the repository:
 [monitor/grafana/zeebe.json](https://github.com/camunda/camunda/blob/stable/8.2/monitor/grafana/zeebe.json).
 
-<!--- While updating the 8.6 links following the minor I noticed this link no longer works. --->
-
 [Import](https://grafana.com/docs/grafana/latest/reference/export_import/#importing-a-dashboard) it into your Grafana instance and select the correct Prometheus data source (important if you have more than one). You will then be greeted with the following dashboard, which displays a healthy cluster topology, general throughput metrics, handled requests, exported events per second, disk and memory usage, and more.
 
 ![Grafana dashboard](assets/grafana-preview.png)

versioned_docs/version-8.6/self-managed/zeebe-deployment/exporters/elasticsearch-exporter.md

@@ -25,9 +25,7 @@ your own ETL jobs.
 
 When configured to do so, the exporter will automatically create an index per record value type (see the value type in the Zeebe protocol). Each of these indexes has a
 corresponding pre-defined mapping to facilitate data ingestion for your own ETL jobs. You can find
-those as templates in [the resources folder of the exporter's source code](https://github.com/camunda/camunda/tree/main/zeebe/exporters/elasticsearch-exporter/src/main/resources).
-
-<!--- The 8.6.0 branch of camunda does not contain the path exporters/elasticsearch-exporter/src/main/resources. --->
+those as templates in [the resources folder of the exporter's source code](https://github.com/camunda/camunda/tree/stable/8.6/zeebe/exporters/elasticsearch-exporter/src/main/resources).
 
 :::note
 The indexes are created as required, and will not be created twice if they already exist. However, once disabled, they will not be deleted (that is up to the administrator.) Similarly, data is never deleted by the exporter, and must be deleted by the administrator when it is safe to do so.