diff --git a/docs/proposals/karmada-operator/custom_ca_cert/README.md b/docs/proposals/karmada-operator/custom_ca_cert/README.md
index 4d3ee7fa1b52..c21eeef94dce 100644
--- a/docs/proposals/karmada-operator/custom_ca_cert/README.md
+++ b/docs/proposals/karmada-operator/custom_ca_cert/README.md
@@ -31,7 +31,7 @@ By enabling users to specify a custom CA certificate, this feature ensures that
 
 ### Goals
 
-- Allow users to specify a custom CA certificate which is used to sign the Karmada API Server certificate and for verifying client certificates
+- Allow users to specify a custom CA certificate which is used to sign the Karmada API Server certificate and for verifying client certificates.
 - Ensure that control plane instances deployed across multiple management clusters that span multiple data centers use the same CA, enabling secure and seamless cross-data center communication.
 - Enable operators to align Karmada control plane PKI with organizational policies for high availability and security.
 
@@ -39,7 +39,7 @@ By enabling users to specify a custom CA certificate, this feature ensures that
 
 - Change the default behavior of the Karmada operator when no custom CA is provided.
 - Alter the process of how control planes are connected to etcd.
-- Address custom CA requirements for other concerns such as PKI for an in-cluster ETCD instance or front proxy communications
+- Address custom CA requirements for other concerns such as PKI for an in-cluster ETCD instance or front proxy communications.
 
 ## Proposal