Docs typo fixes

Signed-off-by: LavredisG <[email protected]>

docs/faq/faq.md

@@ -1,5 +1,5 @@
 ---
-title: FAQ(Frequently Asked Questions)
+title: FAQ (Frequently Asked Questions)
 ---
 
 ## What is the difference between PropagationPolicy and ClusterPropagationPolicy?

docs/key-features/features.md

@@ -29,20 +29,20 @@ Karmada supports:
   * Toleration: Scheduling based on Taint and Toleration.
   * SpreadConstraint: Scheduling based on cluster topology.
   * ReplicasScheduling: Replication mode and split mode for instanced workloads.
-* Differential configuration([OverridePolicy](../userguide/scheduling/override-policy.md)):
+* Differential configuration ([OverridePolicy](../userguide/scheduling/override-policy.md)):
   * ImageOverrider: Differentiated configuration of mirrors.
   * ArgsOverrider: Differentiated configuration of execution parameters.
   * CommandOverrider: Differentiated configuration for execution commands.
   * PlainText: Customized Differentiation Configuration.
 * [Support reschedule](../userguide/scheduling/descheduler.md) with following components:
-  * Descheduler(karmada-descheduler): Trigger rescheduling based on instance state changes in member clusters.
-  * Scheduler-estimator(karmada-scheduler-estimator): Provides the scheduler with a more precise desired state of the running instances of the member cluster.
+  * Descheduler (karmada-descheduler): Trigger rescheduling based on instance state changes in member clusters.
+  * Scheduler-estimator (karmada-scheduler-estimator): Provides the scheduler with a more precise desired state of the running instances of the member cluster.
 
-Much like k8s scheduling, Karmada support different scheduling policy. The overall scheduling process is shown in the figure below:  
+Much like k8s scheduling, Karmada supports different scheduling policies. The overall scheduling process is shown in the figure below:  
 
 ![overall-relationship.png](../resources/key-features/overall-scheduling.png)
 
-If one cluster does not have enough resource to accommodate their pods, Karmada will reschedule the pods. The overall rescheduling process is shown in the following figure:  
+If one cluster does not have enough resources to accommodate their pods, Karmada will reschedule the pods. The overall rescheduling process is shown in the following figure:  
 
 ![overall-relationship.png](../resources/key-features/overall-rescheduling.png)
 
@@ -69,7 +69,7 @@ Karmada supports:
   * User-defined resource, triggering webhook remote calls.
   * Fixed encoding in Karmada for some common resource types.
 * [Unified resource management](../userguide/globalview/aggregated-api-endpoint.md): Unified management for `create`, `update`, `delete`, `query`.
-* [Unified operations](../userguide/globalview/proxy-global-resource.md): Exec operations command(`describe`, `exec`, `logs`) in one k8s context.
+* [Unified operations](../userguide/globalview/proxy-global-resource.md): Exec operations command (`describe`, `exec`, `logs`) in one k8s context.
 * [Global search for resources and events](../tutorials/karmada-search.md):
   * Cache query: global fuzzy search and global precise search are supported.
   * Third-party storage: Search engine (Elasticsearch or OpenSearch), relational database, graph database are supported.
@@ -78,7 +78,7 @@ Users can access and operate all member clusters via karmada-apiserver:
 
 ![overall-relationship.png](../resources/key-features/unified-operation.png)
 
-Users also can check and search all member clusters resources via karmada-apiserver:  
+Users also can check and search all member clusters' resources via karmada-apiserver:  
 
 ![overall-relationship.png](../resources/key-features/unified-search.png)
 
@@ -89,7 +89,7 @@ Karmada supports:
 * [Unified authentication](../userguide/bestpractices/unified-auth.md):
   * Aggregate API unified access entry.
   * Access control is consistent with member clusters.
-* Unified resource quota(`FederatedResourceQuota`):
+* Unified resource quota (`FederatedResourceQuota`):
   * Globally configures the ResourceQuota of each member cluster.
   * Configure ResourceQuota at the federation level.
   * Collects the resource usage of each member cluster in real time.
@@ -100,13 +100,13 @@ Users can access all member clusters with unified authentication:
 
 ![overall-relationship.png](../resources/key-features/unified-access.png)
 
-Users also can defined global resource quota via `FederatedResourceQuota`:  
+Users also can define global resource quota via `FederatedResourceQuota`:  
 
 ![overall-relationship.png](../resources/key-features/unified-resourcequota.png)
 
 ## Cross-cluster service governance
 
-karmada supports:
+Karmada supports:
 
 * [Multi-cluster service discovery](../userguide/service/multi-cluster-service.md):
   * With ServiceExport and ServiceImport, achieving cross-cluster service discovery.