Changeset 2c87187 for server/databases/upgradedb.xml

Timestamp:

02/16/2022 09:04:13 PM (2 years ago)

Author:

Bruce Dubbs <bdubbs@…>

Branches:

11.1, 11.2, 11.3, 12.0, 12.1, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal

Children:

453910f

Parents:

b21f9be

Message:

Spelling fixes

File:

• server/databases/upgradedb.xml (modified) (3 diffs)

server/databases/upgradedb.xml

@@ -82 +82 @@
 
     <para>
-      Unfortunatly, the most likly case is that the new server software
+      Unfortunately, the most likly case is that the new server software
       complains about out of date file formats and exits.  When this happens
       and you have overwritten the installed server software, you may not be
@@ -110 +110 @@
           to restore the data from this backup. When running a
           database server, you should not only create backups but you
-          should also verify that the process you designed to fullfill
+          should also verify that the process you designed to fulfill
           the restore task is working properly. When you encounter a
           problem with the restore when you urgently have to
@@ -268 +268 @@
       </para>
 
-      <para>Unfortunatly, there is no dedicated chapter in the
+      <para>Unfortunately, there is no dedicated chapter in the
       upstream documentation talking about backup/restore but
       there are several articles about it on the