diff --git a/.github/workflows/ci-pr.yml b/.github/workflows/ci-pr.yml
index eab6d398..01bd23c2 100644
--- a/.github/workflows/ci-pr.yml
+++ b/.github/workflows/ci-pr.yml
@@ -49,3 +49,11 @@ jobs:
           name: test-results
           path: '*/build/reports/tests/**/*.*'
           retention-days: 3
+
+      - name: Capture Jacoco Results
+        if: contains(github.event.pull_request.labels.*.name, 'ci/upload-jacoco')
+        uses: actions/upload-artifact@v3
+        with:
+          name: jacoco-results
+          path: '*/build/reports/jacoco/**/*.*'
+          retention-days: 3
diff --git a/spring-pulsar-docs/src/main/asciidoc/pulsar-header.adoc b/spring-pulsar-docs/src/main/asciidoc/pulsar-header.adoc
index 1c251deb..5472144e 100644
--- a/spring-pulsar-docs/src/main/asciidoc/pulsar-header.adoc
+++ b/spring-pulsar-docs/src/main/asciidoc/pulsar-header.adoc
@@ -1,6 +1,4 @@
 
-== Message Headers
-
 === Pulsar Headers
 Pulsar does not have a first-class "`header`" concept but instead provides a map for custom user properties as well as methods to access the message metadata typically stored in a message header (eg. `id` and `event-time`).
 As such, the terms "`Pulsar message header`" and "`Pulsar message metadata`" are used interchangeably.