From 372f4fde2079238e7c7a94119220b738c69e282e Mon Sep 17 00:00:00 2001
From: linchiwei123 <40888469+linchiwei123@users.noreply.github.com>
Date: Sat, 6 Jul 2019 13:30:01 +0800
Subject: [PATCH] Update pagination.md (#6787)

it seems like that
---
 docs/api-guide/pagination.md | 10 ++++------
 1 file changed, 4 insertions(+), 6 deletions(-)

diff --git a/docs/api-guide/pagination.md b/docs/api-guide/pagination.md
index 99612ef46..47be37f33 100644
--- a/docs/api-guide/pagination.md
+++ b/docs/api-guide/pagination.md
@@ -257,6 +257,10 @@ To have your custom pagination class be used by default, use the `DEFAULT_PAGINA
 
 API responses for list endpoints will now include a `Link` header, instead of including the pagination links as part of the body of the response, for example:
 
+![Link Header][link-header]
+
+*A custom pagination style, using the 'Link' header'*
+
 ## Pagination & schemas
 
 You can also make the pagination controls available to the schema autogeneration
@@ -268,12 +272,6 @@ The method should return a list of `coreapi.Field` instances.
 
 ---
 
-![Link Header][link-header]
-
-*A custom pagination style, using the 'Link' header'*
-
----
-
 # HTML pagination controls
 
 By default using the pagination classes will cause HTML pagination controls to be displayed in the browsable API. There are two built-in display styles. The `PageNumberPagination` and `LimitOffsetPagination` classes display a list of page numbers with previous and next controls. The `CursorPagination` class displays a simpler style that only displays a previous and next control.