diff --git a/docs/api-guide/metadata.md b/docs/api-guide/metadata.md index 20708c6e3..f4e8ed2da 100644 --- a/docs/api-guide/metadata.md +++ b/docs/api-guide/metadata.md @@ -66,7 +66,7 @@ The REST framework package only includes a single metadata class implementation, ## Creating schema endpoints -If you have specific requirements for creating schema endpoints that are accessed with regular `GET` requests, you might consider re-using the metadata API for doing so. +If you have specific requirements for creating schema endpoints that are accessed with regular `GET` requests, you might consider reusing the metadata API for doing so. For example, the following additional route could be used on a viewset to provide a linkable schema endpoint. diff --git a/docs/api-guide/testing.md b/docs/api-guide/testing.md index 97b432ddd..a84379eef 100644 --- a/docs/api-guide/testing.md +++ b/docs/api-guide/testing.md @@ -92,7 +92,7 @@ For example, when forcibly authenticating using a token, you might do something --- -**Note**: `force_authenticate` directly sets `request.user` to the in-memory `user` instance. If you are re-using the same `user` instance across multiple tests that update the saved `user` state, you may need to call [`refresh_from_db()`][refresh_from_db_docs] between tests. +**Note**: `force_authenticate` directly sets `request.user` to the in-memory `user` instance. If you are reusing the same `user` instance across multiple tests that update the saved `user` state, you may need to call [`refresh_from_db()`][refresh_from_db_docs] between tests. --- diff --git a/docs/api-guide/validators.md b/docs/api-guide/validators.md index e3407e8a3..3a122a3c6 100644 --- a/docs/api-guide/validators.md +++ b/docs/api-guide/validators.md @@ -5,7 +5,7 @@ source: # Validators -> Validators can be useful for re-using validation logic between different types of fields. +> Validators can be useful for reusing validation logic between different types of fields. > > — [Django documentation][cite]