Fix typo

5 files changed, 5 insertions, 5 deletions

diff --git a/_build/content/articles/ranch-2.0.0-rc.1.asciidoc b/_build/content/articles/ranch-2.0.0-rc.1.asciidoc
index 8065a0e8..77e8c623 100644
--- a/_build/content/articles/ranch-2.0.0-rc.1.asciidoc
+++ b/_build/content/articles/ranch-2.0.0-rc.1.asciidoc
@@ -14,7 +14,7 @@ great release.
 In Ranch 1.x, there is only one supervisor per Ranch listener
 to start and manage connection processes. Under high load
 (many clients rapidly connecting and/or disconnecting), the
-message queue of this one supervisor could becomes congested,
+message queue of this one supervisor could become congested,
 leading to declining accept rates or a stalled listener.
 
 Ranch 2.0 introduces the `num_conns_sups` option (defaulting
diff --git a/articles/index.html b/articles/index.html
index 05b4ead7..0d248e49 100644
--- a/articles/index.html
+++ b/articles/index.html
@@ -76,7 +76,7 @@
 
 		<p>Ranch 2.0.0-rc.1 has been released!
 We are getting very close to releasing Ranch 2.0! As most of the tremendous programming work was done by contributor Jan Uhlig, I will yield the floor and let him describe what went into this great release.
-In Ranch 1.x, there is only one supervisor per Ranch listener to start and manage connection processes. Under high load (many clients rapidly connecting and/or disconnecting), the message queue of this one supervisor could becomes congested, leading to declining accept rates or a stalled listener.</p>
+In Ranch 1.x, there is only one supervisor per Ranch listener to start and manage connection processes. Under high load (many clients rapidly connecting and/or disconnecting), the message queue of this one supervisor could become congested, leading to declining accept rates or a stalled listener.</p>
 
 		<p style="text-align:right">
 			<a class="read_more" href="https://ninenines.eu/articles/ranch-2.0.0-rc.1/">Read More</a>
diff --git a/articles/index.xml b/articles/index.xml
index c2270ff5..6b7675ff 100644
--- a/articles/index.xml
+++ b/articles/index.xml
@@ -19,7 +19,7 @@
       <guid>https://ninenines.eu/articles/ranch-2.0.0-rc.1/</guid>
       <description>Ranch 2.0.0-rc.1 has been released!
 We are getting very close to releasing Ranch 2.0! As most of the tremendous programming work was done by contributor Jan Uhlig, I will yield the floor and let him describe what went into this great release.
-In Ranch 1.x, there is only one supervisor per Ranch listener to start and manage connection processes. Under high load (many clients rapidly connecting and/or disconnecting), the message queue of this one supervisor could becomes congested, leading to declining accept rates or a stalled listener.</description>
+In Ranch 1.x, there is only one supervisor per Ranch listener to start and manage connection processes. Under high load (many clients rapidly connecting and/or disconnecting), the message queue of this one supervisor could become congested, leading to declining accept rates or a stalled listener.</description>
     </item>
     
     <item>
diff --git a/articles/ranch-2.0.0-rc.1/index.html b/articles/ranch-2.0.0-rc.1/index.html
index 29a987fd..40553ff5 100644
--- a/articles/ranch-2.0.0-rc.1/index.html
+++ b/articles/ranch-2.0.0-rc.1/index.html
@@ -71,7 +71,7 @@
 
 <p>Ranch <code>2.0.0-rc.1</code> has been released!</p>
 <p>We are getting very close to releasing Ranch 2.0! As most of the tremendous programming work was done by contributor Jan Uhlig, I will yield the floor and let him describe what went into this great release.</p>
-<p>In Ranch 1.x, there is only one supervisor per Ranch listener to start and manage connection processes. Under high load (many clients rapidly connecting and/or disconnecting), the message queue of this one supervisor could becomes congested, leading to declining accept rates or a stalled listener.</p>
+<p>In Ranch 1.x, there is only one supervisor per Ranch listener to start and manage connection processes. Under high load (many clients rapidly connecting and/or disconnecting), the message queue of this one supervisor could become congested, leading to declining accept rates or a stalled listener.</p>
 <p>Ranch 2.0 introduces the <code>num_conns_sups</code> option (defaulting to the number of acceptors), which allows the message load to be divided between the specified number of connection supervisors. This improves accept concurrency at the same time.</p>
 <p>Another bottleneck is a possible congestion of the syn queue of a listening socket. The reason is located within the operating system&apos;s TCP/IP implementation, and on Linux the <code>SO_REUSEPORT</code> socket option was introduced to address it. What it boils down to is that you can have more than just one socket listening on the same port, causing the sockets to be load-balanced when accepting connections.</p>
 <p>Ranch 1.x always uses a single listening socket per listener, shared between the acceptors. With a trick, starting multiple Ranch listeners on the same port, it is already possible to make use of the <code>SO_REUSEPORT</code> feature. But that&apos;s not ideal.</p>
diff --git a/index.xml b/index.xml
index c4feca24..49fbd2a3 100644
--- a/index.xml
+++ b/index.xml
@@ -2616,7 +2616,7 @@ HTTP IANA Registries HTTP Method Registry  HTTP Status Code Registry  Message He
       <guid>https://ninenines.eu/articles/ranch-2.0.0-rc.1/</guid>
       <description>Ranch 2.0.0-rc.1 has been released!
 We are getting very close to releasing Ranch 2.0! As most of the tremendous programming work was done by contributor Jan Uhlig, I will yield the floor and let him describe what went into this great release.
-In Ranch 1.x, there is only one supervisor per Ranch listener to start and manage connection processes. Under high load (many clients rapidly connecting and/or disconnecting), the message queue of this one supervisor could becomes congested, leading to declining accept rates or a stalled listener.</description>
+In Ranch 1.x, there is only one supervisor per Ranch listener to start and manage connection processes. Under high load (many clients rapidly connecting and/or disconnecting), the message queue of this one supervisor could become congested, leading to declining accept rates or a stalled listener.</description>
     </item>
     
     <item>