diff --git a/docbook/src/main/doc/adoc/content/chapter-5-Advanced_User_Guide.adoc b/docbook/src/main/doc/adoc/content/chapter-5-Advanced_User_Guide.adoc
index 9d22c2665..39ddc8678 100644
--- a/docbook/src/main/doc/adoc/content/chapter-5-Advanced_User_Guide.adoc
+++ b/docbook/src/main/doc/adoc/content/chapter-5-Advanced_User_Guide.adoc
@@ -8978,10 +8978,100 @@ The throttling configuration can be defined in the `jbossws-endpoint-config.xml`
```
-This configuraiton file set a requestCountThreshold "5" to enable the throttling and returns the http response code 419
+This configuration file set a requestCountThreshold "5" to enable the throttling and returns the http response code 419
to the client when the total request count reaches 5. This is totally for demo purpose, please don't use in any situation
except for the test purpose.
+Besides the requestPermits,there are other items can be configured with EndpointMetricsThrottlingManager:
+ - faultPermit: The number of faults allowed before throttling takes effect."
+ - requestPermit: The number of requests allowed before throttling takes effect."
+ - averageProcessingTimePermit: The average processing time in milliseconds; if it exceeds this value, throttling takes effect.
+ - maxProcessingTimePermit: The maximum processing time in milliseconds; if it exceeds this value, throttling takes effect.
+ - minProcessingTimePermit: The minimum processing time in milliseconds; if it exceeds this value, throttling takes effect.
+ - totalProcessingTimePermit: The total processing time in milliseconds; if it exceeds this value, throttling takes effect.
+ - responseStatusCode: The response code if the throttling takes effect and default is 429.
+ - delayTime:When the response code is set to 503, this value in milliseconds will finally be set with Retry-After header in response when throttling takes effect.
+To allow users to configure throttling more easily, there is an out-of-the-box RateLimitThrottlingManager that users can utilize to set traffic limits.
+This RateLimitThrottlingManager enables users to define the permitted number of requests within a specified period.
+To simplify this process, it offers the permitsPerMin configuration item, which allows users to set the number of
+permitted requests per minute. This configuration internally sets the period to 60 seconds and adjusts the permitted number of
+requests based on the user's specifications in the jaxws-endpoint-config.xml. Here is the configuration example which is
+using `permitsPerMin` to limit the 5 requests in one minute:
+```
+
+
+
+
+ org.jboss.test.ws.jaxws.cxf.throttling.HelloImpl
+
+ cxf.features
+ ##throttlingFeature
+
+
+ ##throttlingFeature
+ org.jboss.wsf.stack.cxf.features.throttling.JBossWSThrottlingFeature
+
+
+ ##throttlingFeature.throttlingManager
+ ##throttlingManager
+
+
+ ##throttlingManager
+ org.jboss.wsf.stack.cxf.features.throttling.RateLimitThorttlingManager
+
+
+ ##throttlingManager.permitsPerMin
+ 5
+
+
+
+```
+
+Users can use the `period` and `permitsPerPeriod` settings to define the number of requests allowed within any specified time period.
+Below is an example of the jaxws-endpoint-config.xml configuration to control 5 requests in 30 seconds:
+```
+
+
+
+
+ org.jboss.test.ws.jaxws.cxf.throttling.HelloImpl
+
+ cxf.features
+ ##throttlingFeature
+
+
+ ##throttlingFeature
+ org.jboss.wsf.stack.cxf.features.throttling.JBossWSThrottlingFeature
+
+
+ ##throttlingFeature.throttlingManager
+ ##throttlingManager
+
+
+ ##throttlingManager
+ org.jboss.wsf.stack.cxf.features.throttling.RateLimitThorttlingManager
+
+
+ ##throttlingManager.period
+ 30
+
+
+ ##throttlingManager.permitsPerPeriod
+ 5
+
+
+
+```
+
+Please note that both of these ThrottlingManagers are based on the web service endpoint metrics and require the web service
+subsystem's statistics to be enabled. Before using either of these ThrottlingManagers, ensure that statistics
+are enabled with the jboss-cli:
+
+```
+./subsystem=webservices:write-attribute(name=statistics-enabled,value=true)
+```
\ No newline at end of file