diff --git a/content/en/docs/zero-code/java/spring-boot-starter/_index.md b/content/en/docs/zero-code/java/spring-boot-starter/_index.md
index e9407e1f9905..0292824e7b64 100644
--- a/content/en/docs/zero-code/java/spring-boot-starter/_index.md
+++ b/content/en/docs/zero-code/java/spring-boot-starter/_index.md
@@ -6,6 +6,8 @@ aliases:
   - /docs/zero-code/java/spring-boot
 ---
 
+## Java agent versus Spring Boot starter
+
 You can use two options to instrument
 [Spring Boot](https://spring.io/projects/spring-boot) applications with
 OpenTelemetry.
@@ -23,3 +25,33 @@ OpenTelemetry.
    - **Spring Boot configuration files** (`application.properties`,
      `application.yml`) to configure the OpenTelemetry Spring Boot starter which
      doesn't work with the OpenTelemetry Java agent
+
+## Comparison to Micrometer
+
+A question asked frequently is how [Micrometer](https://micrometer.io/) and the OpenTelemetry Spring Boot Starter differentiate. At a high level, the differences are as follows:
+
+OpenTelemetry Spring Boot starter:
+
+- Natively uses the OpenTelemetry API, OpenTelemetry SDK, and the OpenTelemetry
+  semantic conventions.
+- Supported by the OpenTelemetry community (governed by the CNCF / Linux
+  Foundation).
+
+Micrometer [^1][^2]:
+
+- An independent standalone observability system.
+- Offers optional bridges into parts of the OpenTelemetry ecosystem.
+- Supported by the Micrometer community (governed by Broadcom Inc).
+
+As the authors of the OpenTelemetry Spring Boot starter, we recommend using the
+OpenTelemetry Spring Boot starter. We have a great community behind it, and are
+continuously making improvements. If you try it out and have any problems or
+suggestions, open an
+[issue](https://github.com/open-telemetry/opentelemetry-java-instrumentation/issues)
+in our repository.
+
+[^1]:
+    [Micrometer metrics OTLP registry](https://docs.micrometer.io/micrometer/reference/implementations/otlp.html)
+
+[^2]:
+    [Micrometer tracing OpenTelemetry bridge](https://docs.micrometer.io/tracing/reference/tracers.html)
diff --git a/content/en/docs/zero-code/java/spring-boot-starter/getting-started.md b/content/en/docs/zero-code/java/spring-boot-starter/getting-started.md
index eba5b9332a8b..1f5955033811 100644
--- a/content/en/docs/zero-code/java/spring-boot-starter/getting-started.md
+++ b/content/en/docs/zero-code/java/spring-boot-starter/getting-started.md
@@ -7,7 +7,8 @@ cSpell:ignore: springboot
 {{% alert title="Note" color="info" %}}
 
 You can also use the [Java agent](../../agent) to instrument your Spring Boot
-application. For the pros and cons, see [Java zero-code instrumentation](..).
+application. For the pros and cons, see
+[Java agent versus Spring Boot starter](../#java-agent-versus-spring-boot-starter).
 
 {{% /alert %}}
 
diff --git a/static/refcache.json b/static/refcache.json
index 0943e0b7b65e..19f83660615b 100644
--- a/static/refcache.json
+++ b/static/refcache.json
@@ -1299,6 +1299,14 @@
     "StatusCode": 206,
     "LastSeen": "2024-02-17T16:19:07.140338072Z"
   },
+  "https://docs.micrometer.io/micrometer/reference/implementations/otlp.html": {
+    "StatusCode": 206,
+    "LastSeen": "2024-06-11T08:17:08.270558365+02:00"
+  },
+  "https://docs.micrometer.io/tracing/reference/tracers.html": {
+    "StatusCode": 206,
+    "LastSeen": "2024-06-11T08:17:11.015227386+02:00"
+  },
   "https://docs.microsoft.com/aspnet/core": {
     "StatusCode": 200,
     "LastSeen": "2024-01-18T08:53:25.01054-05:00"
@@ -3739,6 +3747,10 @@
     "StatusCode": 200,
     "LastSeen": "2024-01-18T19:55:35.674322-05:00"
   },
+  "https://github.com/open-telemetry/opentelemetry-java-instrumentation/issues": {
+    "StatusCode": 200,
+    "LastSeen": "2024-06-11T08:17:15.340773687+02:00"
+  },
   "https://github.com/open-telemetry/opentelemetry-java-instrumentation/issues/7413": {
     "StatusCode": 200,
     "LastSeen": "2024-02-22T15:50:20.20139382Z"