diff --git a/doc/common/section_compute_config-api.xml b/doc/common/section_compute_config-api.xml
index 6fd9d90ed2..a35a2b6ea8 100644
--- a/doc/common/section_compute_config-api.xml
+++ b/doc/common/section_compute_config-api.xml
@@ -38,11 +38,8 @@
to configure limits on the type and number of API calls
that can be made in a specific time interval.
When API rate limits are exceeded, HTTP requests return
- an error with a status code of 413
- Request entity too large, and
- includes an HTTP Retry-After header.
- The response body includes the error details and the delay
- before you should retry the request.
+ an error with a status code of 403
+ Forbidden.
Rate limiting is not available for the EC2 API.
diff --git a/doc/config-reference/object-storage/section_object-storage-features.xml b/doc/config-reference/object-storage/section_object-storage-features.xml
index cc50a272ce..32d854ddd2 100644
--- a/doc/config-reference/object-storage/section_object-storage-features.xml
+++ b/doc/config-reference/object-storage/section_object-storage-features.xml
@@ -469,8 +469,7 @@ Sample represents 1.00% of the object partition space
scope of containers that are delegated to non-admin users, exposed to formpost uploads,
or just as a self-imposed sanity check.
Any object PUT operations that exceed these quotas
- return a 413 response (request entity too large) with a
- descriptive body.
+ return a 403 response (forbidden).
Quotas are subject to several limitations: eventual
consistency, the timeliness of the cached container_info
(60 second TTL by default), and it is unable to reject