Fix grammar issues

xml/obs_ag_build_targets.xml

@@ -24,7 +24,7 @@
    this and select the public side you want.</para>
   <para>If you want to connect to a not listed instance, you can simple
    create a remote project using the <emphasis>osc meta prj</emphasis> command.
-   A remote project differs from a local project the it has a <emphasis
+   A remote project differs from a local project as it has a <emphasis
     role="strong">remoteurl</emphasis> tag (see <xref
     linkend="_project_meta_data"/>).</para>
   <para>Example:</para>

xml/obs_ag_publish_hooks.xml

@@ -8,7 +8,7 @@
  xmlns:xlink="http://www.w3.org/1999/xlink" version="5.1"
  xml:id="_publisher_hooks">
  <title>Publisher Hooks</title>
- <para>The job of the publisher service is to publish the build packages
+ <para>The job of the publisher service is to publish the built packages
   and/or images by creating repositories that are made available through a web
   server.</para>
  <para>It can be configured to use custom scripts to copy the build results

xml/obs_ag_source_service.xml

@@ -154,7 +154,7 @@
  </sect2>
  <sect2>
   <title>Dropping a Source Service Again</title>
-  <para> Sometimes it is useful to continue work on generated files
+  <para> Sometimes it is useful to continue working on generated files
    manually. In this situation the _service file needs to be dropped, but all
    generated files need to be committed as standard files. The OBS provides the
    "mergeservice" command for this. It can also be used via osc by calling

xml/obs_ag_unpublish_hooks.xml

@@ -8,7 +8,7 @@
  xmlns:xlink="http://www.w3.org/1999/xlink" version="5.1"
  xml:id="_unpublisher_hooks">
  <title>Unpublisher Hooks</title>
- <para>The job of the publisher service is to publish the build packages
+ <para>The job of the publisher service is to publish the built packages
   and/or images by creating repositories that are made available through a web
   server.</para>
  <para>The OBS Publisher can be configured to use custom scripts to be

xml/obs_ag_user_management.xml

@@ -17,7 +17,7 @@
  <sect2 xml:id="_user_and_group_roles">
   <title>User and Group Roles</title>
   <para>The OBS role model has one global role: Admin, which can be granted
-   to users. Am OBS admin has access to all projects and packages via the API
+   to users. An OBS admin has access to all projects and packages via the API
    interface and the web user interface. Some menus in the Web UI do not allow
    changes by an Admin (for example, the Repository menu) as long the Admin is not a
    Maintainer for the project as well. But the same change can be done via

xml/obs_source_service.xml

@@ -410,7 +410,7 @@
 
  <sect1 xml:id="sec.obs.sserv.remove">
   <title>Removing a Source Service</title>
-  <para> Sometimes it is useful to continued to work on generated files
+  <para> Sometimes it is useful to continue working on generated files
    manually. In this situation the <filename>_service</filename> file needs
    to be dropped, but all
    generated files need to be committed as standard files. The &obsa;