Imported Upstream version 7.6.1upstream/7.6.1

1 files changed, 2 insertions, 2 deletions

diff --git a/doc/imuxsock.html b/doc/imuxsock.html
index 123771f..02b2f18 100644
--- a/doc/imuxsock.html
+++ b/doc/imuxsock.html
@@ -42,7 +42,7 @@ severity and configure things accordingly.
 To turn off rate limiting, set the interval to zero.
 <p><b>Unix log sockets can be flow-controlled.</b> That is, if processing queues fill up,
 the unix socket reader is blocked for a short while. This may be useful to prevent overruning
-the queues (which may cause exessive disk-io where it actually would not be needed). However,
+the queues (which may cause excessive disk-io where it actually would not be needed). However,
 flow-controlling a log socket (and especially the system log socket) can lead to a very
 unresponsive system. As such, flow control is disabled by default. That means any log records
 are places as quickly as possible into the processing queues. If you would like to have
@@ -125,7 +125,7 @@ module documentation for a more in-depth description.
 to the next socket.</li>
 <li><b>RateLimit.Interval</b> [number] - specifies the rate-limiting
 interval in seconds.  Default value is 0, which turns off rate limiting. Set it to a number
-of seconds (5 recommended) to activate rate-limiting. The default of 0 has been choosen 
+of seconds (5 recommended) to activate rate-limiting. The default of 0 has been chosen
 as people experienced problems with this feature activated by default. Now it needs an
 explicit opt-in by setting this parameter.
 </li>