docs: fix link (#769)

Co-authored-by: pyansys-ci-bot <[email protected]>
Co-authored-by: Camille <[email protected]>

Author: 3 people

doc/source/changelog/769.documentation.md

@@ -0,0 +1 @@
+fix link

doc/source/migrations/index.rst

@@ -18,15 +18,15 @@ Version ``v9.0``
 
   .. warning::
 
-    Using the trusted publisher approach in ansys pypi release actions is not possible anymore.
-    The reason for that is related to the action
+    Using the trusted publisher approach in ``ansys/release-pypi-public`` and ``ansys/release-pypi-private`` actions is
+    not possible anymore. The reason for that is related to the action
     `pypa/gh-action-pypi-publish <https://github.com/pypa/gh-action-pypi-publish>`_ which allows to use the trusted
-    publisher. Indeed, starting with versions `v1.12.0` of this action, it is no longer possible to use the action in
-    a composite action, see
+    publisher. Indeed, it is no longer possible to use the action in a composite action for versions after ``v1.12.0``, see
     `pypa/[email protected] <https://github.com/pypa/gh-action-pypi-publish/releases/tag/v1.12.0>`_.
     However, the latest versions of this action is required to upload
-    `PEP 639 licensing metadata <https://packaging.python.org/en/latest/specifications/core-metadata/#license-expression>`
-    to PyPI. This allows to avoid adding upper bounds on build system like ``setuptools<=67.0.0``, ``wheel<0.46.0`` or ``flit_core>=3.2,<3.11``.
+    `PEP 639 licensing metadata <https://packaging.python.org/en/latest/specifications/core-metadata/#license-expression>`_
+    to PyPI. This allows to avoid adding upper bounds on build system like ``setuptools<=67.0.0``, ``wheel<0.46.0`` or
+    ``flit_core>=3.2,<3.11``.
 
 **Migration Steps:**