Update messages.pot as of version 0454c8e

Author: github-actions[bot]

locales/messages.pot

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Python Packaging User Guide \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2025-05-17 20:46+0000\n"
+"POT-Creation-Date: 2025-05-18 19:05+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <[email protected]>\n"
@@ -41,7 +41,7 @@ msgid "Writing new content"
 msgstr ""
 
 #: ../source/contribute.rst:14
-msgid "Translate the guide"
+msgid "Translating the guide"
 msgstr ""
 
 #: ../source/contribute.rst:16
@@ -1165,7 +1165,7 @@ msgid ":ref:`easy_install <easy_install>`, now `deprecated`_, was released in 20
 msgstr ""
 
 #: ../source/discussions/pip-vs-easy-install.rst:14
-msgid ":ref:`pip` came later in 2008, as alternative to :ref:`easy_install <easy_install>`, although still largely built on top of :ref:`setuptools` components.  It was notable at the time for *not* installing packages as :term:`Eggs <Egg>` or from :term:`Eggs <Egg>` (but rather simply as 'flat' packages from :term:`sdists <Source Distribution (or \"sdist\")>`), and introducing the idea of :ref:`Requirements Files <pip:Requirements Files>`, which gave users the power to easily replicate environments."
+msgid ":ref:`pip` came later in 2008, as an alternative to :ref:`easy_install <easy_install>`, although still largely built on top of :ref:`setuptools` components.  It was notable at the time for *not* installing packages as :term:`Eggs <Egg>` or from :term:`Eggs <Egg>` (but rather simply as 'flat' packages from :term:`sdists <Source Distribution (or \"sdist\")>`), and introducing the idea of :ref:`Requirements Files <pip:Requirements Files>`, which gave users the power to easily replicate environments."
 msgstr ""
 
 #: ../source/discussions/pip-vs-easy-install.rst:22
@@ -1818,7 +1818,7 @@ msgid "The decision which version number to choose is up to a project's maintain
 msgstr ""
 
 #: ../source/discussions/versioning.rst:74
-msgid "There are known exceptions for selecting the next version number. The maintainers may consciously choose to break the assumption that the last version segment only contains backwards-compatible changes. One such case is when security vulnerability needs to be addressed. Security releases often come in patch versions but contain breaking changes inevitably."
+msgid "There are known exceptions for selecting the next version number. The maintainers may consciously choose to break the assumption that the last version segment only contains backwards-compatible changes. One such case is when a security vulnerability needs to be addressed. Security releases often come in patch versions but contain breaking changes inevitably."
 msgstr ""
 
 #: ../source/discussions/versioning.rst:84
@@ -1863,7 +1863,7 @@ msgid "Calendar versioning"
 msgstr ""
 
 #: ../source/discussions/versioning.rst:126
-msgid "Semantic versioning is not a suitable choice for all projects, such as those with a regular time based release cadence and a deprecation process that provides warnings for a number of releases prior to removal of a feature."
+msgid "Semantic versioning is not a suitable choice for all projects, such as those with a regular time-based release cadence and a deprecation process that provides warnings for a number of releases prior to removal of a feature."
 msgstr ""
 
 #: ../source/discussions/versioning.rst:130
@@ -1887,7 +1887,7 @@ msgid "Serial versioning refers to the simplest possible versioning scheme, whic
 msgstr ""
 
 #: ../source/discussions/versioning.rst:150
-msgid "Combinations of the above schemes are possible. For example, a project may combine date based versioning with serial versioning to create a *year.serial* numbering scheme that readily conveys the approximate age of a release, but doesn't otherwise commit to a particular release cadence within the year."
+msgid "Combinations of the above schemes are possible. For example, a project may combine date-based versioning with serial versioning to create a *year.serial* numbering scheme that readily conveys the approximate age of a release, but doesn't otherwise commit to a particular release cadence within the year."
 msgstr ""
 
 #: ../source/discussions/versioning.rst:157
@@ -3057,7 +3057,7 @@ msgid "Creating and packaging command-line tools"
 msgstr ""
 
 #: ../source/guides/creating-command-line-tools.rst:7
-msgid "This guide will walk you through creating and packaging a standalone command-line application that can be installed with :ref:`pipx`, a tool creating and managing :term:`Python Virtual Environments <Virtual Environment>` and exposing the executable scripts of packages (and available manual pages) for use on the command-line."
+msgid "This guide will walk you through creating and packaging a standalone command-line application that can be installed with :ref:`pipx`, a tool for creating and managing :term:`Python Virtual Environments <Virtual Environment>` and exposing the executable scripts of packages (and available manual pages) for use on the command-line."
 msgstr ""
 
 #: ../source/guides/creating-command-line-tools.rst:12
