Update out-of-resource.md

docs/tasks/administer-cluster/out-of-resource.md

@@ -78,7 +78,7 @@ Each threshold has the following form:
 
 where:
 
-* `eviction-signal` is a eviction signal token as defined in the previous table.
+* `eviction-signal` is an eviction signal token as defined in the previous table.
 * `operator` is the desired relational operator, such as `<` (less than).
 * `quantity` is the eviction threshhold quantity, such as `1Gi`. These tokens must
 match the quantity representation used by Kubernetes. An eviction threshold can also
@@ -208,7 +208,7 @@ relative to their request for that resource are killed first. If no Pod
 has exceeded its request, the strategy targets the largest consumer of the
 starved resource.
 * `Guaranteed` Pods are guaranteed only when requests and limits are specified
-for all the containers and they are equal A `Guaranteed` Pod is guaranteed to
+for all the containers and they are equal. A `Guaranteed` Pod is guaranteed to
 never be evicted because of another Pod's resource consumption. If a system
 daemon (such as `kubelet`, `docker`, and `journald`) is consuming more resources
 than were reserved via `system-reserved` or `kube-reserved` allocations, and the
@@ -322,7 +322,7 @@ and trigger eviction assuming those Pods use less than their configured request.
 
 ### DaemonSet
 
-It is never desired for a `kubelet` to evict a `DaemonSet` Pod, since the Pod is
+It is never desired for `kubelet` to evict a `DaemonSet` Pod, since the Pod is
 immediately recreated and rescheduled back to the same node.
 
 At the moment, the `kubelet` has no ability to distinguish a Pod created