From a5739d9455afbed663a4ca1fcac002988c885fcb Mon Sep 17 00:00:00 2001 From: Osama Qarem Date: Sun, 1 Sep 2019 21:27:37 +0800 Subject: [PATCH] Fixed broken link (#3551) --- docs/faq/Performance.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/faq/Performance.md b/docs/faq/Performance.md index f8c2dcfdf8..d4c029c443 100644 --- a/docs/faq/Performance.md +++ b/docs/faq/Performance.md @@ -175,7 +175,7 @@ First, only cache as much data as the user needs. If your application displays a Second, cache an abbreviated form of a record when possible. Sometimes a record includes data that is not relevant to the user. If the application does not depend on this data, it can be omitted from the cache. -Third, only cache a single copy of a record. This is especially important when records contain copies of other records. Cache a unique copy for each record and replace each nested copy with a reference. This is called normalization. Normalization is the preferred approach to storing relational data for [several reasons](../recipes/reducers/NormalizingStateShape.md#designing-a-normalized-state), including efficient memory consumption. +Third, only cache a single copy of a record. This is especially important when records contain copies of other records. Cache a unique copy for each record and replace each nested copy with a reference. This is called normalization. Normalization is the preferred approach to storing relational data for [several reasons](../recipes/structuring-reducers/NormalizingStateShape.md#designing-a-normalized-state), including efficient memory consumption. #### Further information