chore: typo

close #880 #879

Author: duncdrum

src/main/xar-resources/data/backup/backup.xml

@@ -434,7 +434,7 @@
             <programlisting xlink:href="listings/listing-9.txt"/>
             <para>Default settings for the user, password or server URIs can also be set in the
                 <literal>backup.properties</literal> file.</para>
-            <para>If you want to connect to a databse using SSL, use the parameter <literal>--use-ssl</literal> or
+            <para>If you want to connect to a database using SSL, use the parameter <literal>--use-ssl</literal> or
                 (shorter) <literal>-S</literal>:</para>
             <programlisting xlink:href="listings/listing-12.txt"/>
             <para>NOTE: You still have to set the correct port (usually port 443), otherwise the client will attempt

src/main/xar-resources/data/devguide_indexes/devguide_indexes.xml

@@ -594,7 +594,7 @@
                 suggests if eXist doesn't own the admin rights. Conversely,
                 <literal>removeIndexContent()</literal> wiould probably have nothing to do if eXist
                 owns the admin rights since physically destroying the DB would probably be more
-                efficient than deleteing table contents.</para>
+                efficient than deleting table contents.</para>
             <para> <literal>checkIndex()</literal> will delegate the task to the
                 <literal>broker</literal>'s <literal>IndexWorker</literal>.</para>
             <para>The remaining methods are DB-dependant and thus abstract:</para>
@@ -648,7 +648,7 @@
                 remember that the database should be closed at that moment no file locking
                 issues.</para>
             <para> <literal>removeIndexContent()</literal> deletes the table that contains spatial
-                data. As explained above, this is less efficient than deleteing the whole databse
+                data. As explained above, this is less efficient than deleting the whole database
                 though!</para>
             <para>The two next methods are totally JDBC-specific and, given the way they are
                 implemented, are totally embedded HSQLDB-specific. The <emphasis>current</emphasis>