Apply suggestions from code review

Co-authored-by: Christopher Desiniotis <[email protected]>
Signed-off-by: Abigail McCarthy <[email protected]>

Author: a-mccarthy

gpu-operator/google-gke.rst

@@ -82,7 +82,7 @@ Prerequisites
 
 .. note::
 
-   When installing NVIDIA GPU Operator v25.10.0 on GKE, there is a known issue in the NVIDIA Container Toolkit v1.18.0, the default toolkit version, that will misconfigure the config.toml file and prevent GPU Operator containers from starting up correctly.
+   When installing NVIDIA GPU Operator on GKE 1.33+, there is a known issue where NVIDIA Container Toolkit will misconfigure the containerd `config.toml` file and prevent GPU Operator containers from starting up correctly.
 
    To resolve this issue, set the ``RUNTIME_CONFIG_SOURCE=file`` environment variable in the toolkit container to resolve this issue. 
    You can set this environment variable by setting the below in the ClusterPolicy CR:

gpu-operator/release-notes.rst

@@ -188,7 +188,7 @@ Known Issues
 
   Create the ConfigMap, then update the ClusterPolicy with the name of the configMap in the ``vgpuDeviceManager.config.name``, and restart the vgpu-device-manager pod.
 
-- When using GKE, there is a known issue in the NVIDIA Container Toolkit v1.18.0 that will miss configure the config.toml file and prevent GPU Operator containers from starting up correctly. 
+- When using GKE 1.33+, there is a known issue where NVIDIA Container Toolkit will misconfigure the containerd `config.toml` file and prevent GPU Operator containers from starting up correctly. 
   To resolve this issue, set the ``RUNTIME_CONFIG_SOURCE=file`` environment variable in the toolkit container to resolve this issue. 
   You can set this environment variable by setting the below in the ClusterPolicy CR: