summary refs log tree commit diff
path: root/v1.57/print.html
diff options
context:
space:
mode:
authorreivilibre <reivilibre@users.noreply.github.com>2022-04-19 10:30:29 +0000
committerreivilibre <reivilibre@users.noreply.github.com>2022-04-19 10:30:29 +0000
commit2d2f2f4dfda604fa4ee1856e2064db1a19f0df30 (patch)
treeb47d14418764e89d8a636dc0681b0e206eeb535a /v1.57/print.html
parentdeploy: 3c758d9808ddc00ee96c5426dda3caea356c8745 (diff)
downloadsynapse-2d2f2f4dfda604fa4ee1856e2064db1a19f0df30.tar.xz
deploy: dfc7646504cef3e4ff396c36089e1c6f1b1634de
Diffstat (limited to 'v1.57/print.html')
-rw-r--r--v1.57/print.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/v1.57/print.html b/v1.57/print.html
index 3104a8dec3..4c4d3b1b0e 100644
--- a/v1.57/print.html
+++ b/v1.57/print.html
@@ -1612,7 +1612,7 @@ worker for application service traffic, <strong>it must be stopped</strong> when
 (which normally happens when the main process is upgraded), to ensure the change is made safely
 without any risk of reusing transaction IDs.</p>
 <p>Deployments which do not use separate worker processes can be upgraded as normal. Similarly,
-deployments where no applciation services are in use can be upgraded as normal.</p>
+deployments where no application services are in use can be upgraded as normal.</p>
 <details>
 <summary><b>Recovering from an incorrect upgrade</b></summary>
 <p>If the database schema is upgraded <em>without</em> stopping the worker responsible