Fix typo: "can controlled" → "can be controlled" in quorum-queues docs

Co-authored-by: Zerpet <[email protected]>

Author: Copilot

docs/quorum-queues/index.md

@@ -735,7 +735,7 @@ When a new quorum queue is declared, the set of nodes that will host its
 members is randomly picked, but will always include the node the client that
 declares the queue is connected to.
 
-Which replica becomes the initial leader can controlled using three options:
+Which replica becomes the initial leader can be controlled using three options:
 
 1. Setting the `queue-leader-locator` [policy](./policies) key (recommended)
 2. By defining the `queue_leader_locator` key in [the configuration file](./configure#configuration-files) (recommended)

versioned_docs/version-3.13/quorum-queues/index.md

@@ -470,7 +470,7 @@ be reasonably evenly distributed across cluster nodes.
 When a new quorum queue is declared, the set of nodes that will host its
 replicas is randomly picked, but will always include the node the client that declares the queue is connected to.
 
-Which replica becomes the initial leader can controlled using three options:
+Which replica becomes the initial leader can be controlled using three options:
 
 1. Setting the `queue-leader-locator` [policy](./policies) key (recommended)
 2. By defining the `queue_leader_locator` key in [the configuration file](./configure#configuration-files) (recommended)

versioned_docs/version-4.0/quorum-queues/index.md

@@ -735,7 +735,7 @@ When a new quorum queue is declared, the set of nodes that will host its
 members is randomly picked, but will always include the node the client that
 declares the queue is connected to.
 
-Which replica becomes the initial leader can controlled using three options:
+Which replica becomes the initial leader can be controlled using three options:
 
 1. Setting the `queue-leader-locator` [policy](./policies) key (recommended)
 2. By defining the `queue_leader_locator` key in [the configuration file](./configure#configuration-files) (recommended)

versioned_docs/version-4.1/quorum-queues/index.md

@@ -735,7 +735,7 @@ When a new quorum queue is declared, the set of nodes that will host its
 members is randomly picked, but will always include the node the client that
 declares the queue is connected to.
 
-Which replica becomes the initial leader can controlled using three options:
+Which replica becomes the initial leader can be controlled using three options:
 
 1. Setting the `queue-leader-locator` [policy](./policies) key (recommended)
 2. By defining the `queue_leader_locator` key in [the configuration file](./configure#configuration-files) (recommended)