typo

Signed-off-by: Edward Welch <[email protected]>

docs/sources/send-data/logstash/_index.md

@@ -17,7 +17,7 @@ The Logstash plugin is not recommended for new deployments. Even as a mechanism
 
 Our experience over the years has found numerous significant challenges using Logstash and this plugin:
 
-  * It's very difficult to configure and get labels correct, conceptually Elasticsearch is a very different database from Loki and users almost always end up sending too many high cardinality labels to Loki which makes getting start with Loki unnecessarily complicated and confusing vs using other clients.
+  * It's very difficult to configure and get labels correct, conceptually Elasticsearch is a very different database from Loki and users almost always end up sending too many high cardinality labels to Loki which makes getting started with Loki unnecessarily complicated and confusing vs using other clients.
   * Logstash and the upstream Beats components implement backoff and flow control which we've found hard to observe leading to ingestion delays into Loki which are hard or impossible to address.
   * It's difficult to impossible to configure Logstash in a way that sending logs to multiple destinations doesn't create scenarios where problems with one database can cause problems with another.
   * We at Grafana Labs have no expertise at configuring Logstash or understanding its configuration language, so we can't help you with it.