Merge pull request #33 from tgiachi/develop

docs: remove em dashes across docs and package READMEs

Author: tgiachi

docs/articles/concepts/abstractions-first.md

@@ -4,18 +4,18 @@ SquidStd is built abstractions-first: code depends on contracts, and concrete ba
 
 ## Contract package plus provider packages
 
-Each capability is a contract package paired with one or more provider packages. The contract package — `*.Abstractions` — defines the interfaces and DTOs. Provider packages implement them. Your application references the abstraction and depends on the provider only in the host project. See the [architecture](architecture.md) overview for how this shapes the package graph.
+Each capability is a contract package paired with one or more provider packages. The contract package - `*.Abstractions` - defines the interfaces and DTOs. Provider packages implement them. Your application references the abstraction and depends on the provider only in the host project. See the [architecture](architecture.md) overview for how this shapes the package graph.
 
 ## In-memory for tests, external for prod
 
 Most capabilities ship an in-memory provider for tests and an external-backend provider for production:
 
-- **Messaging** — in-memory, or `SquidStd.Messaging.RabbitMq` / `SquidStd.Messaging.Sqs`.
-- **Caching** — in-memory, or `SquidStd.Caching.Redis`.
-- **Storage** — file-backed, or `SquidStd.Storage.S3` (S3 and MinIO).
+- **Messaging** - in-memory, or `SquidStd.Messaging.RabbitMq` / `SquidStd.Messaging.Sqs`.
+- **Caching** - in-memory, or `SquidStd.Caching.Redis`.
+- **Storage** - file-backed, or `SquidStd.Storage.S3` (S3 and MinIO).
 
 Tests run fast and deterministically against the in-memory provider; production swaps in the external backend.
 
 ## Swapping providers without touching call sites
 
-Because call sites depend only on the contract, switching backends is a registration change in the host — `container.AddInMemoryMessaging()` versus `container.AddRabbitMqMessaging(...)` — with no edits to the code that publishes or consumes messages. See [dependency injection](dependency-injection.md) for the registration pattern that makes the swap a one-line change.
+Because call sites depend only on the contract, switching backends is a registration change in the host - `container.AddInMemoryMessaging()` versus `container.AddRabbitMqMessaging(...)` - with no edits to the code that publishes or consumes messages. See [dependency injection](dependency-injection.md) for the registration pattern that makes the swap a one-line change.

docs/articles/concepts/architecture.md

@@ -10,10 +10,10 @@ Every capability is split in two: an `*.Abstractions` package that holds the con
 
 The dependency flow runs in one direction:
 
-- **Core** (`SquidStd.Core`) — primitives, options, and the building blocks everything else sits on.
-- **Abstractions** — per-capability contract packages.
-- **Providers** — concrete implementations of those contracts.
-- **Host** — `SquidStdBootstrap` composes services and runs them.
+- **Core** (`SquidStd.Core`) - primitives, options, and the building blocks everything else sits on.
+- **Abstractions** - per-capability contract packages.
+- **Providers** - concrete implementations of those contracts.
+- **Host** - `SquidStdBootstrap` composes services and runs them.
 
 Higher layers depend on lower ones, never the reverse.
 
@@ -30,5 +30,5 @@ graph TD
 
 ## Next
 
-- [Bootstrap lifecycle](bootstrap-lifecycle.md) — how the host starts and stops services.
-- [Abstractions first](abstractions-first.md) — the contract-plus-provider pattern in depth.
+- [Bootstrap lifecycle](bootstrap-lifecycle.md) - how the host starts and stops services.
+- [Abstractions first](abstractions-first.md) - the contract-plus-provider pattern in depth.

docs/articles/concepts/messaging-models.md

