From e8ed994d7c7941f7be74f1e7c6a5a03648d04192 Mon Sep 17 00:00:00 2001 From: Google APIs Date: Wed, 20 Jan 2021 18:29:27 -0800 Subject: [PATCH] docs: Updates "unit" description: changes "KBy" to "kBy"; updates an "http" link to "https"; changes "may" to preferred "might", and removes a duplicated period. PiperOrigin-RevId: 352919477 --- google/api/metric.proto | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/google/api/metric.proto b/google/api/metric.proto index a830405d..111a602b 100644 --- a/google/api/metric.proto +++ b/google/api/metric.proto @@ -128,11 +128,11 @@ message MetricDescriptor { // if the `value_type` is `INT64`, `DOUBLE`, or `DISTRIBUTION`. The `unit` // defines the representation of the stored metric values. // - // Different systems may scale the values to be more easily displayed (so a - // value of `0.02KBy` _might_ be displayed as `20By`, and a value of - // `3523KBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is - // `KBy`, then the value of the metric is always in thousands of bytes, no - // matter how it may be displayed.. + // Different systems might scale the values to be more easily displayed (so a + // value of `0.02kBy` _might_ be displayed as `20By`, and a value of + // `3523kBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is + // `kBy`, then the value of the metric is always in thousands of bytes, no + // matter how it might be displayed. // // If you want a custom metric to record the exact number of CPU-seconds used // by a job, you can create an `INT64 CUMULATIVE` metric whose `unit` is @@ -145,7 +145,7 @@ message MetricDescriptor { // or use `Kis{CPU}` and write `11.723` (which is `12005/1024`). // // The supported units are a subset of [The Unified Code for Units of - // Measure](http://unitsofmeasure.org/ucum.html) standard: + // Measure](https://unitsofmeasure.org/ucum.html) standard: // // **Basic units (UNIT)** //