From 6499a065dc2968961f2a32946d96877e7c76a7eb Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Micha=C5=82=20K=C4=99pie=C5=84?= <michal@isc.org>
Date: Tue, 20 Feb 2018 16:47:12 -0500
Subject: [PATCH] Link to a separate article about backporting merge requests

---
 best-practices.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/best-practices.md b/best-practices.md
index 2df7f24..af865ec 100644
--- a/best-practices.md
+++ b/best-practices.md
@@ -57,6 +57,6 @@ Other branches might be force pushed at convenience of the people that work on t
 
 Yes, we do.  With non-squashed merges, it doesn't add any (historical) value to keep the branches around, and gitlab can automatically delete the branch after the merge.
 
-### How to backport merge request?
+### How to backport a Merge Request?
 
-After the merge request is merged there's an option to use the same commits to create new merge request on different branch.  Generally, this approach should be used.
+See the [relevant article](backporting-a-merge-request).