fixup! Update release instructions

Author: swiatekm

RELEASE.md

@@ -7,7 +7,8 @@ Steps to release a new version of the OpenTelemetry Operator:
    1. Operator, target allocator and opamp-bridge should be `$VERSION`. 
    1. OpenTelemetry Collector should be the latest collector version. The `major.minor` should typically match, with the patch portion being possibly different.
    1. The `autoinstrumentation-*` versions should match the latest supported versions in `autoinstrumentation/`.
-      - :warning: DO NOT BUMP JAVA PAST `1.32.X` AND DO NOT BUMP .NET PAST `1.2.0`. :warning: Upgrades past these versions will introduce breaking HTTP semantic convention changes.
+> [!WARNING]  
+> DO NOT BUMP JAVA PAST `1.32.X` AND DO NOT BUMP .NET PAST `1.2.0`. Upgrades past these versions will introduce breaking HTTP semantic convention changes.
 1. Check if the compatible OpenShift versions are updated in the `hack/add-openshift-annotations.sh` script.
 1. Update the bundle by running `make bundle VERSION=$VERSION`.
 1. Change the compatibility matrix in the [readme](./README.md) file, using the OpenTelemetry Operator version to be released and the current latest Kubernetes version as the latest supported version. Remove the oldest entry.