Fix various spelling mistakes

Mostly detected by Debian's Lintian tool.

Signed-off-by: Simon McVittie <smcv@debian.org>

7 files changed, 9 insertions, 9 deletions

diff --git a/doc/flatpak-build-finish.xml b/doc/flatpak-build-finish.xml
index 7581c47..73bf20f 100644
--- a/doc/flatpak-build-finish.xml
+++ b/doc/flatpak-build-finish.xml
@@ -228,7 +228,7 @@
                 <listitem><para>
                     If the application doesn't have access to the real homedir, make the (homedir-relative) path
                     FILENAME a bind mount to the corresponding path in the per-application directory,
-                    allowing that location to be used for persistant data.
+                    allowing that location to be used for persistent data.
                     This updates the [Context] group in the metadata.
                     This option can be used multiple times.
                 </para></listitem>
diff --git a/doc/flatpak-build-sign.xml b/doc/flatpak-build-sign.xml
index ad8da8f..068aa24 100644
--- a/doc/flatpak-build-sign.xml
+++ b/doc/flatpak-build-sign.xml
@@ -42,7 +42,7 @@
         <title>Description</title>
 
         <para>
-            Signs the commit for a speficied application or runtime in
+            Signs the commit for a specified application or runtime in
             a local repository.  <arg choice="plain">LOCATION</arg> is
             the location of the repository. <arg
             choice="plain">ID</arg> is the name of the application, or
@@ -52,7 +52,7 @@
         </para>
         <para>
             Applications can also be signed during build-export, but
-            it is sometimes useful to add additionaly signatures later.
+            it is sometimes useful to add additional signatures later.
         </para>
     </refsect1>
 
diff --git a/doc/flatpak-build.xml b/doc/flatpak-build.xml
index e6abfce..af16ddd 100644
--- a/doc/flatpak-build.xml
+++ b/doc/flatpak-build.xml
@@ -45,7 +45,7 @@
             must have been initialized with <command>flatpak build-init</command>.
         </para>
         <para>
-            The sdk that is specfied in the <filename>metadata</filename> file
+            The sdk that is specified in the <filename>metadata</filename> file
             in the directory is mounted at <filename>/usr</filename> and the
             <filename>files</filename> and <filename>var</filename> subdirectories
             are mounted at <filename>/app</filename> and <filename>/var</filename>,
@@ -209,7 +209,7 @@
                 <listitem><para>
                     If the application doesn't have access to the real homedir, make the (homedir-relative) path
                     FILENAME a bind mount to the corresponding path in the per-application directory,
-                    allowing that location to be used for persistant data.
+                    allowing that location to be used for persistent data.
                     This overrides to the Context section from the application metadata.
                     This option can be used multiple times.
                 </para></listitem>
diff --git a/doc/flatpak-builder.xml b/doc/flatpak-builder.xml
index 4572295..eb2858a 100644
--- a/doc/flatpak-builder.xml
+++ b/doc/flatpak-builder.xml
@@ -310,7 +310,7 @@
                 </varlistentry>
                 <varlistentry>
                     <term><option>no-autogen</option> (boolean)</term>
-                    <listitem><para>Ignore the existance of an autogen script</para></listitem>
+                    <listitem><para>Ignore the existence of an autogen script</para></listitem>
                 </varlistentry>
                 <varlistentry>
                     <term><option>no-parallel-make</option> (boolean)</term>
diff --git a/doc/flatpak-install.xml b/doc/flatpak-install.xml
index bf8ae01..4a5fc30 100644
--- a/doc/flatpak-install.xml
+++ b/doc/flatpak-install.xml
@@ -58,7 +58,7 @@
             the specified <arg choice="plain">REMOTE</arg>, but you can limit this by using the --app or --runtime option.
         </para>
         <para>
-            Note that flatpak allows to have multiple branches of an application and runtimes
+            Note that flatpak allows one to have multiple branches of an application and runtimes
             installed and used at the same time. However, only version of an application one can be current,
             meaning its exported files (for instance desktop files and icons) are
             visible to the host. The last installed version is made current by
diff --git a/doc/flatpak-override.xml b/doc/flatpak-override.xml
index 50422c4..7cea599 100644
--- a/doc/flatpak-override.xml
+++ b/doc/flatpak-override.xml
@@ -183,7 +183,7 @@
                 <listitem><para>
                     If the application doesn't have access to the real homedir, make the (homedir-relative) path
                     FILENAME a bind mount to the corresponding path in the per-application directory,
-                    allowing that location to be used for persistant data.
+                    allowing that location to be used for persistent data.
                     This overrides to the Context section from the application metadata.
                     This option can be used multiple times.
                 </para></listitem>
diff --git a/doc/flatpak-run.xml b/doc/flatpak-run.xml
index 9f99c25..3a26b0d 100644
--- a/doc/flatpak-run.xml
+++ b/doc/flatpak-run.xml
@@ -285,7 +285,7 @@
                 <listitem><para>
                     If the application doesn't have access to the real homedir, make the (homedir-relative) path
                     FILENAME a bind mount to the corresponding path in the per-application directory,
-                    allowing that location to be used for persistant data.
+                    allowing that location to be used for persistent data.
                     This overrides to the Context section from the application metadata.
                     This option can be used multiple times.
                 </para></listitem>