From 0f5082d9b8dda924d263659f3a1f38c771d3bf2f Mon Sep 17 00:00:00 2001 From: Teddy Wing Date: Thu, 16 Apr 2015 15:47:53 -0400 Subject: [PATCH] docs/renderers: `StaticHTMLRenderer` instead of `TemplateHTMLRenderer` The `StaticHTMLRenderer` section referred to `TemplateHTMLRenderer` instead of `StaticHTMLRenderer`. --- docs/api-guide/renderers.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/api-guide/renderers.md b/docs/api-guide/renderers.md index 993a3ea2f..751465e9a 100644 --- a/docs/api-guide/renderers.md +++ b/docs/api-guide/renderers.md @@ -135,7 +135,7 @@ See also: `StaticHTMLRenderer` A simple renderer that simply returns pre-rendered HTML. Unlike other renderers, the data passed to the response object should be a string representing the content to be returned. -An example of a view that uses `TemplateHTMLRenderer`: +An example of a view that uses `StaticHTMLRenderer`: @api_view(('GET',)) @renderer_classes((StaticHTMLRenderer,)) @@ -143,7 +143,7 @@ An example of a view that uses `TemplateHTMLRenderer`: data = '

Hello, world

' return Response(data) -You can use `TemplateHTMLRenderer` either to return regular HTML pages using REST framework, or to return both HTML and API responses from a single endpoint. +You can use `StaticHTMLRenderer` either to return regular HTML pages using REST framework, or to return both HTML and API responses from a single endpoint. **.media_type**: `text/html`