From 53bdc3d748eae6cb75dc18101d686e54a234eca3 Mon Sep 17 00:00:00 2001 From: Piero Toffanin Date: Thu, 31 Aug 2017 17:53:28 -0400 Subject: [PATCH] Docs typos --- slate/source/includes/reference/_authentication.md | 4 ++-- slate/source/includes/reference/_handlingerrors.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/slate/source/includes/reference/_authentication.md b/slate/source/includes/reference/_authentication.md index 0eb91daf..0becd11f 100644 --- a/slate/source/includes/reference/_authentication.md +++ b/slate/source/includes/reference/_authentication.md @@ -51,6 +51,6 @@ Since applications sometimes do not allow headers to be modified, you can also a ### Token Expiration -The token expires after a set amount of time. The expiration time is dependent on WebODM's settings. You will need to request another token when a token expires. +The token expires after a predefined amount of time. The expiration time is dependent on WebODM's settings. You will need to request another token when a token expires. -You know that a token has expired if any call to an API returns a `403` status code with the JSON body `{'detail': 'Signature has expired.'}`. +You know that a token has expired if any API call returns a `403` status code with the JSON body `{'detail': 'Signature has expired.'}`. diff --git a/slate/source/includes/reference/_handlingerrors.md b/slate/source/includes/reference/_handlingerrors.md index 53763825..92c66eb9 100644 --- a/slate/source/includes/reference/_handlingerrors.md +++ b/slate/source/includes/reference/_handlingerrors.md @@ -1,6 +1,6 @@ ## Handling Errors -All API calls use the status codes as described in the [Django REST Framework's Status Code Guide](http://www.django-rest-framework.org/api-guide/status-codes/), but generally you only need to check for success status code (status code `200` or `204`) and handle the special case of [Token Expiration](#token-expiration) (status code `403`) and report an error otherwise. +All API calls use the status codes as described in the [Django REST Framework's Status Code Guide](http://www.django-rest-framework.org/api-guide/status-codes/), but generally you only need to check for success status codes (`200` or `204`), handle the special case of [Token Expiration](#token-expiration) (`403`) and report an error otherwise. ### Error Status Codes @@ -13,4 +13,4 @@ Status Code | Description 400 | Malformed request 404 | Not found -For security reasons, sometimes an operation which should return `403` returns `404` to avoid disclosing IDs and other information from attackers. +For security reasons, sometimes an operation which should return `403` returns `404` to avoid disclosing IDs and other information to attackers.