Fix several broken links

Author: rpkilby

docs/api-guide/pagination.md

@@ -312,9 +312,10 @@ The [`drf-proxy-pagination` package][drf-proxy-pagination] includes a `ProxyPagi
 
 ## link-header-pagination
 
-The [`django-rest-framework-link-header-pagination` package][drf-link-header-pagination] includes a `LinkHeaderPagination` class which provides pagination via an HTTP `Link` header as described in [Github's developer documentation](github-link-pagination).
+The [`django-rest-framework-link-header-pagination` package][drf-link-header-pagination] includes a `LinkHeaderPagination` class which provides pagination via an HTTP `Link` header as described in [Github's developer documentation][github-link-pagination].
 
 [cite]: https://docs.djangoproject.com/en/stable/topics/pagination/
+[github-link-pagination]: https://developer.github.com/guides/traversing-with-pagination/
 [link-header]: ../img/link-header-pagination.png
 [drf-extensions]: https://chibisov.github.io/drf-extensions/docs/
 [paginate-by-max-mixin]: https://chibisov.github.io/drf-extensions/docs/#paginatebymaxmixin

docs/api-guide/schemas.md

@@ -290,7 +290,7 @@ class MyView(APIView):
 
 ### OperationId
 
-The schema generator generates an [operationid](openapi-operationid) for each operation. This `operationId` is deduced from the model name, serializer name or view name. The operationId may looks like "listItems", "retrieveItem", "updateItem", etc..
+The schema generator generates an [operationid][openapi-operationid] for each operation. This `operationId` is deduced from the model name, serializer name or view name. The operationId may looks like "listItems", "retrieveItem", "updateItem", etc..
 The `operationId` is camelCase by convention.
 
 If you have several views with the same model, the generator may generate duplicate operationId.
@@ -323,11 +323,11 @@ class MyView(APIView):
 
 ### Components
 
-Since DRF 3.12, Schema uses the [OpenAPI Components](openapi-components). This method defines components in the schema and [references them](openapi-reference) inside request and response objects. By default, the component's name is deduced from the Serializer's name.
+Since DRF 3.12, Schema uses the [OpenAPI Components][openapi-components]. This method defines components in the schema and [references them][openapi-reference] inside request and response objects. By default, the component's name is deduced from the Serializer's name.
 
 Using OpenAPI's components provides the following advantages:
 * The schema is more readable and lightweight.
-* If you use the schema to generate an SDK (using [openapi-generator](openapi-generator) or [swagger-codegen](swagger-codegen)). The generator can name your SDK's models.
+* If you use the schema to generate an SDK (using [openapi-generator][openapi-generator] or [swagger-codegen][swagger-codegen]). The generator can name your SDK's models.
 
 ### Handling component's schema errors
 

docs/community/3.1-announcement.md

@@ -46,7 +46,7 @@ The cursor based pagination renders a more simple style of control:
 
 The pagination API was previously only able to alter the pagination style in the body of the response. The API now supports being able to write pagination information in response headers, making it possible to use pagination schemes that use the `Link` or `Content-Range` headers.
 
-For more information, see the [custom pagination styles](../api-guide/pagination/#custom-pagination-styles) documentation.
+For more information, see the [custom pagination styles](../api-guide/pagination.md#custom-pagination-styles) documentation.
 
 ---
 

docs/community/3.3-announcement.md

@@ -54,7 +54,7 @@ The `ModelSerializer` and `HyperlinkedModelSerializer` classes should now includ
 
 [forms-api]: ../topics/html-and-forms.md
 [ajax-form]: https://github.com/encode/ajax-form
-[jsonfield]: ../api-guide/fields#jsonfield
+[jsonfield]: ../api-guide/fields.md#jsonfield
 [accept-headers]: ../topics/browser-enhancements.md#url-based-accept-headers
 [method-override]: ../topics/browser-enhancements.md#http-header-based-method-overriding
 [django-supported-versions]: https://www.djangoproject.com/download/#supported-versions

docs/community/3.4-announcement.md

@@ -179,16 +179,16 @@ The full set of itemized release notes [are available here][release-notes].
 [moss]: mozilla-grant.md
 [funding]: funding.md
 [core-api]: https://www.coreapi.org/
-[command-line-client]: api-clients#command-line-client
-[client-library]: api-clients#python-client-library
+[command-line-client]: ../topics/api-clients.md#command-line-client
+[client-library]: ../topics/api-clients.md#python-client-library
 [core-json]: https://www.coreapi.org/specification/encoding/#core-json-encoding
 [swagger]: https://openapis.org/specification
 [hyperschema]: https://json-schema.org/latest/json-schema-hypermedia.html
 [api-blueprint]: https://apiblueprint.org/
-[tut-7]: ../tutorial/7-schemas-and-client-libraries/
-[schema-generation]: ../api-guide/schemas/
+[tut-7]: ../coreapi/7-schemas-and-client-libraries.md
+[schema-generation]: ../api-guide/schemas.md
 [api-clients]: ../topics/api-clients.md
 [milestone]: https://github.com/encode/django-rest-framework/milestone/35
-[release-notes]: release-notes#34
-[metadata]: ../api-guide/metadata/#custom-metadata-classes
+[release-notes]: release-notes.md#34
+[metadata]: ../api-guide/metadata.md#custom-metadata-classes
 [gh3751]: https://github.com/encode/django-rest-framework/issues/3751

docs/community/3.5-announcement.md

@@ -258,9 +258,9 @@ in version 3.3 and raised a deprecation warning in 3.4. Its usage is now mandato
 [funding]: funding.md
 [uploads]: https://core-api.github.io/python-client/api-guide/utils/#file
 [downloads]: https://core-api.github.io/python-client/api-guide/codecs/#downloadcodec
-[schema-generation-api]: ../api-guide/schemas/#schemagenerator
-[schema-docs]: ../api-guide/schemas/#schemas-as-documentation
-[schema-view]: ../api-guide/schemas/#the-get_schema_view-shortcut
+[schema-generation-api]: ../coreapi/schemas.md#schemagenerator
+[schema-docs]: ../coreapi/schemas.md#schemas-as-documentation
+[schema-view]: ../coreapi/schemas.md#the-get_schema_view-shortcut
 [django-rest-raml]: https://github.com/encode/django-rest-raml
 [raml-image]: ../img/raml.png
 [raml-codec]: https://github.com/core-api/python-raml-codec

docs/community/third-party-packages.md

@@ -288,7 +288,7 @@ To submit new content, [open an issue][drf-create-issue] or [create a pull reque
 [drf-create-issue]: https://github.com/encode/django-rest-framework/issues/new
 [authentication]: ../api-guide/authentication.md
 [permissions]: ../api-guide/permissions.md
-[third-party-packages]: ../topics/third-party-packages/#existing-third-party-packages
+[third-party-packages]: #existing-third-party-packages
 [discussion-group]: https://groups.google.com/forum/#!forum/django-rest-framework
 [djangorestframework-digestauth]: https://github.com/juanriaza/django-rest-framework-digestauth
 [django-oauth-toolkit]: https://github.com/evonove/django-oauth-toolkit

docs/topics/documenting-your-api.md

@@ -209,7 +209,7 @@ To implement a hypermedia API you'll need to decide on an appropriate media type
 [cite]: https://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven
 
 [hypermedia-docs]: rest-hypermedia-hateoas.md
-[metadata-docs]: ../api-guide/metadata/
+[metadata-docs]: ../api-guide/metadata.md
 [schemas-examples]: ../api-guide/schemas/#examples
 
 [image-drf-yasg]: ../img/drf-yasg.png