Address comments

Signed-off-by: Joe Nathan Abellard <[email protected]>

docs/proposals/karmada-components-extra-volumes/README.md → docs/proposals/karmada-operator/api-server-extra-volumes-volume-mounts/README.md

@@ -1,5 +1,5 @@
 ---
-title: Support to Specify Extra Volumes and Volume Mounts for Karmada Control Plane Components
+title: Support to Specify Extra Volumes and Volume Mounts for Karmada API Server Component
 authors:
 - "@jabellard"
 reviewers:
@@ -11,36 +11,41 @@ creation-date: 2024-07-29
 
 ---
 
-# Support to Specify Extra Volumes and Volume Mounts for Karmada Control Plane Components
+# Support to Specify Extra Volumes and Volume Mounts for Karmada API Server Component
 
 
 ## Summary
 
-This proposal aims to introduce the ability to specify extra volumes and volume mounts for Karmada control plane components when creating a Karmada instance managed by the Karmada operator. 
+This proposal aims to introduce the ability to specify extra volumes and volume mounts for the Karmada API server component when creating a Karmada instance managed by the Karmada operator. 
 This enhancement will extend the current configuration capabilities, allowing users to meet additional requirements such as having the ability to configure encryption at rest or to configure
 custom authentication webhooks.
 
 ## Motivation
-Currently, the Karmada operator allows specifying extra arguments for the Karmada control plane components, but lacks support for specifying extra volumes and volume mounts for those components. 
+Currently, the Karmada operator allows specifying extra arguments for the Karmada API server component, but lacks support for specifying extra volumes and volume mounts for it. 
 This limitation hinders certain use cases that require additional configurations for security and customization. For instance, as of today, it's not possible to configure a custom authentication 
 webhook nor encryption at rest. 
 
 ### Goals
-- Enable users to specify extra volumes and volume mounts for Karmada control plane components.
+- Enable users to specify extra volumes and volume mounts for Karmada API server components to unlock the following use cases:
+    - Ability to configure a custom authentication webhook
+    - Ability to configure encryption at rest
+
+It's important to note that although this support will unlock the aforementioned use cases, given that there is a lot that can be configured for the API server component by having the ability to specify not only extra args, but 
+also extra volumes and volume mounts, other potential use cases requiring similar configurations are also unlocked.
 
 
 ### Non-Goals
-- Introducing changes to the core functionality of the Karmada control plane components.
-- Overhauling the existing configuration of Karmada control plane components beyond the scope of adding extra volumes and volume mounts.
+- Introducing changes to the core functionality of the Karmada API server component.
+- Overhauling the existing configuration of the Karmada API server component beyond the scope of adding extra volumes and volume mounts.
 
 
 ## Proposal
-Introduce the new optional fields `ExtraVolumes` and `ExtraVolumeMounts` within Karmada control plane component configurations.
+Introduce the new optional fields `ExtraVolumes` and `ExtraVolumeMounts` within the Karmada API server component configuration.
 
 ## Design Details
 
-Introduce the new optional fields `ExtraVolumes` and `ExtraVolumeMounts` within Karmada control plane component configurations.
-Let's take the API server component as an example. With these new fields, the configuration would look as follows:
+Introduce the new optional fields `ExtraVolumes` and `ExtraVolumeMounts` within Karmada API server component configuration.
+With these new fields, the configuration would look as follows:
 ```go
 // KarmadaAPIServer holds settings to kube-apiserver component of the kubernetes.
 // Karmada uses it as its own apiserver in order to provide Kubernetes-native APIs.