diff --git a/docs/content/internals/model.md b/docs/content/internals/model.md
index d2dd5148a..1f222c3e4 100644
--- a/docs/content/internals/model.md
+++ b/docs/content/internals/model.md
@@ -5,7 +5,7 @@ weight: 1
 
 The illustration below shows the internal architecture of the Prometheus Java client library.
 
-![Internal architecture of the Prometheus Java client library](/images/model.png)
+![Internal architecture of the Prometheus Java client library](/client_java/images/model.png)
 
 prometheus-metrics-core
 -----------------------
diff --git a/docs/content/otel/names.md b/docs/content/otel/names.md
index 2cd892c3c..3d25dd3d4 100644
--- a/docs/content/otel/names.md
+++ b/docs/content/otel/names.md
@@ -7,7 +7,7 @@ OpenTelemetry naming conventions are different from Prometheus naming convention
 
 The goal is, if you set up a pipeline as illustrated below, you will see the same metric names in the Prometheus server as if you had exposed Prometheus metrics directly.
 
-![Image of a with the Prometheus client library pushing metrics to an OpenTelemetry collector](/images/otel-pipeline.png)
+![Image of a with the Prometheus client library pushing metrics to an OpenTelemetry collector](/client_java/images/otel-pipeline.png)
 
 The main steps when converting OpenTelemetry metric names to Prometheus metric names are:
 
diff --git a/docs/content/otel/otlp.md b/docs/content/otel/otlp.md
index d81ed822e..ea39f178f 100644
--- a/docs/content/otel/otlp.md
+++ b/docs/content/otel/otlp.md
@@ -5,7 +5,7 @@ weight: 1
 
 The Prometheus Java client library allows you to push metrics to an OpenTelemetry endpoint using the OTLP protocol.
 
-![Image of a with the Prometheus client library pushing metrics to an OpenTelemetry collector](/images/otel-pipeline.png)
+![Image of a with the Prometheus client library pushing metrics to an OpenTelemetry collector](/client_java/images/otel-pipeline.png)
 
 To implement this, you need to include `prometheus-metrics-exporter` as a dependency