Conditionally #include headers.

[lyx.git] / UPGRADING

diff --git a/UPGRADING b/UPGRADING
index d46c2ea3b45d7bb69c16489f1c43c2db45564fc4..bc8aeb726201111672064e09c34698bc2dcd5a9a 100644 (file)
--- a/UPGRADING
+++ b/UPGRADING
@@ -4,7 +4,7 @@ How do I upgrade my existing LyX system to version 1.3.0?
 One of the perennial bug bears of LyX users in the past has been that
 they have had to run Edit->Reconfigure when starting their new version
 of the code for the first time. Strange and wonderful things would
 One of the perennial bug bears of LyX users in the past has been that
 they have had to run Edit->Reconfigure when starting their new version
 of the code for the first time. Strange and wonderful things would

-often result if they forgot to do this, so LyX 1.3.0 now runs 
+often result if they forgot to do this, so LyX 1.3.0 now runs

 Edit->Reconfigure automatically the first time the program is run.
 
 If you have your own layout files, you may need to update them a little:
 Edit->Reconfigure automatically the first time the program is run.
 
 If you have your own layout files, you may need to update them a little:


@@ -73,7 +73,7 @@ been re-implemented as "Floting figure" inset in 1.3.0. Old files will
 be converted automatically, but you may want to convert the
 1.2.x-style ERT constructs with the native solution (see section 3.8
 of the Extended Features manual).
 be converted automatically, but you may want to convert the
 1.2.x-style ERT constructs with the native solution (see section 3.8
 of the Extended Features manual).

- 
+

 Since LyX 1.2.0, the babel package is loaded after the user-defined
 preamble (because some packages really need to be loaded before
 babel). If you relied, on babel being loaded before your own
 Since LyX 1.2.0, the babel package is loaded after the user-defined
 preamble (because some packages really need to be loaded before
 babel). If you relied, on babel being loaded before your own