From 586b8ca5ef96517bec7b02f0ce1a28d9da56cce2 Mon Sep 17 00:00:00 2001 From: Jason Myers Date: Thu, 12 Feb 2015 19:10:09 -0600 Subject: [PATCH] Making utilization the default spelling This fixes the inconsistent usage of utilisation and utilization. Change-Id: I4840411c144fd7d0990ca5c445fbc5231b0b622c --- doc/source/measurements.rst | 2 +- doc/source/webapi/v2.rst | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/source/measurements.rst b/doc/source/measurements.rst index 6bdcefd96..617135a17 100644 --- a/doc/source/measurements.rst +++ b/doc/source/measurements.rst @@ -73,7 +73,7 @@ instance: g instance inst ID both 1, 2, 3, memory g MB inst ID n 1, 2 Volume of RAM allocated memory.usage g MB inst ID p 1, 2, 3, 4 Volume of RAM used cpu c ns inst ID p 1, 2 CPU time used -cpu_util g % inst ID p 1, 2, 3, 4 Average CPU utilisation +cpu_util g % inst ID p 1, 2, 3, 4 Average CPU utilization vcpus g vcpu inst ID n 1, 2 Number of VCPUs disk.read.requests c request inst ID p 1, 2 Number of read requests disk.read.requests.rate g request/s inst ID p 1, 2, 3 Average rate of reads diff --git a/doc/source/webapi/v2.rst b/doc/source/webapi/v2.rst index 463b1fe0b..590c0baba 100644 --- a/doc/source/webapi/v2.rst +++ b/doc/source/webapi/v2.rst @@ -347,7 +347,7 @@ Get the list of samples about instances with *m1.tiny* flavor running for June Now you may want to have statistics on the meters you are targeting. Consider the following example where you are getting the list of samples -about CPU utilisation of a given instance (identified by its *resource_id*) +about CPU utilization of a given instance (identified by its *resource_id*) running for June 2013:: GET /v2/meters/cpu_util