@@ -8,7 +8,7 @@ The Event Bus (`IEventBus`) is a stateless broadcast. Publishers call `PublishAs
 
 ## Command Dispatcher
 
-The Command Dispatcher is a stateless request routed to a single handler that returns a result. Unlike the Event Bus there is exactly one handler per command, and the caller awaits its result. Use it for request/response work — validating input, performing an operation, returning an outcome — where ownership of the action is unambiguous.
+The Command Dispatcher is a stateless request routed to a single handler that returns a result. Unlike the Event Bus there is exactly one handler per command, and the caller awaits its result. Use it for request/response work - validating input, performing an operation, returning an outcome - where ownership of the action is unambiguous.
 
 ## Actors
 

docs/articles/felix.md

@@ -1,7 +1,7 @@
 # Felix Network
 
 **[Felix Network](https://github.com/tgiachi/SquidStd-Felix)** is a standalone companion library to
-SquidStd: secure, cross-platform **binary mesh networking** for .NET — and for a constrained C
+SquidStd: secure, cross-platform **binary mesh networking** for .NET - and for a constrained C
 target such as the ESP32. It lives in its own repository and ships its own NuGet packages under the
 `SquidStd.Felix.*` prefix.
 
@@ -12,15 +12,15 @@ nodes over **ENet** (reliable UDP), behind a small **portable binary frame** tha
 can speak byte-for-byte. On top of that secure node it adds an optional self-forming **mesh** layer
 (seed discovery + gossip of the peer list with auto-connect).
 
-- **Secure node** — ENet transport, the portable frame (its header is authenticated as AES-GCM
+- **Secure node** - ENet transport, the portable frame (its header is authenticated as AES-GCM
   additional data), best-effort DEFLATE, and a raw `(type, bytes)` API.
-- **Typed layer** — optional `Send<T>` / `On<T>` over MemoryPack with a `[FelixMessage(id)]`
+- **Typed layer** - optional `Send<T>` / `On<T>` over MemoryPack with a `[FelixMessage(id)]`
   attribute mapping message types to wire ids.
-- **Mesh** — fully-connected, self-healing peer discovery via seeds and portable gossip.
-- **Pluggable transport** — the encrypted frame is transport-agnostic; `ITransport` decouples the
+- **Mesh** - fully-connected, self-healing peer discovery via seeds and portable gossip.
+- **Pluggable transport** - the encrypted frame is transport-agnostic; `ITransport` decouples the
   node from the link (ENet ships; a serial/UART transport carries Felix over a reliable serial or
   Bluetooth RFCOMM stream without WiFi).
-- **Portable** — the wire format is documented for non-.NET targets, with a host-testable C core
+- **Portable** - the wire format is documented for non-.NET targets, with a host-testable C core
   (`felix-c`) and ESP32 (ESP-IDF) examples proving byte-for-byte C↔.NET parity.
 
 ## Packages
@@ -84,7 +84,7 @@ mesh.Broadcast(type: 7, "hi mesh"u8.ToArray());
 
 The protocol is portable. The Felix repository ships a portable C core (`felix-c`: AES-256-GCM over
 mbedTLS, raw-DEFLATE inflate, the Felix frame, an ENet leaf transport, and a `felix_serial` UART
-module) plus host harnesses — all testable without an ESP32, proving byte-for-byte C↔.NET parity.
+module) plus host harnesses - all testable without an ESP32, proving byte-for-byte C↔.NET parity.
 The same C builds on an ESP32 (ESP-IDF), over ENet/WiFi or over UART / Bluetooth Classic SPP.
 
 ## Learn more

docs/articles/guides/choosing-search-database.md

@@ -20,4 +20,4 @@ bootstrap.ConfigureServices(container => container.RegisterDatabase());
 
 Reach for `AddElasticsearch` when the core requirement is searching text or
 documents by relevance; use `RegisterDatabase` with the FreeSql provider that
-matches your engine for everything relational. They compose — many apps use both.
+matches your engine for everything relational. They compose - many apps use both.

docs/articles/guides/security.md

@@ -39,5 +39,5 @@ hashing credentials, protecting payloads with a key, and storing named secrets.
 ## Recommendation
 
 Use `HashUtils` for credentials, `ISecretProtector` (AES-GCM locally, KMS in the
-cloud) for encrypting blobs, and `ISecretStore` for named secrets — backed by
+cloud) for encrypting blobs, and `ISecretStore` for named secrets - backed by
 files in development and AWS Secrets Manager in production.

docs/articles/health-checks.md

@@ -5,7 +5,7 @@ The health-check aggregator (`IHealthCheckService` in `SquidStd.Core`, implement
 
 - Implement `IHealthCheck` (`Name` + `CheckAsync`) and register it as `IHealthCheck`.
 - `CheckHealthAsync()` runs all checks **in parallel**, each with a per-check timeout and exception
-  isolation — a failing or timed-out check becomes an `Unhealthy` entry without breaking the others.
+  isolation - a failing or timed-out check becomes an `Unhealthy` entry without breaking the others.
 - The overall `HealthReport.Status` is `Unhealthy` if any check is `Unhealthy`, otherwise `Healthy`.
 
 ```csharp

