Update small docs issues (#307)

* Update troubleshooting guide with cri-o issue

Signed-off-by: Abigail McCarthy <[email protected]>

* add additional error message

Signed-off-by: Abigail McCarthy <[email protected]>

* fix heading

Signed-off-by: Abigail McCarthy <[email protected]>

* remove stuck

Signed-off-by: Abigail McCarthy <[email protected]>

* typo fix

Signed-off-by: Abigail McCarthy <[email protected]>

* update 25.3.4 release notes

Signed-off-by: Abigail McCarthy <[email protected]>

* remove recommended from 25.10.0

Signed-off-by: Abigail McCarthy <[email protected]>

* remove kata docs

Signed-off-by: Abigail McCarthy <[email protected]>

---------

Signed-off-by: Abigail McCarthy <[email protected]>

Author: a-mccarthy

gpu-operator/getting-started.rst

@@ -261,10 +261,6 @@ To view all the options, run ``helm show values nvidia/gpu-operator``.
        You can enable GDRCopy if you use the :doc:`gpu-driver-configuration`.
      - ``false``
 
-   * - ``kataManager.enabled``
-     - The GPU Operator deploys NVIDIA Kata Manager when this field is ``true``.
-       Refer to :doc:`gpu-operator-kata` for more information.
-     - ``false``
 
    * - ``mig.strategy``
      - Controls the strategy to be used with MIG on supported NVIDIA GPUs. Options
@@ -299,7 +295,7 @@ To view all the options, run ``helm show values nvidia/gpu-operator``.
      - Specifies the default type of workload for the cluster, one of ``container``, ``vm-passthrough``, or ``vm-vgpu``.
 
        Setting ``vm-passthrough`` or ``vm-vgpu`` can be helpful if you plan to run all or mostly virtual machines in your cluster.
-       Refer to :doc:`KubeVirt <gpu-operator-kubevirt>`, or :doc:`Kata Containers <gpu-operator-kata>`.
+       Refer to :doc:`KubeVirt <gpu-operator-kubevirt>`.
      - ``container``
 
    * - ``toolkit.enabled``

gpu-operator/google-gke.rst

@@ -84,7 +84,7 @@ Prerequisites
 
    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. 
+   To resolve this issue, set the ``RUNTIME_CONFIG_SOURCE=file`` environment variable in the toolkit container. 
    You can set this environment variable by setting the below in the ClusterPolicy CR:
 
    .. code-block:: yaml