diff --git a/doc/source/contributor/policies/code-reviews.rst b/doc/source/contributor/policies/code-reviews.rst index 320f4c2d9d4..bb22ae31931 100644 --- a/doc/source/contributor/policies/code-reviews.rst +++ b/doc/source/contributor/policies/code-reviews.rst @@ -128,7 +128,7 @@ Stackalytics provides some nice interfaces to track review statistics. The links statistics are used to track not only Neutron core reviewer statistics, but also to track review statistics for potential future core members. -* `30 day review stats `_ -* `60 day review stats `_ -* `90 day review stats `_ -* `180 day review stats `_ +* `30 day review stats `_ +* `60 day review stats `_ +* `90 day review stats `_ +* `180 day review stats `_ diff --git a/doc/source/contributor/policies/neutron-teams.rst b/doc/source/contributor/policies/neutron-teams.rst index 816afd0294a..4404732aa02 100644 --- a/doc/source/contributor/policies/neutron-teams.rst +++ b/doc/source/contributor/policies/neutron-teams.rst @@ -317,10 +317,10 @@ maintain a level of review numbers relatively close to other core reviewers. There are no hard statistics around code review numbers, but in general we use 30, 60, 90 and 180 day stats when examining review stats. -* `30 day review stats `_ -* `60 day review stats `_ -* `90 day review stats `_ -* `180 day review stats `_ +* `30 day review stats `_ +* `60 day review stats `_ +* `90 day review stats `_ +* `180 day review stats `_ There are soft-touch items around being a Neutron core reviewer as well. Gaining trust with the existing Neutron core reviewers is important. Being