docs/articles/scheduler.md

@@ -5,7 +5,7 @@ standard 5-field cron expressions evaluated in UTC.
 
 - `Schedule(name, cronExpression, handler)` → returns a job id.
 - `Unschedule(jobId)` / `UnscheduleByName(name)`.
-- `Jobs` — a snapshot of registered jobs (`CronJobInfo`).
+- `Jobs` - a snapshot of registered jobs (`CronJobInfo`).
 
 Each job is a one-shot, self-rescheduling timer on the timer wheel: when it fires, the handler is
 dispatched through `IJobSystem`, and the next occurrence is registered. An occurrence is **skipped** if the
@@ -31,7 +31,7 @@ scheduler.Schedule("cleanup", "0 3 * * *", async ct =>
 ## Event loop
 
 For applications that need a tight, frame-driven loop (game servers, simulations, real-time
-processing), `SquidStd.Services.Core` provides `EventLoopService` — a dedicated background thread
+processing), `SquidStd.Services.Core` provides `EventLoopService` - a dedicated background thread
 (`SquidStd-EventLoop`) that, every frame:
 
 1. drains the `IMainThreadDispatcher` (deferred callbacks posted with `Post`), and
@@ -67,7 +67,7 @@ eventLoop:
 ### Event loop vs. timer-wheel pump
 
 Both `EventLoopService` and `TimerWheelPumpService` advance the timer wheel, so they are **mutually
-exclusive** — register exactly one. The exclusivity is structural: both implement the
+exclusive** - register exactly one. The exclusivity is structural: both implement the
 `ITimerWheelDriver` marker, `RegisterEventLoop()` throws if a driver is already registered, and modules
 that need the wheel (the worker manager, the mail poller) auto-register the pump only when no driver is
 present. Use the pump for ordinary apps where a coarse periodic pump is enough; use the event loop when

docs/articles/serialization.md

@@ -2,8 +2,8 @@
 
 SquidStd uses a single serialization abstraction across the framework, defined in `SquidStd.Core`:
 
-- `IDataSerializer` — `ReadOnlyMemory<byte> Serialize<T>(T value)`
-- `IDataDeserializer` — `T Deserialize<T>(ReadOnlyMemory<byte> data)`
+- `IDataSerializer` - `ReadOnlyMemory<byte> Serialize<T>(T value)`
+- `IDataDeserializer` - `T Deserialize<T>(ReadOnlyMemory<byte> data)`
 
 The default implementation, `JsonDataSerializer`, uses `System.Text.Json` Web defaults and implements
 both interfaces. It is registered by `RegisterCoreServices()` (via `RegisterDataSerializer()`), so both

docs/index.md

@@ -8,19 +8,19 @@ _layout: landing
 
 # SquidStd
 
-A batteries-included, modular standard library for .NET 10 — distilled from years of building
+A batteries-included, modular standard library for .NET 10 - distilled from years of building
 real-world server software. Each capability ships behind a small contract with an in-memory
 implementation for tests and a production backend, published as a focused NuGet package.
 
 Security & crypto, configuration, persistence, messaging, caching, storage, a virtual filesystem,
-search, mail, workers, actors, telemetry, scripting — take only what you need.
+search, mail, workers, actors, telemetry, scripting - take only what you need.
 
 ## Start here
 
-- **[Tutorials](tutorials/index.md)** — learn by building: bootstrap, caching, messaging, workers,
+- **[Tutorials](tutorials/index.md)** - learn by building: bootstrap, caching, messaging, workers,
   crypto, persistence, and more.
-- **[Guides](articles/guides/configuration.md)** — task-focused how-to and "which provider" decision guides.
-- **[Concepts](articles/concepts/architecture.md)** — the architecture and the ideas behind it.
-- **[Packages](articles/getting-started.md)** — per-package reference.
-- **[API reference](api/index.md)** — full type/member documentation.
-- **[Felix Network](articles/felix.md)** — companion secure binary mesh-networking library (.NET + C/ESP32).
+- **[Guides](articles/guides/configuration.md)** - task-focused how-to and "which provider" decision guides.
+- **[Concepts](articles/concepts/architecture.md)** - the architecture and the ideas behind it.
+- **[Packages](articles/getting-started.md)** - per-package reference.
+- **[API reference](api/index.md)** - full type/member documentation.
+- **[Felix Network](articles/felix.md)** - companion secure binary mesh-networking library (.NET + C/ESP32).