fix typos in various xml files

11 files changed, 23 insertions, 23 deletions

diff --git a/autostart/autostart-spec.xml b/autostart/autostart-spec.xml
index 745e72a..615a1be 100644
--- a/autostart/autostart-spec.xml
+++ b/autostart/autostart-spec.xml
@@ -179,7 +179,7 @@
         <para>
           If an application autostarts by having a .desktop file installed
           in the system wide autostart directory, an individual user can
-          disable the autotomatic start of this application by placing a
+          disable the automatic start of this application by placing a
           .desktop file of the same name in its personal autostart directory
           which contains the key Hidden=true.
         </para>
@@ -198,7 +198,7 @@
       <title>Autostart Files</title>
       <para>
         When a new medium is mounted the root directory of the medium should
-        be checked for the following Autostart files in order of precendence: 
+        be checked for the following Autostart files in order of precedence:
         .autorun, autorun, autorun.sh
         Only the first file that is present should be considered.
       </para>
diff --git a/basedir/basedir-spec.xml b/basedir/basedir-spec.xml
index fb3d7db..0b472a8 100644
--- a/basedir/basedir-spec.xml
+++ b/basedir/basedir-spec.xml
@@ -168,18 +168,18 @@
     </para>
     <para>
       Since <literal>$HOME</literal> might be shared between systems
-      of different achitectures, installing compiled binaries to
+      of different architectures, installing compiled binaries to
       <literal>$HOME</literal>/.local/bin could cause
       problems when used on systems of differing architectures. This
       is often not a problem, but the fact that
-      <literal>$HOME</literal> becomes partially achitecture-specific
+      <literal>$HOME</literal> becomes partially architecture-specific
       if compiled binaries are placed in it should be kept in mind.
     </para>
     <para>
       <literal>$XDG_DATA_DIRS</literal> defines the preference-ordered set of
       base directories to search for data files in addition to the
       <literal>$XDG_DATA_HOME</literal> base directory.
-      The directories in <literal>$XDG_DATA_DIRS</literal> should be seperated
+      The directories in <literal>$XDG_DATA_DIRS</literal> should be separated
       with a colon ':'.
     </para>
     <para>
@@ -190,7 +190,7 @@
       <literal>$XDG_CONFIG_DIRS</literal> defines the preference-ordered set of
       base directories to search for configuration files in addition to the
       <literal>$XDG_CONFIG_HOME</literal> base directory.
-      The directories in <literal>$XDG_CONFIG_DIRS</literal> should be seperated
+      The directories in <literal>$XDG_CONFIG_DIRS</literal> should be separated
       with a colon ':'.
     </para>
     <para>
diff --git a/help-system/help-system-spec.xml b/help-system/help-system-spec.xml
index 22ef1f6..4ddcf42 100644
--- a/help-system/help-system-spec.xml
+++ b/help-system/help-system-spec.xml
@@ -162,7 +162,7 @@
       The page identifier specifies which chunk to display. Not all applications
       will split a DocBook document into chunks in the same way, so the page
       identifier may not map exactly to the <sgmltag>id</sgmltag> attribute
-      of an element that is chunked. In this case, the applicaiton displays
+      of an element that is chunked. In this case, the application displays
       the nearest enclosing chunk and treats the page identifier as an anchor
       if no anchor was explicitly provided.</para>
     </section>
diff --git a/idle-inhibit/specification.xml b/idle-inhibit/specification.xml
index 0e70b23..731a71b 100644
--- a/idle-inhibit/specification.xml
+++ b/idle-inhibit/specification.xml
@@ -86,7 +86,7 @@
 
 			<para>The D-Bus service name, org.freedesktop.ScreenSaver, intentionally contains
 			the word screensaver, as KDE implements the idle inhibition API in a screensaver
