From 4730088a227c68f51e419f7373a3b9f6e8204c9a Mon Sep 17 00:00:00 2001 From: Carla Date: Tue, 17 May 2016 16:11:58 +0200 Subject: [PATCH] Update quota_management.md --- doc/internal/quota_management.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/internal/quota_management.md b/doc/internal/quota_management.md index e92f172..860c461 100644 --- a/doc/internal/quota_management.md +++ b/doc/internal/quota_management.md @@ -3,7 +3,7 @@ All the services from Dataservices API are subject to quota management: check, l There are three main fields in the quota management: - **Quota**: Number of requests of this kind the user could make, eg. Number of street geocoding requests -- **Soft limit**: This flag enables the user to surpass their assigned quota. When this flag is activated, there is no quota check so the user could make all the requests that they want. +- **Soft limit**: This flag enables the user to surpass their assigned quota. When this flag is activated, there is no quota check so the user could make all the requests that they want. Consequently, the `hard_limit` flag, when enabled, indicates that the user cannot surpass the assigned quota. - **Block price**: Price for every 1000 requests