Particular
diff --git a/‎README.md
+3-65 b/‎README.md
+3-65
diff --git a/‎architecture/azure/data-stores.md
+4-2 b/‎architecture/azure/data-stores.md
+4-2
diff --git a/‎architecture/azure/index.md
+2-1 b/‎architecture/azure/index.md
+2-1
diff --git a/‎architecture/consistency.md
+9-8 b/‎architecture/consistency.md
+9-8
diff --git a/‎architecture/recoverability.md
+14-15 b/‎architecture/recoverability.md
+14-15
diff --git a/‎architecture/workflows.md
+4-2 b/‎architecture/workflows.md
+4-2
diff --git a/‎monitoring/custom-checks/install-plugin.md
+4-2 b/‎monitoring/custom-checks/install-plugin.md
+4-2
diff --git a/‎monitoring/custom-checks/writing-custom-checks.md
+2-1 b/‎monitoring/custom-checks/writing-custom-checks.md
+2-1
diff --git a/‎monitoring/heartbeats/expired-heartbeats.md
+2-1 b/‎monitoring/heartbeats/expired-heartbeats.md
+2-1
diff --git a/‎monitoring/heartbeats/in-servicepulse.md
+4-2 b/‎monitoring/heartbeats/in-servicepulse.md
+4-2
diff --git a/‎monitoring/heartbeats/index.md
+2-1 b/‎monitoring/heartbeats/index.md
+2-1
@@ -36,7 +36,8 @@ The repository contains a devcontainer that has all the necessary tools to devel
 
 For more information about devcontainers visit the [official documentation](https://code.visualstudio.com/docs/devcontainers/containers). Install the pre-requirements mentioned in the [getting started guide](https://code.visualstudio.com/docs/devcontainers/containers#_getting-started) and open the repository in Code (`> code .`).
 
-Note: The docstool is currently started in the foreground. While it is possible to run it in the background with `&` or the parallel execution feature of devcontainer it might be more cumbersome to inspect the log output of the tool. The downside of starting in the foreground is that Code will continuously show a spinner with "Configuring container".
+> [!NOTE]
+> The docstool is currently started in the foreground. While it is possible to run it in the background with `&` or the parallel execution feature of devcontainer it might be more cumbersome to inspect the log output of the tool. The downside of starting in the foreground is that Code will continuously show a spinner with "Configuring container".
 
 ### Building samples and snippets
 
@@ -932,70 +933,7 @@ The integrity tests include:
 
 ### Alerts
 
-Sometimes it is necessary to draw attention to items you want to call out in a document.
-
-This is achieved through [bootstrap alerts](https://getbootstrap.com/components/#alerts).
-
-There are several keys each of which map to a different colored alert
-
-| Key                 | Color  |
-|---------------------|--------|
-| `SUCCESS`           | green  |
-| `NOTE` or `INFO`    | blue   |
-| `WARNING` or `WARN` | yellow |
-| `DANGER`            | red    |
-
-Keys can be used in two manners
-
-#### Single-line
-
-This can be done with the following syntax
-
-```markdown
-KEY: the note text.
-```
-
-For example, this
-
-```markdown
-NOTE: Some sample note text.
-```
-
-will be rendered as
-
-```html
-<p class="alert alert-info">
-    Some sample note text.
-</p>
-```
-
-#### Multi-line
-
-Sometimes it is necessary to group markdown elements inside a note. This can be done with the following syntax
-
-```markdown
-{{KEY:
-Inner markdown elements
-}}
-```
-
-For example, this
-
-```markdown
-{{NOTE:
-* Point one
-* Point Two
-}}
-```
-
-will be rendered as
-
-```html
-<p class="alert alert-info">
-* Point One
-* Point Two
-</p>
-```
+[GitHub style alert boxes](https://github.com/orgs/community/discussions/16925) are supported and rendered as [bootstrap alerts](https://getbootstrap.com/docs/5.3/components/alerts/).
 
 ### Headings
 
 
@@ -27,7 +27,8 @@ Azure offers [several data stores](https://learn.microsoft.com/en-us/azure/archi
 
 [**Try the NServiceBus Cosmos DB sample →**](/samples/cosmosdb/simple/)
 
-Note: Cosmos DB offers _serverless_ and _provisioned throughput_ pricing models. When using _provisioned throughput_, Cosmos DB rejects further requests after the reserved Request Units are used. The [Cosmos DB pricing model documentation](https://learn.microsoft.com/en-us/azure/cosmos-db/how-pricing-works) has further information.
+> [!NOTE]
+> Cosmos DB offers _serverless_ and _provisioned throughput_ pricing models. When using _provisioned throughput_, Cosmos DB rejects further requests after the reserved Request Units are used. The [Cosmos DB pricing model documentation](https://learn.microsoft.com/en-us/azure/cosmos-db/how-pricing-works) has further information.
 
 ## Azure Table Storage
 
@@ -48,7 +49,8 @@ Note: Cosmos DB offers _serverless_ and _provisioned throughput_ pricing models.
 
 [**Try the NServiceBus Azure Table Storage sample →**](/samples/azure/azure-table/simple/)
 
-Note: Applications built for Table Storage are compatible with Cosmos DB. See [this table](https://learn.microsoft.com/en-us/azure/cosmos-db/table/support) for a more in-depth comparison.
+> [!NOTE]
+> Applications built for Table Storage are compatible with Cosmos DB. See [this table](https://learn.microsoft.com/en-us/azure/cosmos-db/table/support) for a more in-depth comparison.
 
 ## Azure SQL Database
 
 
@@ -27,7 +27,8 @@ The Particular Service Platform supports the Azure services required to build di
 
 Additional technology choices are described in [Technology choices for Azure solutions](https://learn.microsoft.com/en-us/azure/architecture/guide/technology-choices/technology-choices-overview).
 
-Note: Azure services do not support distributed transactions. Read the [consistency guidance](/architecture/consistency.md) for more information about managing consistency in systems without distributed transactions.
+> [!NOTE]
+> Azure services do not support distributed transactions. Read the [consistency guidance](/architecture/consistency.md) for more information about managing consistency in systems without distributed transactions.
 
 ## Application architecture
 
 
@@ -44,12 +44,11 @@ Databases and queueing technologies may support atomic transactions for a single
 
 Distributed transactions span multiple technologies, such as a database and a message queue. On Windows, the [Distributed Transaction Coordinator (DTC)](https://en.wikipedia.org/wiki/Microsoft_Distributed_Transaction_Coordinator) coordinates distributed transactions across multiple compatible participants using a [two-phase commit protocol](https://en.wikipedia.org/wiki/Two-phase_commit_protocol). Each participant must explicitly support the two-phase commit protocol.
 
-{{WARN:
-While traditional on-premises focused services like MSMQ or Microsoft SQL Server support DTC transactions, managed cloud services do not, and require other strategies for achieving consistency between resources such as:
-
-* The [outbox pattern](#transactions-outbox-pattern), which uses database capabilities to achieve atomic consistency for data and message operations
-* [Stateful workflows](workflows.md), which supervise the successful completion of all involved resources and manage compensating actions to achieve eventual consistency.
-}}
+> [!WARNING]
+> While traditional on-premises focused services like MSMQ or Microsoft SQL Server support DTC transactions, managed cloud services do not, and require other > strategies for achieving consistency between resources such as:
+>
+> * The [outbox pattern](#transactions-outbox-pattern), which uses database capabilities to achieve atomic consistency for data and message operations
+> * [Stateful workflows](workflows.md), which supervise the successful completion of all involved resources and manage compensating actions to achieve eventual consistency.
 
 ### Outbox pattern
 
@@ -59,7 +58,8 @@ The outbox pattern is implemented by storing outgoing messages in the same datab
 
 The nature of the outbox pattern may cause outgoing messages to be dispatched multiple times, which requires [idempotency](#idempotency) in receivers.
 
-Note: Implementing the outbox pattern is very risky and error-prone. Small mistakes can lead to unintended behavior and message or data loss. The [NServiceBus outbox feature](/nservicebus/outbox/) implements the outbox pattern, including built-in message deduplication when receiving messages, and is thoroughly tested and well-documented.
+> [!NOTE]
+> Implementing the outbox pattern is very risky and error-prone. Small mistakes can lead to unintended behavior and message or data loss. The [NServiceBus outbox feature](/nservicebus/outbox/) implements the outbox pattern, including built-in message deduplication when receiving messages, and is thoroughly tested and well-documented.
 
 ## Idempotency
 
@@ -81,7 +81,8 @@ Message deduplication is the easiest way to detect if a message has been process
 
 One advantage of this approach is its simplicity. However, it has downsides. Every message needs to be stored and searched for, which can reduce message throughput. Deduplication storage is not infinite, limiting the deduplication guarantees of this approach to the provided storage capacity. Identifiers for deduplication typically operate on technical IDs (e.g. message ID), which means this approach does not work for duplicate message _content_.
 
-Note: Implementing message deduplication is risky and error-prone. Small mistakes can lead to unintended behavior or message loss. The [NServiceBus Outbox feature](/nservicebus/outbox/) implements message deduplication and is thoroughly tested and well-documented.
+> [!NOTE]
+> Implementing message deduplication is risky and error-prone. Small mistakes can lead to unintended behavior or message loss. The [NServiceBus Outbox feature](/nservicebus/outbox/) implements message deduplication and is thoroughly tested and well-documented.
 
 ### Side effect checks
 
 
@@ -16,14 +16,14 @@ Transient failures are temporary and are not caused by errors in business logic.
 
 [**Blog: I caught an exception. Now what? →**](https://particular.net/blog/but-all-my-errors-are-severe)
 
-Note: The nature of retries implies that messages might be processed in a different order under some circumstances.
+> [!NOTE]
+> The nature of retries implies that messages might be processed in a different order under some circumstances.
 
-{{Note:
-The Particular Platform simplifies the handling of transient errors:
-
-- NServiceBus has [built-in support for immediate and delayed retries](/nservicebus/recoverability/) for all supported messaging technologies. The automated retries behavior is highly customizable.
-- ServicePulse shows [real-time metrics monitoring retries](/servicepulse/#real-time-monitoring) occuring in the system.
-}}
+> [!NOTE]
+> The Particular Platform simplifies the handling of transient errors:
+>
+> - NServiceBus has [built-in support for immediate and delayed retries](/nservicebus/recoverability/) for all supported messaging technologies. The automated > retries behavior is highly customizable.
+> - ServicePulse shows [real-time metrics monitoring retries](/servicepulse/#real-time-monitoring) occuring in the system.
 
 
 ## Persistent errors
@@ -36,14 +36,13 @@ Once the root cause of a persistent error has been resolved, messages can be mov
 
 [**Video: An exception occurred... Try again →**](https://www.youtube.com/watch?v=gSQxtgw1Qz4)
 
-{{Note:
-The Particular Platform simplifies the handling of persistent errors:
-
-- NServiceBus automatically forwards messages exceeding the configured number of automated retries to the [error queue](/nservicebus/recoverability/configure-error-handling.md).
-- ServiceControl can send [email notifications](/servicepulse/health-check-notifications.md) for dead-lettered messages.
-- Messages moved to the error queue are [enhanced with additional metadata](/servicepulse/intro-failed-messages.md#failed-messages-page-message-details-page) to help with root cause detection.
-- Both [ServiceInsight](/serviceinsight/managing-errors-and-retries.md) and [ServicePulse](/servicepulse/intro-failed-messages.md) offer monitoring and inspection of failed messages and advanced retry functionality.
-}}
+> [!NOTE]
+> The Particular Platform simplifies the handling of persistent errors:
+>
+> - NServiceBus automatically forwards messages exceeding the configured number of automated retries to the [error queue](/nservicebus/recoverability/configure-error-handling.md).
+> - ServiceControl can send [email notifications](/servicepulse/health-check-notifications.md) for dead-lettered messages.
+> - Messages moved to the error queue are [enhanced with additional metadata](/servicepulse/intro-failed-messages.md#failed-messages-page-message-details-page) to help with root cause detection.
+> - Both [ServiceInsight](/serviceinsight/managing-errors-and-retries.md) and [ServicePulse](/servicepulse/intro-failed-messages.md) offer monitoring and inspection of failed messages and advanced retry functionality.
 
 ## Best practices
 
 
@@ -7,7 +7,8 @@ callsToAction: ['solution-architect']
 
 Business processes typically involve various distributed components that need to be invoked in a coordinated manner. The Particular Service Platform supports both choreography and orchestration of workflows.
 
-Note: Choreography and orchestration are not mutually exclusive. The patterns may be combined at different levels of business workflows.
+> [!NOTE]
+> Choreography and orchestration are not mutually exclusive. The patterns may be combined at different levels of business workflows.
 
 ## Choreography
 
@@ -46,7 +47,8 @@ _An orchestrated workflow implemented as an NServiceBus Saga, visualized by [Ser
 
 [**Tutorial: Introduction to NServiceBus sagas →**](/tutorials/nservicebus-sagas/1-saga-basics/)
 
-Note: NServiceBus sagas focus on providing a convenient and efficient way to manage message-based workflows as described by the [Process Manager pattern](https://www.enterpriseintegrationpatterns.com/patterns/messaging/ProcessManager.html). The [_saga distributed transactions_ pattern](https://learn.microsoft.com/en-us/azure/architecture/reference-architectures/saga/saga) is primarily concerned with managing long-lived transactions and ensuring consistency between multiple operations, especially in the presence of failures. The NServiceBus saga feature can be used to implement the _saga distributed transactions_ pattern.
+> [!NOTE]
+> NServiceBus sagas focus on providing a convenient and efficient way to manage message-based workflows as described by the [Process Manager pattern](https://www.enterpriseintegrationpatterns.com/patterns/messaging/ProcessManager.html). The [_saga distributed transactions_ pattern](https://learn.microsoft.com/en-us/azure/architecture/reference-architectures/saga/saga) is primarily concerned with managing long-lived transactions and ensuring consistency between multiple operations, especially in the presence of failures. The NServiceBus saga feature can be used to implement the _saga distributed transactions_ pattern.
 
 ### Challenges
 
 
@@ -6,13 +6,15 @@ component: CustomChecks
 versions: 'CustomChecks:*'
 ---
 
-NOTE: This plugin can be enabled and configured with the [ServicePlatform Connector plugin](/platform/connecting.md).
+> [!NOTE]
+> This plugin can be enabled and configured with the [ServicePlatform Connector plugin](/platform/connecting.md).
 
 To install the custom checks plugin into an endpoint, reference the [NServiceBus.CustomChecks NuGet package](https://www.nuget.org/packages/NServiceBus.CustomChecks/) and add the following to the endpoint configuration:
 
 snippet: CustomCheckNew_Enable
 
-NOTE: `ServiceControl_Queue` is a placeholder for the actual ServiceControl Instance (Not a ServiceControl Audit instance) input queue. The ServiceControl input queue is equal to the [ServiceControl service name](/servicecontrol/installation.md#servicecontrol-plugins) as configured in the ServiceControl Management Utility.
+> [!NOTE]
+> `ServiceControl_Queue` is a placeholder for the actual ServiceControl Instance (Not a ServiceControl Audit instance) input queue. The ServiceControl input queue is equal to the [ServiceControl service name](/servicecontrol/installation.md#servicecontrol-plugins) as configured in the ServiceControl Management Utility.
 
 It may not make sense to enable the custom checks plugin in all environments. For instance, a development environment may not have a running ServiceControl instance to consume custom check messages. In these cases, enable the plugin conditionally, based on an environment variable or configuration setting.
 
 
@@ -16,4 +16,5 @@ All custom checks are executed when the endpoint starts up. If the optional inte
 
 snippet: PeriodicCheck
 
-NOTE: Custom checks are discovered at runtime using assembly scanning. This means they can also be deployed to endpoints as NuGet packages.
+> [!NOTE]
+> Custom checks are discovered at runtime using assembly scanning. This means they can also be deployed to endpoints as NuGet packages.
@@ -12,7 +12,8 @@ Heartbeat messages have a [time to be received (TTBR)](/nservicebus/messaging/di
 
 Although NServiceBus configures the use of DLQ by default, messages that are defined with TTBR will not be automatically forwarded to the DLQ and will be discarded. Configuration can be specified to [override this behavior](/transports/msmq/dead-letter-queues.md#enabling-dlq-for-messages-with-ttbr) so that these messages can be forwarded to the DLQ.
 
-WARNING: When using NServiceBus Versions 6.1 or below, messages will be forwarded to the DLQ even if TTBR is set on the messages.  To avoid this behavior, DLQ can be disabled by configuring the [MSMQ connection strings](/transports/msmq/connection-strings.md). The heartbeat messages will be forwarded to the DLQ when ServiceControl is either stopped or very busy. In this case, the dead letter queue needs to be monitored and cleaned up.
+> [!WARNING]
+> When using NServiceBus Versions 6.1 or below, messages will be forwarded to the DLQ even if TTBR is set on the messages.  To avoid this behavior, DLQ can be disabled by configuring the [MSMQ connection strings](/transports/msmq/connection-strings.md). The heartbeat messages will be forwarded to the DLQ when ServiceControl is either stopped or very busy. In this case, the dead letter queue needs to be monitored and cleaned up.
 
 ### Azure Service Bus
 
 
@@ -30,12 +30,14 @@ Heartbeat monitoring for endpoint instances can be configured in the configurati
 
 Setting the endpoint to "Off" will prevent it from appearing on the endpoints overview screen and from affecting the dashboard.
 
-NOTE: This is a configuration setting only and the endpoint itself may still be configured to send heartbeat messages.
+> [!NOTE]
+> This is a configuration setting only and the endpoint itself may still be configured to send heartbeat messages.
 
 ## Removing endpoints
 
 When an endpoint has been decommissioned and should no longer be displayed in ServicePulse it can be removed. From the Endpoint Heartbeats screen, click the trash bin icon next to an endpoint's name to remove it from ServicePulse. The trash icon is only visible when displaying endpoint instances. It is not shown when displaying logical endpoints.
 
-NOTE: This feature requires ServicePulse version 1.23 or higher and ServiceControl version 4.4 or higher.
+> [!NOTE]
+> This feature requires ServicePulse version 1.23 or higher and ServiceControl version 4.4 or higher.
 
 ![Remove endpoint](sp-remove-endpoint.png)
@@ -13,7 +13,8 @@ redirects:
 
 The Heartbeat plugin enables endpoint health monitoring by sending regular heartbeat messages from the endpoint to a ServiceControl instance. The ServiceControl instance keeps track of which endpoint instances are sending heartbeats and which ones are not.
 
-NOTE: Even if an endpoint is able to send heartbeat messages, other failures may occur within the endpoint and its host that prevent it from performing as expected. For example, the endpoint may not be able to process incoming messages, or it may be able to send messages to the ServiceControl queue but not to another queue. [Performance metrics](/monitoring/metrics/) can be used to monitor the processing of messages within an endpoint.
+> [!NOTE]
+> Even if an endpoint is able to send heartbeat messages, other failures may occur within the endpoint and its host that prevent it from performing as expected. For example, the endpoint may not be able to process incoming messages, or it may be able to send messages to the ServiceControl queue but not to another queue. [Performance metrics](/monitoring/metrics/) can be used to monitor the processing of messages within an endpoint.
 
 ```mermaid
 graph LR