Fix small typos in proposal README (#3)

* Fix small typo

* Slight rewording, if things are cached depends on the handler
This commit is contained in:
Konrad `ktoso` Malawski 2019-01-18 16:08:02 +09:00 committed by tomer doron
parent edb434ef6b
commit ac6fe4405f
1 changed files with 2 additions and 2 deletions

View File

@ -23,7 +23,7 @@ The proposed solution is to introduce the following types that encapsulate metri
counter.increment(100)
```
`Recorder`: A recorder collects observations within a time window (usually things like response sizes) and *can* provides aggregated information about the data sample, for example count, sum, min, max and various quantiles.
`Recorder`: A recorder collects observations within a time window (usually things like response sizes) and *can* provide aggregated information about the data sample, for example count, sum, min, max and various quantiles.
```swift
recorder.record(100)
@ -60,7 +60,7 @@ How would you use `counter`, `recorder`, `gauge` and `timer` in you application
}
```
To ensure performance, `Metrics.makeXxx` will returned a cached copy of the metric object so can be called on the hot path.
To ensure performance, `Metrics.makeXxx` can return a cached copy of the metric object so can be called on the hot path.
## Detailed design