Add monitoring diagram + solve todos

docs/src/main/paradox/docs/getting-started/running-nexus/delta.md

@@ -26,13 +26,14 @@ Nexus Delta relies on @link:[Kamon](https://kamon.io/) to also collect metrics a
 
 To enable Kamon in Delta, the `KAMON_ENABLED` env variable must be set to true.
 
-// TODO add mentions to the Kibana dashboard
+To monitor Nexus write activity like resource and file creation/updates, a dashboard is available in the 
+@link:[Nexus repo](https://github.com/BlueBrain/nexus/blob/$git.branch$/kibana/event-metrics/general.ndjson).
 
 **Logs:**
 Nexus Delta relies on @link:[Logback](https://logback.qos.ch/) for logs which one of the popular logging
 frameworks on the JVM.
 
-Log back provides:
+Logback provides:
 
 * Reloading the configuration while the application is running
 * Control the output of the logs, opting for JSON helps for the integration with Filebeats and Elasticsearch

docs/src/main/paradox/docs/getting-started/running-nexus/index.md

@@ -250,12 +250,12 @@ Monitoring a Nexus deployment is important to identify its performance and its h
 While different approaches are possible depending on how and where Nexus is deployed, an example of monitoring stack can be:
 
 * @link:[Prometheus](https://prometheus.io/) which is a open-source tool for monitoring
-* @link:[Blackbox](https://github.com/prometheus/blackbox_exporter) can be used to probe endpoints over
+* @link:[Blackbox](https://github.com/prometheus/blackbox_exporter) can be used to probe endpoints over http
 * @link:[Alert Manager](https://github.com/prometheus/alertmanager) for alerts
 * @link:[Grafana](https://grafana.com/grafana/) for visualization
 * @link:[Filebeats](https://www.elastic.co/beats/filebeat), @link:[Elasticsearch](https://www.elastic.co/elasticsearch) and @link:[Kibana](https://www.elastic.co/kibana) to collect and visualize Delta logs
 
 Prometheus has been the historical solution for monitoring Nexus at BBP for its popularity and its versatility as it allows to
 monitor all components.
 
-// TODO add a diagram of how the Prometheus ecosystem work.
+![Monitoring with Prometheus](../assets/prometheus-monitoring.png)

docs/src/main/paradox/docs/releases/v1.6-to-v1.7-migration.md

@@ -11,6 +11,4 @@ operation are completed without forgetting to remove the environment variables.
 
 ## Fusion
 
-The data model for Studios has changed in 1.7.
-
-//TODO Add Studio migration instructions here
+The data model for Studios has changed in 1.7.

docs/src/main/paradox/docs/releases/v1.8-release-notes.md

@@ -206,6 +206,3 @@ The goal of this release was to improve the user experience and functionality of
 11. App Configuration:
       - The Application manager has the ability to select his favourites images for different top-level pages and the video in the Login page.
 
-## Nexus forge
-
-TODO

docs/src/main/paradox/docs/releases/v1.9-release-notes.md

@@ -6,8 +6,6 @@
 > With v1.9, Nexus Delta also changes its underlying runtime, allowing to it to work properly,
 > switching from @link:[Monix](https://monix.io/) which is not maintained anymore to @link:[Cats Effect](https://typelevel.org/cats-effect/).
 
-//TODO adjust the end date
-
 For the detailed list of updates in this release, see the
 @link:[list of addressed issues](https://github.com/BlueBrain/nexus/issues?&q=is%3Aissue+is%3Aclosed+created%3A2023-06-15..2023-12-14+){ open=new }
 since v1.8.