remove the em-dashes

Author: FreeAndNil

src/site/antora/modules/ROOT/pages/manual/configuration.adoc

@@ -297,7 +297,7 @@ Example usage:
 This attribute may only be used once per assembly.
 
 Using attributes can be a clearer method for defining where the application's configuration will be loaded from.
-However, note that attributes are passive — they only provide information.
+However, note that attributes are passive: they only provide information.
 Therefore, to trigger log4net to read and process the attributes, you must invoke log4net.
 A simple call to `LogManager.GetLogger` will cause the attributes on the calling assembly to be processed.
 
@@ -438,7 +438,7 @@ This tells .NET to ignore the section, as it will be processed by log4net instea
 
 Android does not support `.config` files.
 
-Instead, you can set `AppSettings` values as environment variables for your process — this works only on Android.
+Instead, you can set `AppSettings` values as environment variables for your process: this works only on Android.
 
 You must also load the `log4net` configuration manually, for example by reading it from an XML file at runtime.
 

src/site/antora/modules/ROOT/pages/manual/configuration/appenders.adoc

@@ -128,7 +128,7 @@ This prevents logging events from being passed to ancestor appenders beyond that
 
 [NOTE]
 ====
-If the `Animals` logger has `additivity = false`, then the `Animals.Carnivora` logger will only send its log messages to its own appenders and to `Animals`’ appenders—
+If the `Animals` logger has `additivity = false`, then the `Animals.Carnivora` logger will only send its log messages to its own appenders and to `Animals`’ appenders,
 but not to any appenders higher up in the hierarchy, such as those on the root logger.
 ====
 

src/site/antora/modules/ROOT/pages/manual/configuration/appenders/remotesyslogappender.adoc

@@ -131,7 +131,7 @@ The `RemoteSyslogAppender` uses the UDP protocol to send log messages to the sys
 However, there are size limitations associated with UDP:
 
 * **Message size:** Each log message is limited to **64 KB**, including both the message content and the headers.
-* **Practical size limit:** On many networks, such as Ethernet, the practical limit for message size is typically much lower — around **1500 bytes**.
+* **Practical size limit:** On many networks, such as Ethernet, the practical limit for message size is typically much lower, around **1500 bytes**.
 * **Message truncation:** If a log message exceeds these size limits, it will be **truncated**, which means some of the message content will be lost.
 
 To avoid truncation, ensure that log messages are kept within the size limits of your network setup.

src/site/antora/modules/ROOT/pages/manual/configuration/layouts.adoc

@@ -34,13 +34,13 @@ This section outlines some common concerns shared by most predefined layouts in
 In modern production environments, logs are typically not read from local files by engineers.
 Instead, they are sent to log ingestion systems like Elasticsearch, Google Cloud Logging, or similar platforms for observability, metrics, and monitoring purposes.
 
-To support this, logs must be encoded in a machine-readable format — a practice known as *structured logging*.
+To support this, logs must be encoded in a machine-readable format, a practice known as *structured logging*.
 
 log4net provides support for structured logging through specialized layouts.
 For production use cases, we recommend using either:
 
-* `XmlLayout` — for structured XML output.
-* `JsonLayout` — via the external project https://gitlab.com/gdziadkiewicz/log4net.Ext.Json/-/blob/develop/log4net.Ext.Json/Layout/SerializedLayout.cs[log4net.Ext.Json].
+* `XmlLayout` - for structured XML output.
+* `JsonLayout` - via the external project https://gitlab.com/gdziadkiewicz/log4net.Ext.Json/-/blob/develop/log4net.Ext.Json/Layout/SerializedLayout.cs[log4net.Ext.Json].
 
 These layouts help ensure your logs are compatible with log aggregation and analysis tools.
 
@@ -84,7 +84,7 @@ will yield the output
 The `DynamicPatternLayout` should be used whenever the header or footer needs to include information that may change over time.
 
 Unlike the static `PatternLayout`, which renders headers and footers only once, the `DynamicPatternLayout` re-evaluates its pattern every time it is invoked.
-This makes it possible, for example, to include the current date and time in the header or footer—something not possible with the static layout.
+This makes it possible, for example, to include the current date and time in the header or footer, something not possible with the static layout.
 
 The following example shows how to configure the `DynamicPatternLayout`:
 

src/site/antora/modules/ROOT/pages/manual/faq.adoc

@@ -230,7 +230,7 @@ log.Debug("Entry number: " + i + " is " + entry[i]);
 log.Debug($"Entry number: {i} is {entry[i]}");
 ----
 
-incurs the cost of constructing the message, including converting values to strings and concatenating them—regardless of whether the message is logged.
+incurs the cost of constructing the message, including converting values to strings and concatenating them, regardless of whether the message is logged.
 
 A more efficient alternative is to use log.DebugFormat etc., which formats the message only if the log level is enabled:
 
@@ -252,7 +252,7 @@ if (log.IsDebugEnabled)
 [#locking-models]
 === How do I get multiple process to log to the same file?
 
-Before proceeding, consider if it's absolutely necessary to have multiple processes log to the same file — it's often better to avoid this.
+Before proceeding, consider if it's absolutely necessary to have multiple processes log to the same file: it's often better to avoid this.
 
 FileAppender offers different locking models, but they have limitations:
 

src/site/antora/modules/ROOT/pages/manual/introduction.adoc

@@ -328,7 +328,7 @@ log4net can render the content of log messages using custom logic defined by the
 For example, if you often log `Orange` objects, you can register an `OrangeRenderer` to format them consistently in logs.
 
 Renderers follow the class hierarchy.
-If you register a `FruitRenderer`, it will be used for all `Fruit` types—including `Orange`—unless a more specific `OrangeRenderer` is also registered.
+If you register a `FruitRenderer`, it will be used for all `Fruit` types (including `Orange`) unless a more specific `OrangeRenderer` is also registered.
 
 Renderers must implement the `log4net.ObjectRenderer.IObjectRenderer` interface.