docs: use normal - in the docs

Author: aminya

src/index.ts

@@ -159,7 +159,7 @@ export interface Writable<
    *   they are dropped**, you should implement a [simple
    *   queue](examples/queue/queue.ts) in JavaScript. Such a queue is not
    *   provided by this library because most real world applications need to
-   *   deal with undeliverable messages in more complex ways – for example, they
+   *   deal with undeliverable messages in more complex ways - for example, they
    *   might need to reply with a status message; or first retry delivery a
    *   certain number of times before giving up.
    *
@@ -902,14 +902,14 @@ declare module "./native" {
      * Returns the current security mechanism for the socket, if any. The
      * security mechanism is set implictly by using any of the relevant security
      * options. The returned value is one of:
-     * * `null` – No security mechanism is used.
-     * * `"plain"` – The PLAIN mechanism defines a simple username/password
+     * * `null` - No security mechanism is used.
+     * * `"plain"` - The PLAIN mechanism defines a simple username/password
      *   mechanism that lets a server authenticate a client. PLAIN makes no
      *   attempt at security or confidentiality.
-     * * `"curve"` – The CURVE mechanism defines a mechanism for secure
+     * * `"curve"` - The CURVE mechanism defines a mechanism for secure
      *   authentication and confidentiality for communications between a client
      *   and a server. CURVE is intended for use on public networks.
-     * * `"gssapi"` – The GSSAPI mechanism defines a mechanism for secure
+     * * `"gssapi"` - The GSSAPI mechanism defines a mechanism for secure
      *   authentication and confidentiality for communications between a client
      *   and a server using the Generic Security Service Application Program
      *   Interface (GSSAPI). The GSSAPI mechanism can be used on both public and
@@ -1002,7 +1002,7 @@ export class Publisher extends Socket {
    *
    * If set to `true`, a socket shall keep only one message in its
    * inbound/outbound queue: the last message to be received/sent. Ignores any
-   * high water mark options. Does not support multi-part messages – in
+   * high water mark options. Does not support multi-part messages - in
    * particular, only one part of it is kept in the socket internal queue.
    */
   conflate: boolean
@@ -1041,7 +1041,7 @@ export class Subscriber extends Socket {
    *
    * If set to `true`, a socket shall keep only one message in its
    * inbound/outbound queue: the last message to be received/sent. Ignores any
-   * high water mark options. Does not support multi-part messages – in
+   * high water mark options. Does not support multi-part messages - in
    * particular, only one part of it is kept in the socket internal queue.
    */
   conflate: boolean
@@ -1268,7 +1268,7 @@ export class Dealer extends Socket {
    *
    * If set to `true`, a socket shall keep only one message in its
    * inbound/outbound queue: the last message to be received/sent. Ignores any
-   * high water mark options. Does not support multi-part messages – in
+   * high water mark options. Does not support multi-part messages - in
    * particular, only one part of it is kept in the socket internal queue.
    */
   conflate: boolean
@@ -1398,7 +1398,7 @@ export interface Pull extends Readable {
    *
    * If set to `true`, a socket shall keep only one message in its
    * inbound/outbound queue: the last message to be received/sent. Ignores any
-   * high water mark options. Does not support multi-part messages – in
+   * high water mark options. Does not support multi-part messages - in
    * particular, only one part of it is kept in the socket internal queue.
    */
   conflate: boolean
@@ -1429,7 +1429,7 @@ export interface Push extends Writable {
    *
    * If set to `true`, a socket shall keep only one message in its
    * inbound/outbound queue: the last message to be received/sent. Ignores any
-   * high water mark options. Does not support multi-part messages – in
+   * high water mark options. Does not support multi-part messages - in
    * particular, only one part of it is kept in the socket internal queue.
    */
   conflate: boolean
@@ -1485,11 +1485,11 @@ export class XPublisher extends Socket {
    * ZMQ_XPUB_VERBOSE / ZMQ_XPUB_VERBOSER
    *
    * Whether to pass any duplicate subscription/unsuscription messages.
-   *  * `null` (default) – Only unique subscribe and unsubscribe messages are
+   *  * `null` (default) - Only unique subscribe and unsubscribe messages are
    *    visible to the caller.
-   *  * `"allSubs"` – All subscribe messages (including duplicates) are visible
+   *  * `"allSubs"` - All subscribe messages (including duplicates) are visible
    *    to the caller, but only unique unsubscribe messages are visible.
-   *  * `"allSubsUnsubs"` – All subscribe and unsubscribe messages (including
+   *  * `"allSubsUnsubs"` - All subscribe and unsubscribe messages (including
    *    duplicates) are visible to the caller.
    */
   set verbosity(value: null | "allSubs" | "allSubsUnsubs") {

src/native.ts

@@ -19,13 +19,13 @@ export declare const version: string
  * Unavailable capabilities will be absent or set to `false`.
  *
  * Possible keys include:
- * * `ipc` – Support for the `ipc://` protocol.
- * * `pgm` – Support for the `pgm://` protocol.
- * * `tipc` – Support for the `tipc://` protocol.
- * * `norm` – Support for the `norm://` protocol.
- * * `curve` – Support for the CURVE security mechanism.
- * * `gssapi` – Support for the GSSAPI security mechanism.
- * * `draft` – Wether the library is built with support for DRAFT sockets.
+ * * `ipc` - Support for the `ipc://` protocol.
+ * * `pgm` - Support for the `pgm://` protocol.
+ * * `tipc` - Support for the `tipc://` protocol.
+ * * `norm` - Support for the `norm://` protocol.
+ * * `curve` - Support for the CURVE security mechanism.
+ * * `gssapi` - Support for the GSSAPI security mechanism.
+ * * `draft` - Wether the library is built with support for DRAFT sockets.
  */
 export declare const capability: Partial<{
   ipc: boolean
@@ -65,7 +65,7 @@ export declare function curveKeyPair(): {
  * A ØMQ context. Contexts manage the background I/O to send and receive
  * messages of their associated sockets.
  *
- * It is usually not necessary to instantiate a new context – the global
+ * It is usually not necessary to instantiate a new context - the global
  * {@link context} is used for new sockets by default. The global context is the
  * only context that is shared between threads (when using
  * [worker_threads](https://nodejs.org/api/worker_threads.html)). Custom
@@ -176,76 +176,76 @@ type EventFor<T extends string, D = {}> = Expand<{type: T} & D>
  * errors) that correspond to a specific operation are namespaced with a colon
  * `:`, e.g. `bind:error` or `connect:retry`.
  *
- * * **accept** – ZMQ_EVENT_ACCEPTED The socket has accepted a connection from a
+ * * **accept** - ZMQ_EVENT_ACCEPTED The socket has accepted a connection from a
  *   remote peer.
  *
- * * **accept:error** – ZMQ_EVENT_ACCEPT_FAILED The socket has rejected a
+ * * **accept:error** - ZMQ_EVENT_ACCEPT_FAILED The socket has rejected a
  *   connection from a remote peer.
  *
  *   The following additional details will be included with this event:
  *
- *   * `error` – An error object that describes the specific error
+ *   * `error` - An error object that describes the specific error
  *     that occurred.
  *
- * * **bind** – ZMQ_EVENT_LISTENING The socket was successfully bound to a
+ * * **bind** - ZMQ_EVENT_LISTENING The socket was successfully bound to a
  *   network interface.
  *
- * * **bind:error** – ZMQ_EVENT_BIND_FAILED The socket could not bind to a given
+ * * **bind:error** - ZMQ_EVENT_BIND_FAILED The socket could not bind to a given
  *   interface.
  *
  *   The following additional details will be included with this event:
  *
- *   * `error` – An error object that describes the specific error
+ *   * `error` - An error object that describes the specific error
  *     that occurred.
  *
- * * **connect** – ZMQ_EVENT_CONNECTED The socket has successfully connected to
+ * * **connect** - ZMQ_EVENT_CONNECTED The socket has successfully connected to
  *   a remote peer.
  *
- * * **connect:delay** – ZMQ_EVENT_CONNECT_DELAYED A connect request on the
+ * * **connect:delay** - ZMQ_EVENT_CONNECT_DELAYED A connect request on the
  *   socket is pending.
  *
- * * **connect:retry** – ZMQ_EVENT_CONNECT_RETRIED A connection attempt is being
+ * * **connect:retry** - ZMQ_EVENT_CONNECT_RETRIED A connection attempt is being
  *   handled by reconnect timer. Note that the reconnect interval is
  *   recalculated at each retry.
  *
  *   The following additional details will be included with this event:
  *
- *   * `interval` – The current reconnect interval.
+ *   * `interval` - The current reconnect interval.
  *
- * * **close** – ZMQ_EVENT_CLOSED The socket was closed.
+ * * **close** - ZMQ_EVENT_CLOSED The socket was closed.
  *
- * * **close:error** – ZMQ_EVENT_CLOSE_FAILED The socket close failed. Note that
+ * * **close:error** - ZMQ_EVENT_CLOSE_FAILED The socket close failed. Note that
  *   this event occurs **only on IPC** transports..
  *
  *   The following additional details will be included with this event:
  *
- *   * `error` – An error object that describes the specific error
+ *   * `error` - An error object that describes the specific error
  *     that occurred.
  *
- * * **disconnect** – ZMQ_EVENT_DISCONNECTED The socket was disconnected
+ * * **disconnect** - ZMQ_EVENT_DISCONNECTED The socket was disconnected
  *   unexpectedly.
  *
- * * **handshake** – ZMQ_EVENT_HANDSHAKE_SUCCEEDED The ZMTP security mechanism
+ * * **handshake** - ZMQ_EVENT_HANDSHAKE_SUCCEEDED The ZMTP security mechanism
  *   handshake succeeded. NOTE: This event may still be in DRAFT statea and not
  *   yet available in stable releases.
  *
- * * **handshake:error:protocol** – ZMQ_EVENT_HANDSHAKE_FAILED_PROTOCOL The ZMTP
+ * * **handshake:error:protocol** - ZMQ_EVENT_HANDSHAKE_FAILED_PROTOCOL The ZMTP
  *   security mechanism handshake failed due to some mechanism protocol error,
  *   either between the ZMTP mechanism peers, or between the mechanism server
  *   and the ZAP handler. This indicates a configuration or implementation error
  *   in either peer resp. the ZAP handler. NOTE: This event may still be in
  *   DRAFT state and not yet available in stable releases.
  *
- * * **handshake:error:auth** – ZMQ_EVENT_HANDSHAKE_FAILED_AUTH The ZMTP
+ * * **handshake:error:auth** - ZMQ_EVENT_HANDSHAKE_FAILED_AUTH The ZMTP
  *   security mechanism handshake failed due to an authentication failure. NOTE:
  *   This event may still be in DRAFT state and not yet available in stable
  *   releases.
  *
- * * **handshake:error:other** – ZMQ_EVENT_HANDSHAKE_FAILED_NO_DETAIL
+ * * **handshake:error:other** - ZMQ_EVENT_HANDSHAKE_FAILED_NO_DETAIL
  *   Unspecified error during handshake. NOTE: This event may still be in DRAFT
  *   state and not yet available in stable releases.
  *
- * * **end** – ZMQ_EVENT_MONITOR_STOPPED Monitoring on this socket ended.
+ * * **end** - ZMQ_EVENT_MONITOR_STOPPED Monitoring on this socket ended.
  *
  * * **unknown** An event was generated by ZeroMQ that the Node.js library could
  *   not interpret. Please submit a pull request for new event types if they are