Formatting and changing some words as per the standards, and removing…

… extra spaces

content/en/docs/reference/command-line-tools-reference/feature-gates.md

@@ -610,7 +610,7 @@ Each feature gate is designed for enabling/disabling a specific feature:
   filesystem walk for better performance and accuracy.
 - `LogarithmicScaleDown`: Enable semi-random selection of pods to evict on controller scaledown
   based on logarithmic bucketing of pod timestamps.
-- `MatchLabelKeysInPodTopologySpread`: Enable the `matchLabelKeys` field for 
+- `MatchLabelKeysInPodTopologySpread`: Enable the `matchLabelKeys` field for
   [Pod topology spread constraints](/docs/concepts/scheduling-eviction/topology-spread-constraints/).
 - `MaxUnavailableStatefulSet`: Enables setting the `maxUnavailable` field for the
   [rolling update strategy](/docs/concepts/workloads/controllers/statefulset/#rolling-updates)

content/en/docs/tasks/kubelet-credential-provider/kubelet-credential-provider.md

@@ -11,7 +11,7 @@ content_type: task
 
 <!-- overview -->
 
-Starting from Kubernetes v1.20, the kubelet can dynamically retrieve credentials for a container image registry
+Starting from Kubernetes *v1.20*, the kubelet can dynamically retrieve credentials for a container image registry
 using exec plugins. The kubelet and the exec plugin communicate through stdio (stdin, stdout, and stderr) using
 Kubernetes versioned APIs. These plugins allow the kubelet to request credentials for a container registry dynamically
 as opposed to storing static credentials on disk. For example, the plugin may talk to a local metadata server to retrieve
@@ -27,7 +27,7 @@ This guide demonstrates how to configure the kubelet's image credential provider
 
 ## {{% heading "prerequisites" %}}
 
-* The kubelet image credential provider is introduced in v1.20 as an alpha feature. As with other alpha features,
+* The kubelet image credential provider is introduced in *v1.20* as an alpha feature. As with other alpha features,
   a feature gate `KubeletCredentialProviders` must be enabled on only the kubelet for the feature to work.
 * A working implementation of a credential provider exec plugin. You can build your own plugin or use one provided by cloud providers.
 
@@ -54,7 +54,7 @@ should be invoked for which container images. Here's an example configuration fi
 ```yaml
 apiVersion: kubelet.config.k8s.io/v1alpha1
 kind: CredentialProviderConfig
-# providers is a list of credential provider plugins that will be enabled by the kubelet.
+# providers is a list of credential provider helper plugins that will be enabled by the kubelet.
 # Multiple providers may match against a single image, in which case credentials
 # from all providers will be returned to the kubelet. If multiple providers are called
 # for a single image, the results are combined. If providers return overlapping
@@ -74,7 +74,7 @@ providers:
     # Globs can be used in the domain, but not in the port or the path. Globs are supported
     # as subdomains like '*.k8s.io' or 'k8s.*.io', and top-level-domains such as 'k8s.*'.
     # Matching partial subdomains like 'app*.k8s.io' is also supported. Each glob can only match
-    # a single subdomain segment, so *.io does not match *.k8s.io.
+    # a single subdomain segment, so `*.io` does **not** match `*.k8s.io`.
     #
     # A match exists between an image and a matchImage when all of the below are true:
     # - Both contain the same number of domain parts and each part matches.