correct docs spelling errors

docs/source/content_generators.rst

@@ -12,7 +12,7 @@ provide stable APIs and interfaces to other processes.
 
 Along with the content to be managed by Koji, a Content Generator will
 provide enough metadata to enable a reasonable level of auditing and
-reproduceability. The exact data provided and the format used is being
+reproducibility. The exact data provided and the format used is being
 discussed, but will include information like the upstream source URL,
 build tools used, build environment contents, and any
 container/virtualization technologies used.

docs/source/defining_hub_policies.rst

@@ -247,7 +247,7 @@ Available tests
     * for use with the channel policy
 
 ``method``
-    * matches the task method name agaist glob pattern(s)
+    * matches the task method name against glob pattern(s)
     * true if the method name matches any of the patterns
     * for use with the channel policy
 

docs/source/external_repo_server_bootstrap.rst

@@ -83,7 +83,7 @@ Examples of urls to use for external Repositories
 all these examples use mirrors.kernel.org please find the closest mirror
 to yourself. Note that the Fedora minimal buildroots download ~100Mb
 then build dependencies on top. these are downloaded each build you can
-save alot of network bandwidth by using a local mirror or running
+save a lot of network bandwidth by using a local mirror or running
 through a caching proxy.
 
 NOTE: this uses $arch **NOT** $basearch

docs/source/migrating_to_1.10.rst

@@ -67,7 +67,7 @@ And there are three new commands
 Other Configuration changes
 ---------------------------
 
-The Koji web interface can now treate ``extra-footer.html`` as a Cheetah
+The Koji web interface can now treat ``extra-footer.html`` as a Cheetah
 template. This behavior can be enabled by setting the ``LiteralFooter`` option
 to ``False`` in the kojiweb config.
 

docs/source/migrating_to_1.12.rst

@@ -71,7 +71,7 @@ Changes to calls:
     * repo related calls (e.g. ``repoInfo`` now include a boolean ``dist``
       field
     * the ``editTag2`` call can now remove tag_extra data if the
-      ``remove_extra`` keywarg argument is used
+      ``remove_extra`` keyword argument is used
     * the listTaskOutput call supports a new ``all_volumes`` keyword argument.
       If true, the results are extended to deal with files in same relative paths
       on different volumes.

docs/source/migrating_to_1.14.rst

@@ -12,7 +12,7 @@ DB Updates
 
 The schema updates this time are minor
 
-   * dropping unused `log_messages` table
+   * dropping unused ``log_messages`` table
    * new standard entries in the archivetypes table
 
 As in previous releases, we provide a migration script that updates the

docs/source/release_notes_1.13.rst

@@ -61,7 +61,7 @@ similar to the web interface.
 
 .. code-block:: text
 
-    Usage: lkoji hostinfo [options] <hostname> [<hostname> ...]
+    Usage: koji hostinfo [options] <hostname> [<hostname> ...]
     (Specify the --help global option for a list of other help options)
 
     Options:
@@ -75,7 +75,7 @@ Enhancements to restart-hosts
 The `restart-hosts` command is used by admins to safely restart the build hosts
 after a configuration change.
 
-Because multiple restarts can confict, the command will now exit with a error
+Because multiple restarts can conflict, the command will now exit with a error
 if a restart is already underway (can be overridden with --force).
 
 There are now options to limit the restart to a given channel or arch.

docs/source/release_notes_1.14.rst

@@ -107,7 +107,7 @@ without having to resort to the ``call`` command.
 
 .. code-block:: text
 
-    Usage: lkoji block-group <tag> <group>
+    Usage: koji block-group <tag> <group>
     (Specify the --help global option for a list of other help options)
 
     Options:

docs/source/server_howto.rst

@@ -566,7 +566,7 @@ Set Database To Listen On All Addresses
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 The koji-hub service will attempt to connect to the database server in the
 manner you configure.  If you use the system hostname, then the database will
-need to be avalible on that address.  To configure this please perform the
+need to be available on that address.  To configure this please perform the
 following:
 
 #.  Edit /var/lib/pgsql/data/postgresql.conf
@@ -987,7 +987,7 @@ Add the host entry for the koji builder to the database
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 You will now need to add the koji builder to the database so that they can be
-utilized by kojij hub. Make sure you do this before you start kojid for the
+utilized by koji hub. Make sure you do this before you start kojid for the
 first time, or you'll need to manually remove entries from the sessions and
 users table before it can be run successfully.
 
@@ -1033,7 +1033,7 @@ the same as KojiDir)
     ; The directory root for temporary storage
     workdir=/tmp/koji
 
-The root of the koji build directory (ie, ``/mnt/koji``) must be mounted on the
+The root of the koji build directory (i.e., ``/mnt/koji``) must be mounted on the
 builder. A Read-Only NFS mount is the easiest way to handle this.
 
 ::

docs/source/using_the_koji_build_system.rst

@@ -66,7 +66,7 @@ by running ``fedora-cert -n`` again. You can check if it has expired
 with ``fedora-cert -v``.
 
 the following are downloaded automatically by fedora-packager-setup and
-dont need to be manually setup
+don't need to be manually setup
 
 ``~/.fedora-upload-ca.cert`` (The certificate for the Certificate
 Authority used to sign the user keys.) : It can be manually downloaded
@@ -258,7 +258,7 @@ the next group will begin building. For example:
 ``fedpkg chain-build libwidget libaselib : libgizmo :``
 
 will cause libwidget and libaselib to be built in parallel, followed by
-libgizmo and then the currect directory package. If no groups are
+libgizmo and then the correct directory package. If no groups are
 defined, packages will be built sequentially.
 
 If a build fail, following builds are cancelled but the builds that
@@ -406,7 +406,7 @@ any mock-config command to get a working mock-config from fedoras koji.
 
 .. _tuning-mock-per-tag:
 
-Tuning mock's behaviour per tag
+Tuning mock's behavior per tag
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 Few options for mock can be configured per-tag. These options are stored in
@@ -423,7 +423,7 @@ environment follows:
   package manager. Typically used with `yum` or `dnf` values.
 * `mock.new_chroot` - 0/1 value. If it is set, `--new-chroot` or
   `--old-chroot` option is appended to any mock call. If it is not set,
-  mock's default behaviour is used.
+  mock's default behavior is used.
 
 Using Koji to control tasks
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^

docs/source/writing_a_plugin.rst

@@ -218,7 +218,7 @@ the command.
 
 In the first case, the command will not automatically
 authenticate with the hub (though the user can still override
-this behaviour with `--force-auth` option). In the second case, the command
+this behavior with `--force-auth` option). In the second case, the command
 will perform authentication by default (this too can be overridden by the
 user with the `--noauth` option).