summaryrefslogtreecommitdiff
path: root/api-guide/source/limits.rst
diff options
context:
space:
mode:
Diffstat (limited to 'api-guide/source/limits.rst')
-rw-r--r--api-guide/source/limits.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/api-guide/source/limits.rst b/api-guide/source/limits.rst
index 8229d5ee5b..5208892a98 100644
--- a/api-guide/source/limits.rst
+++ b/api-guide/source/limits.rst
@@ -8,7 +8,7 @@ two kinds of limits: *rate limits* and *absolute limits*. Rate limits
are thresholds that are reset after a certain amount of time passes.
Absolute limits are fixed. Limits are configured by operators and may
differ from one deployment of the OpenStack Compute service to
-another. Please contact your provider to determine the limits that
+another. Please contact your provider to determine the limits that
apply to your account. Your provider may be able to adjust your
account's limits if they are too low. Also see the API Reference for
`*Limits* <http://developer.openstack.org/api-ref-compute-v2.html#compute_limits>`__.
@@ -58,7 +58,7 @@ Absolute limits
Absolute limits are specified as name/value pairs. The name of the
absolute limit uniquely identifies the limit within a deployment. Please
-consult your provider for an exhaustive list of absolute value names. An
+consult your provider for an exhaustive list of absolute limits names. An
absolute limit value is always specified as an integer. The name of the
absolute limit determines the unit type of the integer value. For
example, the name maxServerMeta implies that the value is in terms of