Merge pull request #8020 from Particular/editorial

Weekly recent docs review editorial: 2025-12-22

Author: helenktsai

nservicebus/outbox/index.md

@@ -1,6 +1,6 @@
 ---
 title: Outbox
-summary: Ensure message consistency with NServiceBus Outbox pattern preventing duplicate message processing in distributed systems.
+summary: Use the NServiceBus Outbox pattern to ensure message consistency and prevent duplicate message processing in distributed systems.
 reviewed: 2025-06-05
 component: Core
 isLearningPath: true

persistence/sql/install.md

@@ -9,7 +9,6 @@ reviewed: 2025-12-19
 
 The SQL persistence package generates scripts to create necessary database assets. It is recommended to run those scripts as part of the deployment process. See [Installer Workflow](installer-workflow.md) for more information.
 
-
 ## Script execution during development
 
 To streamline development, SQL persistence will execute generated scripts at endpoint startup if installers are enabled.
@@ -19,18 +18,16 @@ snippet: ExecuteAtStartup
 > [!NOTE]
 > Automatically executing generated scripts is recommended only in development environments.
 
-
 ## Script execution in non-development environments
 
 In non-development environments, where the SQL persistence installation scripts have been executed as part of the deployment, it may be necessary to explicitly disable the SQL persistence installers if [standard installers](/nservicebus/operations/installers.md) need to be used for other purposes.
 
 snippet: DisableInstaller
 
-The `ScriptRunner` class can be used to run the scripts without creating and starting an NServiceBus endpoint
+The `ScriptRunner` class can be used to run the scripts without creating and starting an NServiceBus endpoint.
 
 snippet: ScriptRunner
 
-
 ## Table prefix
 
 The *table prefix* is the string that is prefixed to every table name, e.g. Saga, Outbox, Subscription and Timeout tables.
@@ -46,7 +43,6 @@ When using the default approach to installation (execute at startup), the value
 
 snippet: TablePrefix
 
-
 ## Database schema
 
 When using a database that supports schemas, a schema value other than default can be defined in the configuration API. Consult the documentation of the selected SQL dialect for details.
@@ -58,19 +54,16 @@ When using a database that supports schemas, a schema value other than default c
 > [!NOTE]
 > The same value must be passed to the installation scripts as a parameter.
 
-
 ## Manual installation
 
 When performing a custom script execution the table prefix is required. See also [Installer Workflow](installer-workflow.md).
 
 Note that `scriptDirectory` can be either the root directory for all scripts or the specific locations for a given storage type i.e. Saga, Outbox, Subscription and Timeout scripts.
 
-
 ### SQL Server
 
 snippet: ExecuteScriptsSqlServer
 
-
 ### MySQL
 
 snippet: ExecuteScriptsMySql
@@ -79,7 +72,6 @@ snippet: ExecuteScriptsMySql
 
 snippet: ExecuteScriptsOracle
 
-
 #### PostgreSQL
 
 snippet: ExecuteScriptsPostgreSQL

platform/index.md

@@ -15,7 +15,7 @@ The Particular Service Platform consists of [NServiceBus](/nservicebus), [Servic
 
 ![Particular Service Platform architecture](architecture-overview.png)
 
-The details of each component are discussed below. A Particular Service Platform-based system consists of several NServiceBus [endpoints](/nservicebus/endpoints/). Endpoints are logical entities that perform business operations. They communicate with each other using messages (via queues) and forward messages to ServiceControl for auditing. ServiceControl stores this audit trail and provides integration points for ServicePulse. ServicePulse provides monitoring and recoverability for production systems. ServicePulse provides debugging information and visualization of how the system works.
+The details of each component are discussed below. A Particular Service Platform-based system consists of several NServiceBus [endpoints](/nservicebus/endpoints/). Endpoints are logical entities that perform business operations. They communicate with each other using messages (via queues) and forward messages to ServiceControl for auditing. ServiceControl stores this audit trail and provides integration points for ServicePulse. ServicePulse provides monitoring and recoverability for production systems, as well as debugging information and visualization of how the system works.
 
 ## [NServiceBus](/nservicebus) - where it all begins
 

platform/nservicebus.include.md

@@ -76,7 +76,7 @@ NServiceBus is designed to work with the rest of the Particular Service Platform
 
 When a message fails to be processed, even after a number of retry strategies have been attempted, NServiceBus will forward the message to an [error queue](/nservicebus/recoverability/configure-error-handling.md) for manual investigation. Messages sent to the error queue are instrumented with headers containing details about the failure including a full exception stack trace. ServiceControl picks up messages from the error queue and makes them available in [ServicePulse](/servicepulse/). Once the root cause of the failure has been found and corrected, all messages caused by the same problem can be retried at once.
 
-Additionally, each endpoint can send [heartbeat](/monitoring/heartbeats/), [health check](/monitoring/custom-checks/), and [performance metrics](/monitoring/metrics/) through the platform for visualization in ServicePulse, making it easy to see which endpoints are offline, which are ready to scale out, and which require manual intervention. Message  visualizations available in [ServicePulse](/servicepulse/message-details.md#messages-with-audited-conversation-data) make it easy to understand message flows and timing of a running NServiceBus system.
+Additionally, each endpoint can send [heartbeat](/monitoring/heartbeats/), [health check](/monitoring/custom-checks/), and [performance metrics](/monitoring/metrics/) through the platform for visualization in ServicePulse, making it easy to see which endpoints are offline, which are ready to scale out, and which require manual intervention. Message visualizations available in [ServicePulse](/servicepulse/message-details.md#messages-with-audited-conversation-data) make it easy to understand message flows and timing of a running NServiceBus system.
 
 The [real-time monitoring demo](https://particular.net/real-time-monitoring) provides the ability to experience the Service Platform in action. The [Platform Sample package](/platform/platform-sample-package.md) provides the ability to demonstrate the Service Platform from within any .NET Project, without the need to install anything.
 

serviceinsight/serviceinsight-sunset.include.md

@@ -1,4 +1,4 @@
 > [!WARNING]
-> **ServiceInsight has been sunset**
+> **ServiceInsight has been sunset and will receive no further updates.**
 >
-> We recommend [moving to ServicePulse](/servicepulse/installation.md) for vizualization and debugging capabilities.
+> We recommend [moving to ServicePulse](/servicepulse/installation.md) for vizualization and debugging capabilities.

serviceinsight/support-policy.md

@@ -18,7 +18,7 @@ related:
 >
 > The latest version of ServiceInsight is supported (including bug fixes) until migration instructions to ServicePulse are available.
 
-The latest version can be found on the [downloads page](https://particular.net/downloads), however, it is recommended to install the latest version of [ServicePulse](/servicepulse/installation.md) for the latest features and full support.
+The latest version can be found on the [downloads page](https://particular.net/downloads); however, it is recommended to install the latest version of [ServicePulse](/servicepulse/installation.md) for the latest features and full support.
 
 ## ServiceControl compatibility
 

tutorials/quickstart/tutorial.md

@@ -1,7 +1,7 @@
 ---
 title: "Quickstart: Sending and processing your first messages"
 reviewed: 2025-06-15
-summary: "Part 1: Learn messaging basics with NServiceBus quickstart guide covering commands,events, and publish subscribe patterns"
+summary: "Part 1: Learn messaging basics with NServiceBus quickstart guide covering commands, events, and the publish-subscribe pattern"
 extensions:
 - !!tutorial
   nextText: "Next: Recovering from failure"