From fa0459d9361b4be27babea5451e1a160cd84b7ea Mon Sep 17 00:00:00 2001
From: skirtle <65301168+skirtles-code@users.noreply.github.com>
Date: Fri, 8 Jan 2021 01:51:15 +0000
Subject: [PATCH] docs: add links to the guide from the migration guide for
 v-if/v-for

---
 src/guide/migration/v-if-v-for.md | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/src/guide/migration/v-if-v-for.md b/src/guide/migration/v-if-v-for.md
index 5461834320..75f52016cf 100644
--- a/src/guide/migration/v-if-v-for.md
+++ b/src/guide/migration/v-if-v-for.md
@@ -27,3 +27,8 @@ In 3.x, `v-if` will always have the higher precedence than `v-for`.
 It is recommended to avoid using both on the same element due to the syntax ambiguity.
 
 Rather than managing this at the template level, one method for accomplishing this is to create a computed property that filters out a list for the visible elements.
+
+## See also
+
+- [List Rendering - Displaying Filtered/Sorted Results](/guide/list.html#displaying-filtered-sorted-results)
+- [List Rendering - `v-for` with `v-if`](/guide/list.html#v-for-with-v-if)