diff --git a/gpu-operator/release-notes.rst b/gpu-operator/release-notes.rst
index e4dc7c6d0..eb3a8fd7d 100644
--- a/gpu-operator/release-notes.rst
+++ b/gpu-operator/release-notes.rst
@@ -41,6 +41,9 @@ Refer to the :ref:`GPU Operator Component Matrix` for a list of software compone
 New Features
 ------------
 
+* The NVIDIA GPU Operator now supports government ready components for NVIDIA AI Enterprise customers.
+  Government ready is NVIDIA's designation for software that meets applicable security requirements for deployment in your FedRAMP High or equivalent sovereign use case. For more information on NVIDIA's government ready support, refer to the :ref:`install-gpu-operator-gov-ready` deployment guide or the `AI Software for Regulated Environments White Paper <https://docs.nvidia.com/ai-enterprise/planning-resource/ai-software-regulated-environments-white-paper/latest/index.html>`_.
+
 * Updated software component versions:
 
   - NVIDIA Driver Manager for Kubernetes v0.9.0
diff --git a/openshift/openshift-virtualization.rst b/openshift/openshift-virtualization.rst
index 1cf782234..08a9d2004 100644
--- a/openshift/openshift-virtualization.rst
+++ b/openshift/openshift-virtualization.rst
@@ -91,8 +91,6 @@ Assumptions, constraints, and dependencies
 
 * Worker nodes running GPU accelerated VMs (with pGPU or vGPU) are assumed to be bare metal.
 
-* MIG-backed vGPUs are not supported.
-
 * The GPU Operator will not automate the installation of the vGPU guest driver inside KubeVirt VMs with vGPUs attached.
 
 * There are two separate device plugins – the NVIDIA k8s-device-plugin and the NVIDIA kubevirt-gpu-device-plugin.
@@ -682,6 +680,13 @@ Switching vGPU device configuration after one has been successfully applied assu
 
 To apply a new configuration after GPU Operator install, simply update the ``nvidia.com/vgpu.config`` node label.
 
+
+.. note::
+
+   On GPUs that support MIG, you have the option to select MIG-backed vGPU instances instead of time-sliced vGPU instances. 
+   To select a MIG-backed vGPU profile, label the node with the name of the MIG-backed vGPU profile.
+
+
 The following example shows a system with two **A10** GPUs.
 
 .. code-block:: console
@@ -725,8 +730,3 @@ You should now see 12 **A10-4Q** devices on the node, as 6 **A10-4Q** devices ca
    {
       "nvidia.com/NVIDIA_A10-4Q": "12"
    }
-
-.. note::
-   
-   On GPUs that support MIG, you have the option to select MIG-backed vGPU instances instead of time-sliced vGPU instances.
-   To select a MIG-backed vGPU profile, label the node with the name of the MIG-backed vGPU profile.