From dc700e1e58b4a3ed818e9df0a902ec6013955cd8 Mon Sep 17 00:00:00 2001 From: =?utf8?q?=C3=86var=20Arnfj=C3=B6r=C3=B0=20Bjarmason?= Date: Mon, 2 May 2005 04:22:14 +0000 Subject: [PATCH] * eg => e.g. --- UPGRADE | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/UPGRADE b/UPGRADE index 85485272b5..4449ffa233 100644 --- a/UPGRADE +++ b/UPGRADE @@ -1,11 +1,11 @@ == The basic theory == -Generally, within a stable release series (eg 1.4.0, 1.4.1, etc) there +Generally, within a stable release series (e.g. 1.4.0, 1.4.1, etc) there are no required database changes, and upgrading should require no more than copying the new source files over the old ones. If there are larger changes, such as upgrading from one release series -to another (eg from 1.3.12 to 1.4.3), then you may need to update the +to another (e.g. from 1.3.12 to 1.4.3), then you may need to update the database schema and configuration. Basically, to upgrade a wiki you: -- 2.20.1