Merge pull request #8144 from Particular/docs-batch-2026-03-20

dvdstelt · web-flow · commit ca6bf43b186c · 2026-03-23T11:46:38.000+01:00
diff --git a/nservicebus/gateway/sql/index.md b/nservicebus/gateway/sql/index.md
@@ -2,7 +2,7 @@
 title: SQL Gateway Storage
 summary: SQL deduplication storage for the gateway component
 component: GatewaySql
-reviewed: 2024-06-19
+reviewed: 2026-03-20
 related:
  - samples/gateway
 ---
diff --git a/nservicebus/hosting/azure-functions-service-bus/custom-triggers.md b/nservicebus/hosting/azure-functions-service-bus/custom-triggers.md
@@ -4,7 +4,7 @@ component: ASBFunctionsWorker
 summary: How to write custom triggers to call NServiceBus from Azure Functions
 related:
  - nservicebus/hosting/azure-functions-service-bus
-reviewed: 2024-06-17
+reviewed: 2026-03-20
 ---
 
 partial: content
diff --git a/nservicebus/scaling.md b/nservicebus/scaling.md
@@ -4,7 +4,7 @@ summary: NServiceBus provides several options to scale out a system
 redirects:
  - transports/scale-out
  - nservicebus/architecture/scaling
-reviewed: 2024-06-17
+reviewed: 2026-03-20
 ---
 
 There are several reasons to scale out [logical endpoints](/nservicebus/endpoints/), such as to achieve higher message throughput, or to provide high availability.
