Update tc-dualpi2.8

man/man8/tc-dualpi2.8

@@ -62,7 +62,7 @@ Simple implementation
 .IP \(bu 4
 Guaranteed stability and fast responsiveness
 .PD
-The detailed PI2 parameters (alpha, beta, and tupdate) of DualPI2 are hard to get right and typically give bad results if just tried or guessed. DualPI2 has a set of default parameters that can be used for the general internet were the maximum RTT is around 100ms and the typical RTT is around 15ms. These parameters need to be calculated to a coherent set with a typical objective in mind. It is highly recommended to use the max_rtt and typical_rtt (or target) helper parameters if your deployment is deviating from the above objectives (e.g. in a data center). The are used to provide the theoretically optimal PI2 parameters (alpfa, beta and tupdate) for those objectives, and that can be used as a basis for further finetuning, experimentation and testing if desired.
+The detailed PI2 parameters (alpha, beta, and tupdate) of DualPI2 are hard to get right and typically give bad results if just tried or guessed. These parameters need to be calculated to a coherent set with a typical objective in mind. DualPI2 has a set of default parameters that can be used for the general internet were the maximum RTT is around 100ms and the typical RTT is around 15ms. It is highly recommended to use the max_rtt and typical_rtt (or target) helper parameters if your deployment is deviating from the above objectives (e.g. in a data center). These helpers are used to provide the theoretically optimal PI2 parameters (alpfa, beta and tupdate) for those objectives, and that can be used as a basis for further finetuning, experimentation and testing if desired.
 
 .SH ALGORITHM
 DUALPI2 is designed to provide low loss and low latency to L4S traffic, without harming classic traffic. Every update interval a new internal base probability is calculated, based on queue delay. The base probability is updated with a delta based on the difference between the current queue delay and the