diff --git a/.github/workflows/auto-update-community-members.yml b/.github/workflows/auto-update-community-members.yml
index 402545a20011..6fe36ee0c676 100644
--- a/.github/workflows/auto-update-community-members.yml
+++ b/.github/workflows/auto-update-community-members.yml
@@ -35,6 +35,9 @@ jobs:
         uses: peter-evans/create-pull-request@v7
         with:
           add-paths: 'data/community/members.yaml'
+          author:
+            opentelemetrybot
+            <107717825+opentelemetrybot@users.noreply.github.com>
           committer:
             opentelemetrybot
             <107717825+opentelemetrybot@users.noreply.github.com>
diff --git a/content/en/blog/2024/prometheus-compatibility-survey/index.md b/content/en/blog/2024/prometheus-compatibility-survey/index.md
index 83a6fa8e2cca..85352faadf43 100644
--- a/content/en/blog/2024/prometheus-compatibility-survey/index.md
+++ b/content/en/blog/2024/prometheus-compatibility-survey/index.md
@@ -121,7 +121,7 @@ should not generally be included in the metric name. Prometheus conventions
 [recommend](https://prometheus.io/docs/practices/naming/#metric-names) that the
 unit be included as a suffix of the metric name. OpenMetrics goes a step further
 and
-[requires this unit suffix](https://github.com/OpenObservability/OpenMetrics/blob/main/specification/OpenMetrics.md#unit).
+[requires this unit suffix](https://github.com/prometheus/OpenMetrics/blob/v1.0.0/specification/OpenMetrics.md#unit).
 Currently, when exporting in Prometheus format from an OpenTelemetry SDK, the
 unit is added as a suffix to the metric name.
 
diff --git a/content/en/docs/languages/java/_index.md b/content/en/docs/languages/java/_index.md
index cbfa6a1ba438..7027329a3bbc 100644
--- a/content/en/docs/languages/java/_index.md
+++ b/content/en/docs/languages/java/_index.md
@@ -8,7 +8,7 @@ cascade:
   vers:
     instrumentation: 2.10.0
     otel: 1.45.0
-    contrib: 1.41.0
+    contrib: 1.42.0
     semconv: 1.28.0
 weight: 18
 ---
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 19aec24686e0..ebf99c6a66e6 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
@@ -111,20 +111,16 @@ The OpenTelemetry starter uses OpenTelemetry Spring Boot
 {{< tabpane text=true >}} {{% tab header="Maven (`pom.xml`)" lang=Maven %}}
 
 ```xml
-<dependencies>
-  <dependency>
+<dependency>
     <groupId>io.opentelemetry.instrumentation</groupId>
     <artifactId>opentelemetry-spring-boot-starter</artifactId>
-  </dependency>
-</dependencies>
+</dependency>
 ```
 
 {{% /tab %}} {{% tab header="Gradle (`gradle.build`)" lang=Gradle %}}
 
 ```kotlin
-dependencies {
-	implementation("io.opentelemetry.instrumentation:opentelemetry-spring-boot-starter")
-}
+implementation("io.opentelemetry.instrumentation:opentelemetry-spring-boot-starter")
 ```
 
 {{% /tab %}} {{< /tabpane>}}
diff --git a/data/registry/exporter-js-sap-cloud-logging.yml b/data/registry/exporter-js-sap-cloud-logging.yml
index 667df759bc2a..f22bd08d10b0 100644
--- a/data/registry/exporter-js-sap-cloud-logging.yml
+++ b/data/registry/exporter-js-sap-cloud-logging.yml
@@ -24,4 +24,4 @@ isFirstParty: false
 package:
   registry: npm
   name: '@sap/opentelemetry-exporter-for-sap-cloud-logging'
-  version: 0.2.0
+  version: 0.3.0