CONTRIBUTING.rst

@@ -120,7 +120,7 @@ preferred in separate commits.
 
 If a commit in your branch modifies behavior such that a test must also
 be changed to match the new behavior, then the tests should be updated
-with the same commit, so that every commit passes it's own tests.
+with the same commit, so that every commit passes its own tests.
 
 
 Commit messages
@@ -733,7 +733,7 @@ is **illegal** to override any other method.
 * Subclasses are not allowed to override any other methods.
 
 The key here is that in BuildStream, we consider it unacceptable
-that a subclass overrides a method of it's parent class unless
+that a subclass overrides a method of its parent class unless
 the said parent class has explicitly given permission to subclasses
 to do so, and outlined the API contract for this purpose. No surprises
 are allowed.
@@ -937,7 +937,7 @@ possible, and avoid any cyclic relationships in modules.
 
 For instance, the ``Source`` objects are owned by ``Element``
 objects in the BuildStream data model, and as such the ``Element``
-will delegate some activities to the ``Source`` objects in it's
+will delegate some activities to the ``Source`` objects in its
 possesion. The ``Source`` objects should however never call functions
 on the ``Element`` object, nor should the ``Source`` object itself
 have any understanding of what an ``Element`` is.
@@ -1180,7 +1180,7 @@ The BuildStream documentation style is as follows:
     Feel free to also use ``.. attention::`` or ``.. important::`` to call special
     attention to a paragraph, ``.. tip::`` to give the reader a special tip on how
     to use an advanced feature or ``.. warning::`` to warn the user about a potential
-    misuse of the API and explain it's consequences.
+    misuse of the API and explain its consequences.
 
 * Code blocks are defined using: ``.. code:: LANGUAGE`` blocks, followed by an empty
   line and then indented (3 spaces) text. Note that the default language is ``python``.

README.rst

 About
 -----
 
-.. image:: https://buildstream.gitlab.io/buildstream/_static/release.svg
+.. image:: https://docs.buildstream.build/_static/release.svg
    :target: https://gitlab.com/BuildStream/buildstream/commits/bst-1.2
 
-.. image:: https://buildstream.gitlab.io/buildstream/_static/snapshot.svg
+.. image:: https://docs.buildstream.build/_static/snapshot.svg
    :target: https://gitlab.com/BuildStream/buildstream/commits/master
 
 .. image:: https://gitlab.com/BuildStream/buildstream/badges/master/pipeline.svg
@@ -63,7 +63,7 @@ BuildStream offers the following advantages:
 
 How do I use BuildStream?
 =========================
-Please refer to the `documentation <https://buildstream.gitlab.io/buildstream/>`_
+Please refer to the `documentation <https://docs.buildstream.build>`_
 for  information about installing BuildStream, and about the BuildStream YAML format
 and plugin options.
 
@@ -86,9 +86,9 @@ BuildStream operates on a set of YAML files (.bst files), as follows:
 How can I get started?
 ======================
 To get started, first `install BuildStream by following the installation guide
-<https://buildstream.gitlab.io/buildstream/main_install.html>`_
+<https://buildstream.build/install.html>`_
 and then follow our tutorial in the
-`user guide <https://buildstream.gitlab.io/buildstream/main_using.html>`_.
+`user guide <https://docs.buildstream.build/main_using.html>`_.
 
 We also recommend exploring some existing BuildStream projects:
 

buildstream/_frontend/cli.py

@@ -104,7 +104,7 @@ def complete_target(args, incomplete):
     # The project is not required to have an element-path
     element_directory = project.get('element-path')
 
-    # If a project was loaded, use it's element-path to
+    # If a project was loaded, use its element-path to
     # adjust our completion's base directory
     if element_directory:
         base_directory = os.path.join(base_directory, element_directory)

buildstream/_fuse/mount.py

@@ -60,7 +60,7 @@ class FuseMountError(Exception):
 #
 #   With the daemon approach, we know that the fuse is mounted right
 #   away when fuse_main() returns, then the daemon will go and handle
-#   requests on it's own, but then we have no way to shut down the
+#   requests on its own, but then we have no way to shut down the
 #   daemon.
 #
 #   With the blocking approach, we still have it as a child process
@@ -105,7 +105,7 @@ class Mount():
         self.__process = Process(target=self.__run_fuse)
 
         # Ensure the child fork() does not inherit our signal handlers, if the
-        # child wants to handle a signal then it will first set it's own
+        # child wants to handle a signal then it will first set its own
         # handler, and then unblock it.
         with _signals.blocked([signal.SIGTERM, signal.SIGTSTP, signal.SIGINT], ignore=False):
             self.__process.start()
@@ -185,7 +185,7 @@ class Mount():
         self.__operations = self.create_operations()
 
         # Run fuse in foreground in this child process, internally libfuse
-        # will handle SIGTERM and gracefully exit it's own little main loop.
+        # will handle SIGTERM and gracefully exit its own little main loop.
         #
         FUSE(self.__operations, self.__mountpoint, nothreads=True, foreground=True, nonempty=True,
              **self._fuse_mount_options)

buildstream/element.py

@@ -867,8 +867,8 @@ class Element(Plugin):
 
     # _new_from_meta():
     #
-    # Recursively instantiate a new Element instance, it's sources
-    # and it's dependencies from a meta element.
+    # Recursively instantiate a new Element instance, its sources
+    # and its dependencies from a meta element.
     #
     # Args:
     #    artifacts (ArtifactCache): The artifact cache
@@ -1217,7 +1217,7 @@ class Element(Plugin):
     # _preflight():
     #
     # A wrapper for calling the abstract preflight() method on
