Copyedit news entries before 25.0

ichard26 · ichard26 · commit d35384ef91cb · 2025-01-24T18:09:21.000-05:00
diff --git a/news/12176.feature.rst b/news/12176.feature.rst
@@ -1 +1 @@
-Pip now returns the size, along with the number, of files cleared on ``pip cache purge`` and ``pip cache remove``
+Return the size, along with the number, of files cleared on ``pip cache purge`` and ``pip cache remove``
diff --git a/news/13048.process.rst b/news/13048.process.rst
@@ -1,3 +1 @@
 Started releasing to PyPI from a GitHub Actions CI/CD workflow that implements trusted publishing and bundles :pep:`740` digital attestations.
-
-In addition to being signed, the released distribution packages are now reproducible through the commit timestamp.
diff --git a/news/13079.bugfix.rst b/news/13079.bugfix.rst
@@ -1 +1,2 @@
-This change fixes a security bug allowing a wheel to execute code during installation.
+Fix a security bug allowing a specially crafted wheel to execute code during
+installation.
diff --git a/news/13112.feature.rst b/news/13112.feature.rst
@@ -1 +1 @@
-Prefer to display ``License-Expression`` in ``pip show`` if metadata version is at least 2.4.
+Prefer to display :pep:`639` ``License-Expression`` in ``pip show`` if metadata version is at least 2.4.
diff --git a/news/13134.feature.rst b/news/13134.feature.rst
@@ -1,4 +1,4 @@
-Support :pep:`639` License-Expression and License-File metadata fields in JSON
+Support :pep:`639` ``License-Expression`` and ``License-File`` metadata fields in JSON
 output. ``pip inspect`` and ``pip install --report`` now emit
 ``license_expression`` and ``license_file`` fields in the ``metadata`` object,
 if the corresponding fields are present in the installed ``METADATA`` file.
diff --git a/news/13163.bugfix.rst b/news/13163.bugfix.rst
@@ -1,4 +1,4 @@
-Note: Packaging 24.2 changes how pre-release specifiers with ``<`` and ``>``
+The inclusion of packaging 24.2 changes how pre-release specifiers with ``<`` and ``>``
 behave. Including a pre-release version with these specifiers now implies
 accepting pre-releases (e.g., ``<2.0dev`` can include ``1.0rc1``). To avoid
 implying pre-releases, avoid specifying them (e.g., use ``<2.0``).
diff --git a/news/5502.bugfix.rst b/news/5502.bugfix.rst
@@ -1,2 +1,3 @@
-Configured TLS server and client certificates are now used while installing build dependencies.
-Consequently, the private ``_PIP_STANDALONE_CERT`` environment variable is no longer used.
+The ``--cert`` and ``--client-cert`` command-line options are now respected while
+installing build dependencies. Consequently, the private ``_PIP_STANDALONE_CERT``
+environment variable is no longer used.

Original file line number	Diff line number	Diff line change
`@@ -1 +1 @@`
`1`		-Pip now returns the size, along with the number, of files cleared on ``pip cache purge`` and ``pip cache remove``
	`1`	+Return the size, along with the number, of files cleared on ``pip cache purge`` and ``pip cache remove``
Original file line number	Diff line number	Diff line change
`@@ -1,3 +1 @@`
`1`	`1`	Started releasing to PyPI from a GitHub Actions CI/CD workflow that implements trusted publishing and bundles :pep:`740` digital attestations.
`2`		`-`
`3`		`-In addition to being signed, the released distribution packages are now reproducible through the commit timestamp.`
Original file line number	Diff line number	Diff line change
`@@ -1 +1,2 @@`
`1`		`-This change fixes a security bug allowing a wheel to execute code during installation.`
	`1`	`+Fix a security bug allowing a specially crafted wheel to execute code during`
	`2`	`+installation.`
Original file line number	Diff line number	Diff line change
`@@ -1 +1 @@`
`1`		-Prefer to display ``License-Expression`` in ``pip show`` if metadata version is at least 2.4.
	`1`	+Prefer to display :pep:`639` ``License-Expression`` in ``pip show`` if metadata version is at least 2.4.
Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		-Note: Packaging 24.2 changes how pre-release specifiers with ``<`` and ``>``
	`1`	+The inclusion of packaging 24.2 changes how pre-release specifiers with ``<`` and ``>``
`2`	`2`	`behave. Including a pre-release version with these specifiers now implies`
`3`	`3`	accepting pre-releases (e.g., ``<2.0dev`` can include ``1.0rc1``). To avoid
`4`	`4`	implying pre-releases, avoid specifying them (e.g., use ``<2.0``).