diff options
| author | Dave Whiteland <dave@mysociety.org> | 2014-07-09 15:55:36 +0100 |
|---|---|---|
| committer | Dave Whiteland <dave@mysociety.org> | 2014-07-09 15:55:36 +0100 |
| commit | 008de728188f770ee6fe3bfe1bd657c29e685535 (patch) | |
| tree | 3472147005993822d0a08d52e6bdb6313716ed98 /docs/running/upgrading.md | |
| parent | 8743372722bafff935c54d56250d292e9ddd8597 (diff) | |
change glossary link class to glossary__link throughout
Diffstat (limited to 'docs/running/upgrading.md')
| -rw-r--r-- | docs/running/upgrading.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/running/upgrading.md b/docs/running/upgrading.md index 2142bfd47..ab8db2385 100644 --- a/docs/running/upgrading.md +++ b/docs/running/upgrading.md @@ -17,7 +17,7 @@ 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 +<a href="{{site.baseurl}}docs/glossary/#production" class="glossary__link">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). |