From 2ca5b808797ccd2c24cfb65a06d98e1db844b1b1 Mon Sep 17 00:00:00 2001 From: Jared Nielsen Date: Thu, 27 Jun 2024 11:02:31 -0400 Subject: [PATCH] remove underscores --- explanation/pre-merge-reviews.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/explanation/pre-merge-reviews.rst b/explanation/pre-merge-reviews.rst index 8431b48..79c6f4c 100644 --- a/explanation/pre-merge-reviews.rst +++ b/explanation/pre-merge-reviews.rst @@ -46,7 +46,7 @@ Working with PreMergeReviews For pre-merge reviews to be effective, however, small modifications to the development workflow are required. The main modification is, of course, requesting peer review of your code changes before merging your -code into :doc:`Trunk `__. The sections below go into the details +code into :doc:`Trunk `. The sections below go into the details of how this is best performed. There is a crib sheet for getting a branch merged on the WorkingWithReviews page.