fixing thin and zero width white space characters in docs (#18019)

(cherry picked from commit 5f7a6cd)

Author: georgewallace

docs/reference/event-api.md

@@ -5,7 +5,7 @@ mapped_pages:
 
 # Event API [event-api]
 
-This section is targeted for plugin developers and users of Logstash’s Ruby filter. Below we document recent changes (starting with version 5.0) in the way users have been accessing Logstash’s event based data in custom plugins and in the Ruby filter. Note that [Accessing event data and fields](/reference/event-dependent-configuration.md) data flow in Logstash’s config files — using [Field references](/reference/event-dependent-configuration.md#logstash-config-field-references) — is not affected by this change, and will continue to use existing syntax.
+This section is targeted for plugin developers and users of Logstash’s Ruby filter. Below we document recent changes (starting with version 5.0) in the way users have been accessing Logstash’s event based data in custom plugins and in the Ruby filter. Note that [Accessing event data and fields](/reference/event-dependent-configuration.md) data flow in Logstash’s config files — using [Field references](/reference/event-dependent-configuration.md#logstash-config-field-references) — is not affected by this change, and will continue to use existing syntax.
 
 
 ## Event Object [_event_object]

docs/reference/event-dependent-configuration.md

@@ -19,7 +19,7 @@ Event and data field types:
 
 
 ::::{important}
-Some configuration options in Logstash require the existence of fields in order to function. Because inputs generate events, there are no fields to evaluate within the input block—​they do not exist yet!
+Some configuration options in Logstash require the existence of fields in order to function. Because inputs generate events, there are no fields to evaluate within the input block—they do not exist yet!
 
 [Field references](#logstash-config-field-references), [sprintf format](#sprintf), and [conditionals](#conditionals) do not work in input blocks.
 These configuration options depend on events and fields, and therefore, work only within filter and output blocks.

docs/reference/how-logstash-works.md

@@ -37,7 +37,7 @@ For more information about the available filters, see [Filter Plugins](logstash-
 
 Outputs are the final phase of the Logstash pipeline. An event can pass through multiple outputs, but once all output processing is complete, the event has finished its execution. Some commonly used outputs include:
 
-* **elasticsearch**: send event data to Elasticsearch. If you’re planning to save your data in an efficient, convenient, and easily queryable format…​ Elasticsearch is the way to go. Period. Yes, we’re biased :)
+* **elasticsearch**: send event data to Elasticsearch. If you’re planning to save your data in an efficient, convenient, and easily queryable format… Elasticsearch is the way to go. Period. Yes, we’re biased :)
 * **file**: write event data to a file on disk.
 * **graphite**: send event data to graphite, a popular open source tool for storing and graphing metrics. [http://graphite.readthedocs.io/en/latest/](http://graphite.readthedocs.io/en/latest/)
 * **statsd**: send event data to statsd, a service that "listens for statistics, like counters and timers, sent over UDP and sends aggregates to one or more pluggable backend services". If you’re already using statsd, this could be useful for you!

docs/reference/installing-logstash.md

@@ -8,7 +8,7 @@ mapped_pages:
 
 ## Installing from a Downloaded Binary [installing-binary]
 
-The {{ls}} binaries are available from [https://www.elastic.co/downloads](https://www.elastic.co/downloads/logstash). Download the Logstash installation file for your host environment—​TAR.GZ, DEB, ZIP, or RPM.
+The {{ls}} binaries are available from [https://www.elastic.co/downloads](https://www.elastic.co/downloads/logstash). Download the Logstash installation file for your host environment—TAR.GZ, DEB, ZIP, or RPM.
 
 Unpack the file. Do not install Logstash into a directory path that contains colon (:) characters.
 

docs/reference/logging.md

@@ -45,7 +45,7 @@ These appenders define:
 * **triggering policies** that determine *if* a rollover should be performed, and
 * **rollover strategy**  to defines *how* the rollover should be done.
 
-By default, two triggering policies are defined—​time and size.
+By default, two triggering policies are defined—time and size.
 
 * The **time** policy creates one file per day.
 * The **size** policy forces the creation of a new file after the file size surpasses 100 MB.