move frontmatter break and notes

Author: vepatel

site/content/releases.md

@@ -6,6 +6,36 @@ doctypes:
 title: Releases
 toc: true
 weight: 2100
+
+---
+{{< note >}}
+FIPS compliant images are currently impacted by compatibility issues with a dependent library.
+
+We recommend against:
+1. Patching older FIPS images, which could re-introduce the incompatible dependency.
+2. Building new custom FIPS images.
+{{< /note >}}
+
+{{< note >}}
+In our next major release, `v4.0.0`, the default log library for NGINX Ingress Controller will be changed from `golang/glog` to `log/slog`.
+This will mean that logs generated by NGINX Ingress Controller will be in a structured format with the option to choose a `string` or `json` output.
+This will not affect logs generated by NGINX.
+To ensure backwards compatibility, we will ensure the existing log format, `glog`, will be maintained through a configuration option for the next 3 releases.
+{{< /note >}}
+
+{{< important >}}
+CRD version removal notice.
+In our next major release, `v4.0.0`, support for the following apiVersions for these listed CRDs will be dropped:
+1. `k8s.nginx.org/v1alpha` for `GlobalConfiguration`
+2. `k8s.nginx.org/v1alpha` for `Policy`
+3. `k8s.nginx.org/v1alpha` for `TransportServer`
+
+Prior to upgrading, **please ensure** that any of these resources deployed as `apiVersion: k8s.nginx.org/v1alpha1` are upgraded to `apiVersion: k8s.nginx.org/v1`
+If a resource of `kind: GlobalConfiguration`, `kind: Policy` or `kind: TransportServer` are deployed as `apiVersion: k8s.nginx.org/v1alpha1`, these resources will be **deleted** when upgrading from, at least, `v3.4.0` to `v4.0.0`
+
+When `v4.0.0` is released, the release notes will contain the required upgrade steps to go from `v3.X.X` to `v4.X.X`
+{{< /important >}}
+
 ## 3.7.2
 
 25 Nov 2024
@@ -38,36 +68,7 @@ We will provide technical support for NGINX Ingress Controller on any Kubernetes
 its provider and that passes the Kubernetes conformance tests. This release was fully tested on the following Kubernetes
 versions: 1.25-1.31.
 
-
 ---
-{{< note >}}
-FIPS compliant images are currently impacted by compatibility issues with a dependent library.
-
-We recommend against:
-1. Patching older FIPS images, which could re-introduce the incompatible dependency.
-2. Building new custom FIPS images.
-{{< /note >}}
-
-{{< note >}}
-In our next major release, `v4.0.0`, the default log library for NGINX Ingress Controller will be changed from `golang/glog` to `log/slog`.
-This will mean that logs generated by NGINX Ingress Controller will be in a structured format with the option to choose a `string` or `json` output.
-This will not affect logs generated by NGINX.
-To ensure backwards compatibility, we will ensure the existing log format, `glog`, will be maintained through a configuration option for the next 3 releases.
-{{< /note >}}
-
-{{< important >}}
-CRD version removal notice.
-In our next major release, `v4.0.0`, support for the following apiVersions for these listed CRDs will be dropped:
-1. `k8s.nginx.org/v1alpha` for `GlobalConfiguration`
-2. `k8s.nginx.org/v1alpha` for `Policy`
-3. `k8s.nginx.org/v1alpha` for `TransportServer`
-
-Prior to upgrading, **please ensure** that any of these resources deployed as `apiVersion: k8s.nginx.org/v1alpha1` are upgraded to `apiVersion: k8s.nginx.org/v1`
-If a resource of `kind: GlobalConfiguration`, `kind: Policy` or `kind: TransportServer` are deployed as `apiVersion: k8s.nginx.org/v1alpha1`, these resources will be **deleted** when upgrading from, at least, `v3.4.0` to `v4.0.0`
-
-When `v4.0.0` is released, the release notes will contain the required upgrade steps to go from `v3.X.X` to `v4.X.X`
-{{< /important >}}
-
 ## 3.7.1
 
 06 Nov 2024