Browse Source

Fix typos in keystone-specs

Change-Id: Ie3504639be6187b6fae968c1f16b5aa582c8a8a9
baiwenteng 1 year ago
parent
commit
7364e98854
1 changed files with 1 additions and 1 deletions
  1. 1
    1
      specs/keystone/ongoing/unified-limits.rst

+ 1
- 1
specs/keystone/ongoing/unified-limits.rst View File

@@ -244,7 +244,7 @@ and are not meant to mean these will also be implemented.
244 244
   This is a lower level specification (with POC code) that includes
245 245
   putting the limits information in the Token. Overuse of token was a
246 246
   primary concern. Tokens, are by definition, stale information, and
247
-  can be long lived, thus an adminstrator changing limits would have
247
+  can be long lived, thus an administrator changing limits would have
248 248
   no idea when the system would start enforcing them. Token bloat is
249 249
   also a concern for projects that have worker daemons and rely
250 250
   heavily on RPC, as it means more load on the RPC bus.

Loading…
Cancel
Save