diff --git a/.github/workflows/release_build.yml b/.github/workflows/release_build.yml
index f6fe6cf5..ff032a00 100644
--- a/.github/workflows/release_build.yml
+++ b/.github/workflows/release_build.yml
@@ -125,7 +125,7 @@ jobs:
       - name: Get SHA256 checksum of wheel file
         id: get_sha256
         run: |
-          shasum -a 256 dist/${{ env.ARTIFACT_NAME }} > ${{ env.ARTIFACT_NAME }}.sha256
+          shasum -a 256 dist/${{ env.ARTIFACT_NAME }} | sed "s|dist/||" > ${{ env.ARTIFACT_NAME }}.sha256
 
       # Publish to GitHub releases
       - name: Create GH release
diff --git a/README.md b/README.md
index 7ccd9d92..ef8b04c8 100644
--- a/README.md
+++ b/README.md
@@ -40,7 +40,7 @@ This project ensures compatibility with the following supported Python versions:
 ### Note on Amazon CloudWatch Application Signals
 [Amazon CloudWatch Application Signals](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-Application-Monitoring-Sections.html) components are designed to seamlessly work with all library instrumentations offered by [OpenTelemetry Python auto-instrumentation](https://github.com/open-telemetry/opentelemetry-python-contrib/blob/main/instrumentation/README.md). While upstream OpenTelemetry Python instrumentations are in beta, Application Signals components are stable, production ready and have also been tested for popular libraries/frameworks such as [Django, Boto3, and others](https://github.com/aws-observability/aws-otel-python-instrumentation/tree/main/contract-tests/images/applications). We will prioritize backward compatibility for Application Signals components, striving to ensure that they remain functional even in the face of potential breaking changes introduced by OpenTelemetry upstream libraries. Please [raise an issue](https://github.com/aws-observability/aws-otel-python-instrumentation/blob/main/CONTRIBUTING.md#reporting-bugsfeature-requests) if you notice Application Signals doesn't work for a particular OpenTelemetry supported library.
 
-### Checksum Verification
+## Checksum Verification
 Artifacts released will include a `.sha256` file for checksum verification starting from v0.7.0
 To verify, run the command `shasum -a 256 -c <artifact_name>.sha256` 
 It should return the output `<artifact_name>: OK` if the validation is successful