diff --git a/release_notes/ocp-4-14-release-notes.adoc b/release_notes/ocp-4-14-release-notes.adoc
index 41cc4ce022..8157c74035 100644
--- a/release_notes/ocp-4-14-release-notes.adoc
+++ b/release_notes/ocp-4-14-release-notes.adoc
@@ -1484,6 +1484,12 @@ With this release, `oc` commands now default to obtaining the credentials from P
 
 Additionally, the `oc registry login` command now stores credentials in the Podman configuration locations instead of the Docker configuration file locations.
 
+[discrete]
+[id="ocp-4-14-connect-requests"]
+=== Long-running pod requests are now recorded as CONNECT requests
+
+In {product-title} metrics, the pod `attach`, `exec`, `log`, `portforward`, and `proxy` requests are now recorded as `CONNECT` requests.
+
 [id="ocp-4-14-deprecated-removed-features"]
 == Deprecated and removed features
 
@@ -3414,7 +3420,7 @@ $ oc adm release info 4.14.44 --pullspecs
 
 * Previously, the Single-Root I/O Virtualization (SR-IOV) Operator did not expire the acquired lease during the Operator's shutdown operation. This impacted a new instance of the Operator, because the new instance had to wait for the lease to expire before the new instance was ready. With this release, an update to the Operator shutdown logic ensures that the Operator expires the lease when the Operator is shutting down. (link:https://issues.redhat.com/browse/OCPBUGS-44726[*OCPBUGS-44726*])
 
-* Previously, when you attempted to use Operator Lifecycle Manager (OLM) to upgrade an Operator, the upgrade was blocked and an `error validating existing CRs against new CRD's schema` message was generated. An issue existed with OLM, whereby OLM erroneously identified incompatibility issues with the validation of an existing custom resources definition (CRD) of the the new Operator version. With this release, the validation is corrected so that Operator upgrades are no longer blocked. (link:https://issues.redhat.com/browse/OCPBUGS-46595[*OCPBUGS-46595*]) 
+* Previously, when you attempted to use Operator Lifecycle Manager (OLM) to upgrade an Operator, the upgrade was blocked and an `error validating existing CRs against new CRD's schema` message was generated. An issue existed with OLM, whereby OLM erroneously identified incompatibility issues with the validation of an existing custom resources definition (CRD) of the the new Operator version. With this release, the validation is corrected so that Operator upgrades are no longer blocked. (link:https://issues.redhat.com/browse/OCPBUGS-46595[*OCPBUGS-46595*])
 
 * Previously, the `aws-sdk-go-v2` software development kit (SDK) failed to authenticate an `AssumeRoleWithWebIdentity` API operation on an {aws-first} {sts-first} cluster. With this release, `pod-identity-webhook` includes a default region so that the authenticate issue no longer exists. (link:https://issues.redhat.com/browse/OCPBUGS-46487[*OCPBUGS-46487*])