aboutsummaryrefslogtreecommitdiffstats
path: root/docs/running/upgrading.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/running/upgrading.md')
-rw-r--r--docs/running/upgrading.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/running/upgrading.md b/docs/running/upgrading.md
index 4074e7a14..611712bf6 100644
--- a/docs/running/upgrading.md
+++ b/docs/running/upgrading.md
@@ -15,8 +15,8 @@ Upgrading Alaveteli
The developer team policy is that the `master` branch in git should always
contain the latest stable release -- so you'll be up to date if you pull from
-the `master` branch. However, on your <a
-href="{{site.baseurl}}docs/glossary/#production" class="glossary">production site</a>,
+the `master` branch. However, on your
+<a href="{{site.baseurl}}docs/glossary/#production" class="glossary">production site</a>,
you should know precisely what version you're running, and deploy Alaveteli
from a [*specific* release tag](https://github.com/mysociety/alaveteli/releases).