From 7364e988541988a711edf1cad4af4046565c4874 Mon Sep 17 00:00:00 2001 From: baiwenteng Date: Thu, 8 Feb 2018 11:47:54 +0800 Subject: [PATCH] Fix typos in keystone-specs Change-Id: Ie3504639be6187b6fae968c1f16b5aa582c8a8a9 --- specs/keystone/ongoing/unified-limits.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/specs/keystone/ongoing/unified-limits.rst b/specs/keystone/ongoing/unified-limits.rst index a40ddba9..7c2a0306 100644 --- a/specs/keystone/ongoing/unified-limits.rst +++ b/specs/keystone/ongoing/unified-limits.rst @@ -244,7 +244,7 @@ and are not meant to mean these will also be implemented. This is a lower level specification (with POC code) that includes putting the limits information in the Token. Overuse of token was a primary concern. Tokens, are by definition, stale information, and - can be long lived, thus an adminstrator changing limits would have + can be long lived, thus an administrator changing limits would have no idea when the system would start enforcing them. Token bloat is also a concern for projects that have worker daemons and rely heavily on RPC, as it means more load on the RPC bus.