-    # the element and it's sources.
+    # the element and its sources.
     #
     def _preflight(self):
 
@@ -1999,7 +1999,7 @@ class Element(Plugin):
         if workspace:
 
             # A workspace is considered inconsistent in the case
-            # that it's directory went missing
+            # that its directory went missing
             #
             fullpath = workspace.get_absolute_path()
             if not os.path.exists(fullpath):

buildstream/plugin.py

@@ -169,7 +169,7 @@ class Plugin():
 
         For elements, this is the project relative bst filename,
         for sources this is the owning element's name with a suffix
-        indicating it's index on the owning element.
+        indicating its index on the owning element.
 
         For sources this is for display purposes only.
         """
@@ -208,8 +208,8 @@ class Plugin():
            node (dict): The loaded configuration dictionary
 
         Raises:
-           :class:`.SourceError`: If its a :class:`.Source` implementation
-           :class:`.ElementError`: If its an :class:`.Element` implementation
+           :class:`.SourceError`: If it's a :class:`.Source` implementation
+           :class:`.ElementError`: If it's an :class:`.Element` implementation
 
         Plugin implementors should implement this method to read configuration
         data and store it.
@@ -238,8 +238,8 @@ class Plugin():
         """Preflight Check
 
         Raises:
-           :class:`.SourceError`: If its a :class:`.Source` implementation
-           :class:`.ElementError`: If its an :class:`.Element` implementation
+           :class:`.SourceError`: If it's a :class:`.Source` implementation
+           :class:`.ElementError`: If it's an :class:`.Element` implementation
 
         This method is run after :func:`Plugin.configure() <buildstream.plugin.Plugin.configure>`
         and after the pipeline is fully constructed.

buildstream/plugins/elements/compose.py

@@ -41,7 +41,7 @@ from buildstream import Element, Scope
 class ComposeElement(Element):
     # pylint: disable=attribute-defined-outside-init
 
-    # The compose element's output is it's dependencies, so
+    # The compose element's output is its dependencies, so
     # we must rebuild if the dependencies change even when
     # not in strict build plans.
     #

buildstream/plugins/elements/filter.py

@@ -47,7 +47,7 @@ from buildstream import Element, ElementError, Scope
 class FilterElement(Element):
     # pylint: disable=attribute-defined-outside-init
 
-    # The filter element's output is it's dependencies, so
+    # The filter element's output is its dependencies, so
     # we must rebuild if the dependencies change even when
     # not in strict build plans.
     BST_STRICT_REBUILD = True

buildstream/plugins/sources/deb.py

@@ -44,7 +44,7 @@ deb - stage files from .deb packages
    # Specify the ref. It's a sha256sum of the file you download.
    ref: 6c9f6f68a131ec6381da82f2bff978083ed7f4f7991d931bfa767b7965ebc94b
 
-   # Specify the basedir to return only the specified dir and it's children
+   # Specify the basedir to return only the specified dir and its children
    base-dir: ''
 
 """

buildstream/plugins/sources/local.py

@@ -133,7 +133,7 @@ def unique_key(filename):
     if os.path.isdir(filename):
         return "0"
     elif os.path.islink(filename):
-        # For a symbolic link, use the link target as it's unique identifier
+        # For a symbolic link, use the link target as its unique identifier
         return os.readlink(filename)
 
     return utils.sha256sum(filename)

buildstream/plugins/sources/ostree.py

@@ -105,7 +105,7 @@ class OSTreeSource(Source):
         node['ref'] = self.ref = ref
 
     def track(self):
-        # If self.tracking is not specified its' not an error, just silently return
+        # If self.tracking is not specified it's not an error, just silently return
         if not self.tracking:
             return None
 
@@ -151,7 +151,7 @@ class OSTreeSource(Source):
             # The target directory is guaranteed to exist, here we must move the
             # content of out checkout into the existing target directory.
             #
-            # We may not be able to create the target directory as it's parent
+            # We may not be able to create the target directory as its parent
             # may be readonly, and the directory itself is often a mount point.
             #
             try:

buildstream/sandbox/_mount.py

@@ -41,7 +41,7 @@ class Mount():
         self.safe_hardlinks = safe_hardlinks
         self._fuse_mount_options = fuse_mount_options
 
-        # FIXME: When the criteria for mounting something and it's parent
+        # FIXME: When the criteria for mounting something and its parent
         #        mount is identical, then there is no need to mount an additional
         #        fuse layer (i.e. if the root is read-write and there is a directory
         #        marked for staged artifacts directly within the rootfs, they can

buildstream/scriptelement.py

@@ -45,7 +45,7 @@ class ScriptElement(Element):
     __commands = None
     __layout = []
 
-    # The compose element's output is it's dependencies, so
+    # The compose element's output is its dependencies, so
     # we must rebuild if the dependencies change even when
     # not in strict build plans.
     #
@@ -135,7 +135,7 @@ class ScriptElement(Element):
            be made available at the specified location.
         """
         #
-        # Even if this is an empty list by default, make sure that it's
+        # Even if this is an empty list by default, make sure that its
         # instance data instead of appending stuff directly onto class data.
         #
         if not self.__layout:

buildstream/utils.py

@@ -993,7 +993,7 @@ def _tempdir(suffix="", prefix="tmp", dir=None):  # pylint: disable=redefined-bu
 
 # _kill_process_tree()
 #
-# Brutally murder a process and all of it's children
+# Brutally murder a process and all of its children
 #
 # Args:
 #    pid (int): Process ID

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']

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
 

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...
 

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
 

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`

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.