From 4f57bfda388977fe41bb740e3ef6ec3a9d5401d5 Mon Sep 17 00:00:00 2001
From: Nicolas <50466554+rasnick@users.noreply.github.com>
Date: Sat, 9 Nov 2019 17:47:37 -0300
Subject: [PATCH] Wrong link to Profiling components article (#2552)

Recommended article link, written by Ben Schwarz, returns a 404. Updated with correct link.
---
 content/docs/optimizing-performance.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/docs/optimizing-performance.md b/content/docs/optimizing-performance.md
index b5aea3bd6..8354166e6 100644
--- a/content/docs/optimizing-performance.md
+++ b/content/docs/optimizing-performance.md
@@ -176,7 +176,7 @@ To do this in Chrome:
 
 6. React events will be grouped under the **User Timing** label.
 
-For a more detailed walkthrough, check out [this article by Ben Schwarz](https://calibreapp.com/blog/2017-11-28-debugging-react/).
+For a more detailed walkthrough, check out [this article by Ben Schwarz](https://building.calibreapp.com/debugging-react-performance-with-react-16-and-chrome-devtools-c90698a522ad).
 
 Note that **the numbers are relative so components will render faster in production**. Still, this should help you realize when unrelated UI gets updated by mistake, and how deep and how often your UI updates occur.