diff options
| author | Gareth Rees <gareth@mysociety.org> | 2014-10-15 16:44:27 +0100 |
|---|---|---|
| committer | Gareth Rees <gareth@mysociety.org> | 2014-10-15 16:44:27 +0100 |
| commit | 20035e1e497bb3d2355e95798c80d0ae263734fb (patch) | |
| tree | 214f7484f175e41dc35166810aeffac3c0af91ce /docs/running/upgrading.md | |
| parent | 3f9abdd0967e1c82064096711979b1ed087005fe (diff) | |
Fix typo
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 4c4db64ad..6bc54665c 100644 --- a/docs/running/upgrading.md +++ b/docs/running/upgrading.md @@ -44,7 +44,7 @@ Upgrading may just require pulling in the latest code -- but it may also require other changes ("further action"). For this reason, for anything other than a *patch* (see below), always read the [`CHANGES.md`](https://github.com/mysociety/alaveteli/blob/master/doc/CHANGES.md) -document **before** doing an uprade. This way you'll be able to prepare for any +document **before** doing an upgrade. This way you'll be able to prepare for any other changes that might be needed to make the new code work. ## How to upgrade the code |