-			sub-module. It was necessary for the specificed Idle Inhibition Service API to be
+			sub-module. It was necessary for the specified Idle Inhibition Service API to be
 			compatible with this existing software.</para>
 
 			<para>KDE's implementation until kde-workspace 4.11.8 lived on the
diff --git a/menu/menu-spec.xml b/menu/menu-spec.xml
index 918ba74..d3931ca 100644
--- a/menu/menu-spec.xml
+++ b/menu/menu-spec.xml
@@ -1343,7 +1343,7 @@
         <listitem>
           <para>
 	    The <link linkend="reserved-category-registry">list of
-	    Reserved Categories</link> containes categories that have a
+	    Reserved Categories</link> contains categories that have a
 	    desktop-specific meaning.
           </para>
         </listitem>
@@ -1912,7 +1912,7 @@
 
 	      </row><row>
 		<entry>Maps</entry>
-		<entry>Sofware for viewing maps, navigation, mapping, GPS</entry>
+		<entry>Software for viewing maps, navigation, mapping, GPS</entry>
 		<entry>Education or Science or Utility</entry>
 
 	      </row><row>
@@ -2311,7 +2311,7 @@
           </programlisting>
         </informalexample>
         And finally, a .menu file needs to be provided that links it all
-        togther:
+        together:
         <informalexample>
           <programlisting>
           <replaceable>sysconfdir</replaceable>/menus/application-merged/shinythings-webmirror.menu:
diff --git a/notification/notification-spec.xml b/notification/notification-spec.xml
index 37a7552..9131a20 100644
--- a/notification/notification-spec.xml
+++ b/notification/notification-spec.xml
@@ -162,7 +162,7 @@
         displayed to the user.
        </para>
        <para>
-        The default action (usually invoked my clicking the notification)
+        The default action (usually invoked by clicking the notification)
         should have a key named <literal>"default"</literal>. The name can
         be anything, though implementations are free not to display it.
        </para>
diff --git a/recent-files/recent-file-spec.xml b/recent-files/recent-file-spec.xml
index 8affa47..176a071 100644
--- a/recent-files/recent-file-spec.xml
+++ b/recent-files/recent-file-spec.xml
@@ -83,7 +83,7 @@
      The URI, Mime-Type, Timestamp tags are required, but the
      Private, Groups, and Group tags are not.  The Timestamp tag should be
      the number of
-     seconds sinced the Epoch when the item was added to the list.
+     seconds since the Epoch when the item was added to the list.
      The Group tags exist for the purpose of
      making groups of items with an arbitrary set of MIME types.  A single item
      can belong to an unlimited number of groups.  If the Private tag is
diff --git a/secret-service/org.freedesktop.Secrets.xml b/secret-service/org.freedesktop.Secrets.xml
index b6fba64..2dfa3ea 100644
--- a/secret-service/org.freedesktop.Secrets.xml
+++ b/secret-service/org.freedesktop.Secrets.xml
@@ -202,7 +202,7 @@ properties = { "org.freedesktop.Secret.Collection.Label": "MyCollection" }
                     <tp:docstring>An alias, such as 'default'.</tp:docstring>
                 </arg>
                 <arg name="collection" type='o' direction='out'>
-                    <tp:docstring>The collection or the the path '/' if no such collection exists.</tp:docstring>
+                    <tp:docstring>The collection or the path '/' if no such collection exists.</tp:docstring>
                 </arg>
             </method>
 
diff --git a/secret-service/specification.xml b/secret-service/specification.xml
index 28d9c4c..d69c9b2 100644
--- a/secret-service/specification.xml
+++ b/secret-service/specification.xml
@@ -264,7 +264,7 @@
 
 			<para>Many client applications may choose not to make use of the provisions to
 			encrypt secrets in transit. In fact for applications unable to prevent their own
