Sidecar or Monitor? I chose Sidecar

README.md

@@ -38,6 +38,6 @@ The SMI specification outlines three basic resource types:
 
 * MutualTLS - a resource for managing and configuring encryption between services
 * Canary - a resource for defining flexible routing between different versions of a system
-* Monitor - a resource that defines a side car for basic HTTP monitoring that can be installed alongside an application.
+* Sidecar - a resource that defines a sidecar (e.g. for basic HTTP monitoring) that can be installed alongside an application.
 
-The details of the APIs can be founded in [Specification.md](dpecification.md)
+The details of the APIs can be founded in [specification.md](specification.md)

specification.md

@@ -46,14 +46,14 @@ spec:
     - service-3: 10%
 ```
 
-### Monitor
-The Monitor resource defines a sidecar which is injected alongside the application to perform HTTP monitoring. The Monitor collects standard HTTP metrics (status codes, requests / second, latency, etc) and exposes a common interface using Prometheus metrics.
+### Sidecar
+The Sidecar resource defines a sidecar container which is injected alongside the application. The primary use case is to perform HTTP monitoring. A monitoring sidecar collects standard HTTP metrics (status codes, requests / second, latency, etc) and exposes a common interface using Prometheus metrics.
 These metrics can be picked up by a metrics scraper and pushed to either an in-cluster or
 in-cloud monitoring endpoint.
 
 ```yaml
 apiVersion: v1beta1
-kind: Monitor
+kind: Sidecar
 name: my-monitor
 spec:
   # The monitor sidecar is added to Pods matching these labels
@@ -66,4 +66,4 @@ spec:
     team: my-team
     app: my-server
     region: us-east
-```
+```