From 1a09983dfc2d7ac03f2722e054e04c300bf77e65 Mon Sep 17 00:00:00 2001
From: Tom Christie <tom@tomchristie.com>
Date: Fri, 5 Oct 2012 13:51:09 +0100
Subject: [PATCH] Tweak doc headings

---
 docs/api-guide/renderers.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/docs/api-guide/renderers.md b/docs/api-guide/renderers.md
index d2d8985df..f27eb3601 100644
--- a/docs/api-guide/renderers.md
+++ b/docs/api-guide/renderers.md
@@ -60,6 +60,8 @@ For example if your API serves JSON responses and the HTML browseable API, you m
 
 If your API includes views that can serve both regular webpages and API responses depending on the request, then you might consider making `TemplateHTMLRenderer` your default renderer, in order to play nicely with older browsers that send [broken accept headers][browser-accept-headers].
 
+# API Reference
+
 ## JSONRenderer
 
 **.media_type:** `application/json`
@@ -117,7 +119,7 @@ If you're building websites that use `HTMLTemplateRenderer` along with other ren
 
 To implement a custom renderer, you should override `BaseRenderer`, set the `.media_type` and `.format` properties, and implement the `.render(self, data, media_type)` method.
 
-## Advanced renderer usage
+# Advanced renderer usage
 
 You can do some pretty flexible things using REST framework's renderers.  Some examples...