docs: tip about custom consumers in intro

Author: wkillerud

src/content/docs/introduction/getting-started.md

@@ -77,6 +77,12 @@ guard.on('drop', (metric) => {
 });
 ```
 
+:::tip
+
+Not using Prometheus? You can [write your own metrics consumer](/reference/client/#metrics-consumption) to adapt the metrics to your preferred system.
+
+:::
+
 ## Pipe client data to the consumer
 
 MetricsJS works on streams, so you need to pipe the client data to the consumer:

src/content/docs/reference/client.md

@@ -545,7 +545,7 @@ module2.pipe(consumer);
 
 ### Metrics consumption
 
-In order to consume metrics produced by `@metrics/client` you just need to listen for data and use your favourite metrics client to convert our data format into something usable by your system of choice.
+In order to consume metrics produced by `@metrics/client` you need to listen for data and use your favourite metrics client to convert our data format into something usable by your system of choice.
 
 _Example: Prometheus using prom-client_
 

src/content/docs/reference/guard.md

@@ -95,7 +95,7 @@ action.
 
 ### Metrics threshold
 
-It also might be that an application is just reporting too many different metrics.
+It also might be that an application is reporting too many different metrics.
 
 This guard will also monitor the amount of unique metrics and will start emitting
 a `warn` event when a threshold of allowed unique metrics is exceeded.