Fix spelling of it's and its

10 files changed, 13 insertions, 13 deletions

diff --git a/doc/bst2html.py b/doc/bst2html.py
index d90eba43f..af35efe24 100755
--- a/doc/bst2html.py
+++ b/doc/bst2html.py
@@ -445,7 +445,7 @@ def run_bst(directory, force, source_cache, description, palette):
     """Run a bst command and capture stdout/stderr in html
 
     This command normally takes a description yaml file, see the CONTRIBUTING
-    file for information on it's format.
+    file for information on its format.
     """
     if not source_cache and os.environ.get('BST_SOURCE_CACHE'):
         source_cache = os.environ['BST_SOURCE_CACHE']
diff --git a/doc/examples/autotools/elements/hello.bst b/doc/examples/autotools/elements/hello.bst
index 510f5b975..ce3ea7466 100644
--- a/doc/examples/autotools/elements/hello.bst
+++ b/doc/examples/autotools/elements/hello.bst
@@ -8,7 +8,7 @@ variables:
   # The hello world example lives in the doc/amhello folder.
   #
   # Set the %{command-subdir} variable to that location
-  # and just have the autotools element run it's commands there.
+  # and just have the autotools element run its commands there.
   #
   command-subdir: doc/amhello
 
diff --git a/doc/examples/flatpak-autotools/files/src/aclocal.m4 b/doc/examples/flatpak-autotools/files/src/aclocal.m4
index f3018f6c8..b0616b92c 100644
--- a/doc/examples/flatpak-autotools/files/src/aclocal.m4
+++ b/doc/examples/flatpak-autotools/files/src/aclocal.m4
@@ -150,7 +150,7 @@ fi])])
 
 # There are a few dirty hacks below to avoid letting 'AC_PROG_CC' be
 # written in clear, in which case automake, when reading aclocal.m4,
-# will think it sees a *use*, and therefore will trigger all it's
+# will think it sees a *use*, and therefore will trigger all its
 # C support machinery.  Also note that it means that autoscan, seeing
 # CC etc. in the Makefile, will ask for an AC_PROG_CC use...
 
diff --git a/doc/examples/junctions/autotools/elements/hello.bst b/doc/examples/junctions/autotools/elements/hello.bst
index 510f5b975..ce3ea7466 100644
--- a/doc/examples/junctions/autotools/elements/hello.bst
+++ b/doc/examples/junctions/autotools/elements/hello.bst
@@ -8,7 +8,7 @@ variables:
   # The hello world example lives in the doc/amhello folder.
   #
   # Set the %{command-subdir} variable to that location
-  # and just have the autotools element run it's commands there.
+  # and just have the autotools element run its commands there.
   #
   command-subdir: doc/amhello
 
diff --git a/doc/source/advanced-features/junction-elements.rst b/doc/source/advanced-features/junction-elements.rst
index d2d223b88..b6065d344 100644
--- a/doc/source/advanced-features/junction-elements.rst
+++ b/doc/source/advanced-features/junction-elements.rst
@@ -43,7 +43,7 @@ Building callHello.bst,
 .. raw:: html
    :file: ../sessions/junctions-build.html
 
-You can see that the hello.bst element and it's dependencies from the autotools
+You can see that the hello.bst element and its dependencies from the autotools
 project have been build as part of the pipeline for callHello.bst.
 
 We can now invoke `bst shell`
diff --git a/doc/source/format_project.rst b/doc/source/format_project.rst
index 31984145b..469f99747 100644
--- a/doc/source/format_project.rst
+++ b/doc/source/format_project.rst
@@ -57,7 +57,7 @@ the ``format-version`` field, e.g.:
   # The minimum base BuildStream format
   format-version: 0
 
-BuildStream will increment it's core YAML format version at least once
+BuildStream will increment its core YAML format version at least once
 in any given minor point release where the format has been extended
 to support a new feature.
 
diff --git a/doc/source/tutorial/autotools.rst b/doc/source/tutorial/autotools.rst
index 8d24ca59c..ea2835838 100644
--- a/doc/source/tutorial/autotools.rst
+++ b/doc/source/tutorial/autotools.rst
@@ -88,7 +88,7 @@ As :ref:`the documentation <format_composition>` mentions:
 The variable we needed to override was ``command-subdir``, which is an
 automatic variable provided by the :mod:`BuildElement <buildstream.buildelement>`
 abstract class. This variable simply instructs the :mod:`BuildElement <buildstream.buildelement>`
-in which subdirectory of the ``%{build-root}`` to run it's commands in.
+in which subdirectory of the ``%{build-root}`` to run its commands in.
 
 One can always display the resolved set of variables for a given
 element's configuration using :ref:`bst show <invoking_show>`:
diff --git a/doc/source/tutorial/first-project.rst b/doc/source/tutorial/first-project.rst
index 1791b198b..18df85bb7 100644
--- a/doc/source/tutorial/first-project.rst
+++ b/doc/source/tutorial/first-project.rst
@@ -73,7 +73,7 @@ The element
 ~~~~~~~~~~~
 The :mod:`import <elements.import>` element can be used to simply add content
 directly to the output artifacts. In this case, it simply takes the ``hello.world`` file
-provided by it's source and stages it directly to the artifact output root.
+provided by its source and stages it directly to the artifact output root.
 
 .. tip::
 
diff --git a/doc/source/tutorial/integration-commands.rst b/doc/source/tutorial/integration-commands.rst
index 8d80eb9a2..ead5be8b2 100644
--- a/doc/source/tutorial/integration-commands.rst
+++ b/doc/source/tutorial/integration-commands.rst
@@ -7,11 +7,11 @@ performed at installation time, otherwise it will not run properly.
 
 This is especially true in cases where a daemon or library interoperates
 with third party extensions and needs to maintain a system wide cache whenever
-it's extensions are installed or removed; system wide font caches are an example
+its extensions are installed or removed; system wide font caches are an example
 of this.
 
 In these cases we use :ref:`integration commands <public_integration>` to
-ensure that a runtime is ready to run after all of it's components have been *staged*.
+ensure that a runtime is ready to run after all of its components have been *staged*.
 
 .. note::
 
@@ -60,10 +60,10 @@ we've used any :ref:`builtin public data <public_builtin>`.
 
 Public data is a free form portion of an element's configuration and
 is not necessarily understood by the element on which it is declared, public
-data is intended to be read by it's reverse dependency elements.
+data is intended to be read by its reverse dependency elements.
 
 This allows annotations on some elements to inform elements later in
-the dependency chain about details of it's artifact, or to suggest how
+the dependency chain about details of its artifact, or to suggest how
 it should be processed.
 
 
diff --git a/doc/source/using_configuring_artifact_server.rst b/doc/source/using_configuring_artifact_server.rst
index 2c4e761ba..b25b5aecf 100644
--- a/doc/source/using_configuring_artifact_server.rst
+++ b/doc/source/using_configuring_artifact_server.rst
@@ -79,7 +79,7 @@ in a system wide location, with ``pip3 install .`` in the BuildStream
 checkout directory.
 
 Otherwise, some tinkering is required to ensure BuildStream is available
-in ``PATH`` when it's companion ``bst-artifact-server`` program is run
+in ``PATH`` when its companion ``bst-artifact-server`` program is run
 remotely.
 
 You can install only the artifact server companion program without