-			memory from being paged to disk (eg: Java, C# or Python apps), transfering
+			memory from being paged to disk (eg: Java, C# or Python apps), transferring
 			encrypted secrets would be an excersize of questionable value.</para>
 
 			<section>
@@ -299,7 +299,7 @@
 				<para>When <function>OpenSession()</function> completes, it returns the session object
 				path along with a valid session object path.</para>
 
-				<para>Once an session algorithm has been negotiated, it is used for all transfer a
+				<para>Once a session algorithm has been negotiated, it is used for all transfer of
 				secrets whenever that session is specified along with the
 				<link linkend='type-Secret'><classname>secret</classname></link>.</para>
 			</section>
@@ -384,7 +384,7 @@
 
 			<para>A service may choose to unlock items or collections just for a single client
 			application. Alternatively the service may choose to allow any client application to access
-			items or collections unlocked by a another client application.</para>
+			items or collections unlocked by another client application.</para>
 
 			<para>A client application should always be ready to unlock the items for the secrets
 			it needs, or objects it must modify. It must not assume that an item is already unlocked
@@ -440,7 +440,7 @@
 			argument to display the prompt attached to their application window.</para>
 
 			<para>Once the user provides the additional required information to the prompt, the service
-			completes the operation that required the prompt. Then it emits the the
+			completes the operation that required the prompt. Then it emits the
 			<link linkend='org.freedesktop.Secret.Prompt.Completed'><function>Completed</function></link>
 			signal of the prompt object. The <parameter class='function'>result</parameter> argument of
 			the signal contains operation an operation specific result.</para>
diff --git a/xembed/spec/xembed-spec.xml b/xembed/spec/xembed-spec.xml
index 5f134a4..2d139e9 100644
--- a/xembed/spec/xembed-spec.xml
+++ b/xembed/spec/xembed-spec.xml
@@ -232,7 +232,7 @@
 	window which has the X input focus (set with
 	XSetInputFocus()). However, if the mouse pointer is inside
 	that focus window, the event is sent to the subwindow of the
-	focus window that is under the moues pointer. In modern toolkits,
+	focus window that is under the mouse pointer. In modern toolkits,
 	the X input focus is typically left on the toplevel window and
 	a separate logical input focus is implemented within the
 	toolkit. The toolkit ignores the window that the key event is
@@ -1220,7 +1220,7 @@ void send_xembed_message(
       <para>
 	Toolkits such as Qt and GTK+ have a concept of disabled
 	widgets. This notion is typically hierarchical, so if 
-	the embedder or a ancestry of the embedder becomes
+	the embedder or an ancestor of the embedder becomes
 	insensitive, widgets inside the client should be displayed as,
 	and act insensitive as well.
       </para>
diff --git a/xsettings/xsettings.xml b/xsettings/xsettings.xml
index 7608581..9098f37 100644
--- a/xsettings/xsettings.xml
+++ b/xsettings/xsettings.xml
@@ -62,7 +62,7 @@
 	<para>
 	  The Xrm database merges information from various sources - the
 	  ~/.Xdefaults file on the root window, and a property on the root
-	  window. This means that to programatically configure the Xrm
+	  window. This means that to programmatically configure the Xrm
 	  database in response to a GUI config tool is difficult and
 	  unreliable.
 	</para>
@@ -229,7 +229,7 @@ be set to 65535.
     </programlisting>
     <para>
       With the additional restrictions that '/' cannot appear in
-      the leading or trailing position, that two occurences of
+      the leading or trailing position, that two occurrences of
       '/' cannot be consecutive, and that the first character
       of the name, and and the first character after a slash
       cannot be one of '0'-'9'. Names may not be empty.
@@ -327,7 +327,7 @@ be set to 65535.
 	Having a process always present as the owner of the _XSETTING
 	selection ensures that there are no race conditions and is
 	simpler than trying to create a locking mechanism that can
-	work without a persistant process. It is also expected that to
+	work without a persistent process. It is also expected that to
 	properly handle notification of changes to the stored
 	properties most desktops will want a process running to watch
 	for changes in any case. In cases of tight resource usage, the