diff --git a/doc/source/getting_started/comparison/includes/copies.rst b/doc/source/getting_started/comparison/includes/copies.rst
index d0f3d26332d98..4f49c3a1a762e 100644
--- a/doc/source/getting_started/comparison/includes/copies.rst
+++ b/doc/source/getting_started/comparison/includes/copies.rst
@@ -25,4 +25,4 @@ or overwrite the original one:
    most methods (e.g. ``dropna``) except for a very small subset of methods
    (including ``replace``). Both keywords won't be
    necessary anymore in the context of Copy-on-Write. The proposal can be found
-   [here](https://github.com/pandas-dev/pandas/pull/51466).
+   `here <https://github.com/pandas-dev/pandas/pull/51466>`_.
diff --git a/doc/source/whatsnew/v2.0.0.rst b/doc/source/whatsnew/v2.0.0.rst
index be9f105a7b994..2ea0cf8421ff5 100644
--- a/doc/source/whatsnew/v2.0.0.rst
+++ b/doc/source/whatsnew/v2.0.0.rst
@@ -822,7 +822,7 @@ Other API changes
 
     A current PDEP proposes the deprecation and removal of the keywords ``inplace`` and ``copy``
     for all but a small subset of methods from the pandas API. The current discussion takes place
-    at [here](https://github.com/pandas-dev/pandas/pull/51466). The keywords won't be necessary
+    at `here <https://github.com/pandas-dev/pandas/pull/51466>`_. The keywords won't be necessary
     anymore in the context of Copy-on-Write. If this proposal is accepted, both
     keywords would be deprecated in the next release of pandas and removed in pandas 3.0.