From 6b78680875d9e721d46e4f3d34047c6a3fbd2f33 Mon Sep 17 00:00:00 2001
From: DMRobertson <DMRobertson@users.noreply.github.com>
Date: Mon, 1 Nov 2021 11:36:20 +0000
Subject: deploy: ece84f2c450d986e54acc80971225fb02f4e1d05

---
 develop/synctl_workers.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'develop/synctl_workers.html')

diff --git a/develop/synctl_workers.html b/develop/synctl_workers.html
index 9f3b3c8077..38147da9e3 100644
--- a/develop/synctl_workers.html
+++ b/develop/synctl_workers.html
@@ -196,14 +196,14 @@ synchrotron, you might write:</p>
 <p>Finally, to actually run your worker-based synapse, you must pass synctl the <code>-a</code>
 commandline option to tell it to operate on all the worker configurations found
 in the given directory, e.g.:</p>
-<pre><code>synctl -a $CONFIG/workers start
+<pre><code class="language-sh">synctl -a $CONFIG/workers start
 </code></pre>
 <p>Currently one should always restart all workers when restarting or upgrading
 synapse, unless you explicitly know it's safe not to.  For instance, restarting
 synapse without restarting all the synchrotrons may result in broken typing
 notifications.</p>
 <p>To manipulate a specific worker, you pass the -w option to synctl:</p>
-<pre><code>synctl -w $CONFIG/workers/worker1.yaml restart
+<pre><code class="language-sh">synctl -w $CONFIG/workers/worker1.yaml restart
 </code></pre>
 
                     </main>
-- 
cgit 1.5.1