Resolve comments

docs/running-on-kubernetes.md

@@ -46,7 +46,7 @@ logs and remains in "completed" state in the Kubernetes API until it's eventuall
 Note that in the completed state, the driver pod does *not* use any computational or memory resources.
 
 The driver and executor pod scheduling is handled by Kubernetes. Communication to the Kubernetes API is done via fabric8, and we are 
-currently running <code>kubernetes-client</code> version <code>4.1.0</code>. Make sure that any infrastructure additions are weary of said version. It is possible to schedule the
+currently running <code>kubernetes-client</code> version <code>4.1.0</code>. Make sure that when you are making infrastructure additions that you are aware of said version. It is possible to schedule the
 driver and executor pods on a subset of available nodes through a [node selector](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#nodeselector)
 using the configuration property for it. It will be possible to use more advanced
 scheduling hints like [node/pod affinities](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity) in a future release.

resource-managers/kubernetes/core/src/main/scala/org/apache/spark/deploy/k8s/KubernetesUtils.scala

@@ -158,7 +158,8 @@ private[spark] object KubernetesUtils {
   }
 
   def formatTime(time: String): String = {
-    // TODO: Investigate form `time` comes in
+    // TODO: Investigate form `time` comes in as there was a DataType
+    // change from Time to String
     if (time != null) time else "N/A"
   }
 }