Remove redundant closing spaces

Signed-off-by: tico88612 <[email protected]>
kubernetes · Apr 26, 2024 · 9a0bda6 · 9a0bda6
1 parent fb69fcd
commit 9a0bda6
Show file tree

Hide file tree

Showing 3 changed files with 4 additions and 4 deletions.
diff --git a/content/en/docs/concepts/services-networking/ingress.md b/content/en/docs/concepts/services-networking/ingress.md
@@ -6,7 +6,7 @@ api_metadata:
 - apiVersion: "networking.k8s.io/v1"
   kind: "Ingress"
 - apiVersion: "networking.k8s.io/v1"
-  kind: "IngressClass"  
+  kind: "IngressClass"
 content_type: concept
 description: >-
   Make your HTTP (or HTTPS) network service available using a protocol-aware configuration

diff --git a/content/en/docs/concepts/storage/persistent-volumes.md b/content/en/docs/concepts/storage/persistent-volumes.md
@@ -510,11 +510,11 @@ PersistentVolume types are implemented as plugins. Kubernetes currently supports
 * [`nfs`](/docs/concepts/storage/volumes/#nfs) - Network File System (NFS) storage
 
 The following types of PersistentVolume are deprecated but still available.
-If you are using these volume types except for `flexVolume`, `cephfs` and `rbd`, 
+If you are using these volume types except for `flexVolume`, `cephfs` and `rbd`,
 please install corresponding CSI drivers.
 
 * [`awsElasticBlockStore`](/docs/concepts/storage/volumes/#awselasticblockstore) - AWS Elastic Block Store (EBS)
-  (**migration on by default** starting v1.23) 
+  (**migration on by default** starting v1.23)
 * [`azureDisk`](/docs/concepts/storage/volumes/#azuredisk) - Azure Disk
   (**migration on by default** starting v1.23)
 * [`azureFile`](/docs/concepts/storage/volumes/#azurefile) - Azure File

diff --git a/content/en/docs/concepts/storage/volumes.md b/content/en/docs/concepts/storage/volumes.md
@@ -1129,7 +1129,7 @@ configuration changes to existing Storage Classes, PersistentVolumes or Persiste
 Existing PVs created by a in-tree volume plugin can still be used in the future without any configuration
 changes, even after the migration to CSI is completed for that volume type, and even after you upgrade to a
 version of Kubernetes that doesn't have compiled-in support for that kind of storage.
- 
+
 As part of that migration, you - or another cluster administrator - **must** have installed and configured
 the appropriate CSI driver for that storage. The core of Kubernetes does not install that software for you.