Apply suggestions from code review

Co-authored-by: Rajath Agasthya <rajathagasthya@gmail.com>

Author: a-mccarthy

gpu-operator/gpu-operator-mig.rst

@@ -109,7 +109,7 @@ Configuring MIG Profiles
 ************************
 
 When MIG is enabled, nodes are labeled with ``nvidia.com/mig.config: all-disabled`` by default.
-To use a profile on a node, you add a label with the desired profile, for example, ``nvidia.com/mig.config=all-1g.10gb``.
+To use a profile on a node, update the label value with the desired profile, for example, ``nvidia.com/mig.config=all-1g.10gb``.
 
 Introduced in GPU Operator v26.3.0, MIG Manager generates the MIG configuration for a node at runtime from the available hardware.
 The configuration is generated on startup, discovering MIG profiles for each MIG-capable GPU on a node using `NVIDIA Management Library (NVML) <https://developer.nvidia.com/management-library-nvml>`_, then writing it to a ConfigMap for each MIG-capable node in your cluster. 
@@ -570,7 +570,7 @@ Finally, it applies the MIG reconfiguration and restarts the GPU pods and possib
 The MIG reconfiguration can also involve rebooting a node if a reboot is required to enable MIG mode.
 
 The default MIG profiles are specified in the ``<node-name>-mig-config`` ConfigMap.
-This ConfigMap is auto-generated by the Operator for each MIG-capable node and contains the standard MIG profiles for the available GPUs on the node.
+This ConfigMap is auto-generated by the MIG Manager for each MIG-capable node and contains the standard MIG profiles for the available GPUs on the node.
 You can also configure the operator to configure a custom ConfigMap to use instead of the auto-generated one.
 
 You can specify one of these profiles to apply to the ``mig.config`` label to trigger a reconfiguration of the MIG geometry.