diff --git a/docs/reference/spiderpool-agent.md b/docs/reference/spiderpool-agent.md
index 7034c5a84e..99347670fa 100644
--- a/docs/reference/spiderpool-agent.md
+++ b/docs/reference/spiderpool-agent.md
@@ -37,9 +37,9 @@ To optimize the kernel network configuration of a node, spiderpool-agent will by
 | net.ipv6.neigh.default.gc_thresh3 | 28160 | This is the hard maximum number of entries to keep in the ARP cache. The garbage collector will always run if there are more than this number of entries in the cache. for ipv6. Note: this is only avaliable in some low kernel version.|
 | net.ipv4.conf.all.arp_notify | 1 |  Generate gratuitous arp requests when device is brought up or hardware address changes.|
 | net.ipv4.conf.all.forwarding | 1 | enable ipv4 forwarding |
-| net.ipv4.conf.all.forwarding | 1 | enable ipv6 forwarding |
+| net.ipv6.conf.all.forwarding | 1 | enable ipv6 forwarding |
 
-To optimize the kernel network configuration of a node, spiderpool-agent configures some kernel parameters (such as a, etc.) by default. Some kernel parameters can only be set in certain kernel versions, so we will ignore the "kernel parameter does not exist" error when configure the kernel parameters.
+Note: Some kernel parameters can only be set in certain kernel versions, so we will ignore the "kernel parameter does not exist" error when configure the kernel parameters. Example: `net.ipv6.neigh.default.gc_thresh3`.
 
 Users can edit the `spiderpoolAgent.securityContext` field of values.yaml in the chart before installing spiderpool to update the kernel parameters that need additional configuration, or manually edit spiderpool-agent daemonSet after installing Spiderpool, and then restart spiderpool-agent pods: