Minor documentation changes

git-svn-id: https://ledger-smb.svn.sourceforge.net/svnroot/ledger-smb/trunk@155 4979c152-3d1c-0410-bac9-87ea11338e46

3 files changed, 4 insertions, 4 deletions

diff --git a/doc/README b/doc/README
index 14fcdcc3..3846ea24 100755
--- a/doc/README
+++ b/doc/README
@@ -1,5 +1,5 @@
                 LedgerSMB Small Medium Business Accounting
-                     Version 1.1
+                     Version 1.1.1c
 
 
 DESCRIPTION:
diff --git a/doc/faq.html b/doc/faq.html
index dc739e05..59831b9c 100755
--- a/doc/faq.html
+++ b/doc/faq.html
@@ -37,10 +37,10 @@ Unfortunately, since this problem involves information loss, no
 solution can be automated without invalidating your accounting
 information.  </li></p>
 
-<p><li><h4>PostgreSQL 8.x</h4>
+<p><li><h4>Restoring old SQL-Ledger backups</h4>
 PostgreSQL added a restriction in v8.x that a sequence cannot be dropped
 after if it is referenced by a table. However backups created with
-LedgerSMB v2.6.13 and earlier have a DROP SEQUENCE step in the backup
+SQL-Ledger v2.6.13 and earlier have a DROP SEQUENCE step in the backup
 which will fail. To fix this edit the backup before restoring on a 8.x
 system.
 
diff --git a/doc/release_notes b/doc/release_notes
index 4d9d8932..0e9255d2 100644
--- a/doc/release_notes
+++ b/doc/release_notes
@@ -19,7 +19,7 @@ which it was derived, but the feature set is starting to diverge rapidly.
 will not work out of the box.
 * Any operating system that supports the above environment.
 
-2:  What's New in 1.1.0?
+2:  What's New in 1.1?
 
 2.1: Database changes:
 LedgerSMB 1.1 allows more flexibility in dataset creation. We now offer the