@@ -3098,7 +3098,7 @@ msgid "Now, add an empty :file:`__init__.py` file, to define the project as a re
 msgstr ""
 
 #: ../source/guides/creating-command-line-tools.rst:99
-msgid "The file :file:`__main__.py` marks the main entry point for the application when running it via :mod:`runpy` (i.e. ``python -m greetings``, which works immediately with flat layout, but requires installation of the package with src layout), so initizalize the command-line interface here:"
+msgid "The file :file:`__main__.py` marks the main entry point for the application when running it via :mod:`runpy` (i.e. ``python -m greetings``, which works immediately with flat layout, but requires installation of the package with src layout), so initialize the command-line interface here:"
 msgstr ""
 
 #: ../source/guides/creating-command-line-tools.rst:111
@@ -3142,7 +3142,7 @@ msgid "To just run the program without installing it permanently, use ``pipx run
 msgstr ""
 
 #: ../source/guides/creating-command-line-tools.rst:165
-msgid "This syntax is a bit unpractical, however; as the name of the entry point we defined above does not match the package name, we need to state explicitly which executable script to run (even though there is only on in existence)."
+msgid "This syntax is a bit impractical, however; as the name of the entry point we defined above does not match the package name, we need to state explicitly which executable script to run (even though there is only on in existence)."
 msgstr ""
 
 #: ../source/guides/creating-command-line-tools.rst:168
@@ -4419,7 +4419,7 @@ msgid "Install a package"
 msgstr ""
 
 #: ../source/guides/installing-using-pip-and-virtual-environments.rst:203
-msgid "For example,let's install the `Requests`_ library from the :term:`Python Package Index (PyPI)`:"
+msgid "For example, let's install the `Requests`_ library from the :term:`Python Package Index (PyPI)`:"
 msgstr ""
 
 #: ../source/guides/installing-using-pip-and-virtual-environments.rst:218
@@ -6890,7 +6890,7 @@ msgid "Explanations and Discussions"
 msgstr ""
 
 #: ../source/index.rst:82
-msgid "The :doc:`discussions/index` section for in-depth explanations and discussion about topics, such as:"
+msgid "The :doc:`discussions/index` section provides in-depth explanations and discussion about topics, such as:"
 msgstr ""
 
 #: ../source/index.rst:85
@@ -15605,7 +15605,7 @@ msgid "Source distribution format"
 msgstr ""
 
 #: ../source/specifications/source-distribution-format.rst:8
-msgid "The current standard format of source distribution format is identified by the presence of a :file:`pyproject.toml` file in the distribution archive.  The layout of such a distribution was originally specified in :pep:`517` and is formally documented here."
+msgid "The current standard source distribution format is identified by the presence of a :file:`pyproject.toml` file in the distribution archive.  The layout of such a distribution was originally specified in :pep:`517` and is formally documented here."
 msgstr ""
 
 #: ../source/specifications/source-distribution-format.rst:13
@@ -15621,7 +15621,7 @@ msgid "Source trees"
 msgstr ""
 
 #: ../source/specifications/source-distribution-format.rst:28
-msgid "A *source tree* is a collection of files and directories -- like a version control system checkout -- which contains a :file:`pyproject.toml` file that can be use to build a source distribution from the contained files and directories. :pep:`517` and :pep:`518` specify what is required to meet the definition of what :file:`pyproject.toml` must contain for something to be deemed a source tree."
+msgid "A *source tree* is a collection of files and directories -- like a version control system checkout -- which contains a :file:`pyproject.toml` file that can be used to build a source distribution from the contained files and directories. :pep:`517` and :pep:`518` specify what is required to meet the definition of what :file:`pyproject.toml` must contain for something to be deemed a source tree."
 msgstr ""
 
 #: ../source/specifications/source-distribution-format.rst:38
@@ -15994,7 +15994,7 @@ msgid "``X.Y`` and ``X.Y.0`` are not considered distinct release numbers, as the
 msgstr ""
 
 #: ../source/specifications/version-specifiers.rst:229
-msgid "Date based release segments are also permitted. An example of a date based release scheme using the year and month of the release::"
+msgid "Date-based release segments are also permitted. An example of a date-based release scheme using the year and month of the release::"
 msgstr ""
 
 #: ../source/specifications/version-specifiers.rst:243