@@ -15,7 +15,7 @@ If message throughput is an issue, the first method to consider is splitting up
 
 One message type might take considerably longer to process than other message types. The faster processing messages might suffer in throughput because of the slower processing messages. A good way to monitor and detect this is by using [ServicePulse's monitoring capabilities](/monitoring/metrics/in-servicepulse.md).
 
-Separating slower messages from faster messages leads to higher throughput for the faster messages. For this reason, it can be beneficial to seperate different message types and their corresponding handlers into different logical endpoints.
+Separating slower messages from faster messages leads to higher throughput for the faster messages. For this reason, it can be beneficial to separate different message types and their corresponding handlers into different logical endpoints.
 
 ## Scaling out to multiple nodes
 
diff --git a/persistence/sql/postgresql-combining-persistence-with-transport.md b/persistence/sql/postgresql-combining-persistence-with-transport.md
@@ -1,7 +1,7 @@
 ---
 title: Combining PostgreSQL Persistence and Transport
 component: SqlPersistence
-reviewed: 2024-06-14
+reviewed: 2026-03-20
 related:
   - persistence/sql/dialect-postgresql
   - transports/postgresql
diff --git a/persistence/sql/sqlserver-combining-persistence-wth-transport.md b/persistence/sql/sqlserver-combining-persistence-wth-transport.md
@@ -1,7 +1,7 @@
 ---
 title: Combining MS SQL Server Persistence and Transport
 component: SqlPersistence
-reviewed: 2024-06-10
+reviewed: 2026-03-20
 related:
   - persistence/sql/dialect-mysql
   - transports/sql
@@ -31,7 +31,7 @@ SendsAtomicWithReceive | SQL Transport uses isolated transaction for send and re
 ReceiveOnly | SQL Transport uses isolated transaction for receive | Transport DB
 None | No transactions | Persistence DB
 
-<sup>1</sup> - Requires .NET Framework, or .NET 8 [`ImplicitDistributedTransactions`](https://learn.microsoft.com/en-us/dotnet/api/system.transactions.transactionmanager.implicitdistributedtransactions?view=net-8.0) set to `true`.
+<sup>1</sup> - Requires .NET Framework, or .NET 8+ [`ImplicitDistributedTransactions`](https://learn.microsoft.com/en-us/dotnet/api/system.transactions.transactionmanager.implicitdistributedtransactions) set to `true`.
 
 #### Explicitly opting out of connection sharing when not using the Outbox
 
diff --git a/samples/msmq/persistence/sample.md b/samples/msmq/persistence/sample.md
@@ -1,6 +1,6 @@
 ---
 title: MSMQ Subscription Persistence usage
-reviewed: 2024-06-18
+reviewed: 2026-03-20
 component: MsmqPersistence
 related:
 - persistence/msmq
diff --git a/samples/pipeline/unit-of-work/sample.md b/samples/pipeline/unit-of-work/sample.md
@@ -1,7 +1,7 @@
 ---
 title: Unit of work using custom pipeline behavior
 summary: How to use IoC and a pipeline behavior to create a custom unit of work implementation.
-reviewed: 2024-06-10
+reviewed: 2026-03-20
 component: Core
 related:
  - nservicebus/pipeline
diff --git a/servicecontrol/ravendb/containers.md b/servicecontrol/ravendb/containers.md
@@ -1,6 +1,6 @@
 ---
 title: Managing ServiceControl RavenDB instances via Containers
-reviewed: 2024-06-11
+reviewed: 2026-03-20
 component: ServiceControl
 versions: '[5,)'
 redirects:
diff --git a/servicecontrol/sequence-contains-no-matching-element.md b/servicecontrol/sequence-contains-no-matching-element.md
@@ -1,7 +1,7 @@
 ---
 title: "InvalidOperationException: Sequence contains no matching element"
 summary: "ServiceControl Management Utility shows System.InvalidOperationException: Sequence contains no matching element"
-reviewed: 2024-06-06
+reviewed: 2026-03-20
 ---
 
 ## Symptoms
diff --git a/servicecontrol/servicecontrol-instances/deployment/scmu.md b/servicecontrol/servicecontrol-instances/deployment/scmu.md
@@ -1,7 +1,7 @@
 ---
 title: Deploying Error instances using ServiceControl Management
 summary: A guide to using ServiceControl Management Utility to set up ServiceControl instances. Information about installing and upgrading ServiceControl instances.
-reviewed: 2024-06-14
+reviewed: 2026-03-20
 component: ServiceControl
 related:
  - servicecontrol/servicecontrol-instances/hardware
diff --git a/transports/msmq/delayed-delivery.md b/transports/msmq/delayed-delivery.md
@@ -1,7 +1,7 @@
 ---
 title: MSMQ transport delayed delivery
 summary: Explains how delayed delivery works in the MSMQ transport
-reviewed: 2024-05-30
+reviewed: 2026-03-20
 component: MsmqTransport
 ---
 
diff --git a/transports/msmq/delayed-delivery_content_msmqtransport_[2,).partial.md b/transports/msmq/delayed-delivery_content_msmqtransport_[2,).partial.md
@@ -1,4 +1,4 @@
-Because MSMQ lacks a mechanism for sending delayed messages, the MSMQ transport uses an external store for delayed messages. Messages that are to be delivered later (e.g. [saga timeouts](/nservicebus/sagas/timeouts.md) or [delayed retries](/nservicebus/recoverability/configure-delayed-retries.md)) are persisted in the delayed message store until they are due. When a message is due, it is retreived from the store and dispatched to its destination.
+Because MSMQ lacks a mechanism for sending delayed messages, the MSMQ transport uses an external store for delayed messages. Messages that are to be delivered later (e.g. [saga timeouts](/nservicebus/sagas/timeouts.md) or [delayed retries](/nservicebus/recoverability/configure-delayed-retries.md)) are persisted in the delayed message store until they are due. When a message is due, it is retrieved from the store and dispatched to its destination.
 
 The MSMQ transport requires explicit configuration to enable delayed message delivery. For example:
 
@@ -66,7 +66,7 @@ In `TransactionScope` [transaction mode](/transports/transactions.md), the delay
 
 In lower transaction modes the dispatch behavior is **at least once**. `FetchNextDueTimeout` and `Remove` are executed in the same `TransactionScope` but sending messages to their destination queues is executed in a separate (inner) transport scope. If `Remove` fails, the message will be sent to the destination queue multiple times and the destination endpoint must handle the duplicates, using either the [outbox feature](/nservicebus/outbox/) or a custom de-duplication mechanism.
 
-The built-in SQL Server delayed message store takes a pessimistic lock on the delayed message row in the `FetchNextDueTimeout` operation to prevent other physical instances of the same logical endpoint from delivering the same delayed message. A custom delayed message store must also take some kind of lock to prevent this from happening. For example, a delayed message store using Azure Blog Storage may take a lease lock.
+The built-in SQL Server delayed message store takes a pessimistic lock on the delayed message row in the `FetchNextDueTimeout` operation to prevent other physical instances of the same logical endpoint from delivering the same delayed message. A custom delayed message store must also take some kind of lock to prevent this from happening. For example, a delayed message store using Azure Blob Storage may take a lease lock.
 
 ### IDelayedMessageStore
 
diff --git a/transports/postgresql/native-publish-subscribe.md b/transports/postgresql/native-publish-subscribe.md
@@ -1,7 +1,7 @@
 ---
 title: PostgreSQL Native Publish Subscribe
 summary: Describes the native publish subscribe implementation in the PostgreSQL transport
-reviewed: 2024-05-28
+reviewed: 2026-03-20
 component: PostgreSqlTransport
 ---
 
