Apply suggestions from code review

Co-authored-by: Yim Lee <[email protected]>

Author: ktoso

Sources/MetricsTestUtils/Docs.docc/index.md

@@ -13,7 +13,7 @@ import Metrics
 import MetricsTestUtils
 ```
 
-First, bootstrap the metrics system in your test using the `bootstrapInternal` method which allows overriding existing bootstraps:
+Then bootstrap the metrics system in your test using the `bootstrapInternal` method which allows overriding existing bootstraps:
 
 ```swift
 final class SWIMNIOMetricsTests: XCTestCase {

Sources/MetricsTestUtils/TestMetrics.swift

@@ -158,7 +158,7 @@ extension TestMetrics {
     /// - Parameters:
     ///   - label: the expected label the looked for metric should have
     ///   - dimensions: the expected dimensions the looked for metric should have
-    /// - Returns: the underlying ``TestMetric``
+    /// - Returns: the underlying ``TestCounter``
     /// - Throws: when no such test metric was present
     public func expectCounter(_ label: String, _ dimensions: [(String, String)] = []) throws -> TestCounter {
         let maybeItem = self.lock.withLock {

Sources/SystemMetrics/Docs.docc/index.md

@@ -27,8 +27,8 @@ This makes the System Metrics API available. This adds a new method to `MetricsS
 
 `bootstrapWithSystemMetrics` takes a `SystemMetrics.Configuration` object to configure the system metrics. The config has the following properties:
 
-- interval: The interval at which SystemMetrics are being calculated & exported.
-- dataProvider: A closure returing `SystemMetrics.Data?`. When `nil` no metrics are exported (the default on non-linux platforms). `SystemMetrics.Data` holds all the values mentioned above.
+- interval: The interval at which `SystemMetrics` are being calculated & exported.
+- dataProvider: A closure returning `SystemMetrics.Data?`. When `nil`, no metrics are exported (the default on non-Linux platforms). `SystemMetrics.Data` holds all the values mentioned above.
 - labels: `SystemMetrics.Labels` hold a string label for each of the above mentioned metrics that will be used for the metric labels, along with a prefix that will be used for all above mentioned metrics.
 
 Swift Metrics backend implementations are encouraged to provide static extensions to `SystemMetrics.Configuration` that fit the requirements of their specific backends. For example:

docker/docker-compose.2004.56.yaml

@@ -10,7 +10,7 @@ services:
         swift_version: "5.6"
 
   test:
-    image: swift-metrics:20.04-5.6∂
+    image: swift-metrics:20.04-5.6
     environment:
       - FORCE_TEST_DISCOVERY=--enable-test-discovery
       #- SANITIZER_ARG=--sanitize=thread

docker/docker-compose.2004.57.yaml

@@ -6,8 +6,7 @@ services:
     image: swift-metrics:20.04-5.7
     build:
       args:
-        ubuntu_version: "focal"
-        swift_version: "5.7"
+        base_image: "swiftlang/swift:nightly-5.7-focal"
 
   test:
     image: swift-metrics:20.04-5.7