From 381115940566e52ee9152d87291ff26225d44988 Mon Sep 17 00:00:00 2001
From: shannonbux <32467162+shannonbux@users.noreply.github.com>
Date: Wed, 9 Jan 2019 10:42:19 -0800
Subject: [PATCH] Update debugging-replace-renderer-api.md

---
 docs/docs/debugging-replace-renderer-api.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/docs/docs/debugging-replace-renderer-api.md b/docs/docs/debugging-replace-renderer-api.md
index 4b7dab3231f3e..ec3891435f67b 100644
--- a/docs/docs/debugging-replace-renderer-api.md
+++ b/docs/docs/debugging-replace-renderer-api.md
@@ -2,6 +2,10 @@
 title: Debugging replaceRenderer API
 ---
 
+## Prerequisites
+
+If you’re not familiar with Gatsby’s lifecycle, see the overview [Gatsby Lifecycle APIs](/gatsby-lifecycle-apis/).
+
 ## What is the `replaceRenderer` API?
 
 The `replaceRenderer` API is one of [Gatsby's Server Side Rendering (SSR) extension APIs](/docs/ssr-apis/#replaceRenderer). This API is called when you run `gatsby build` and is used to customise how Gatsby renders your static content. It can be implemented by any Gatsby plugin or your `gatsby-ssr.js` file - adding support for Redux, CSS-in-JS libraries or any code that needs to change Gatsby's default HTML output.