Remove ServiceInsight from /architecture and /get-started docs (#7977)

* Removed references to SI from architecture/recoverability.md

* Updated SI references to SP in architecture/workflows.md

* Removed SI references from get-started docs

* Update reviewed dates on architecture changes

* Fixed broken link for the new ServicePulse link

Author: ngallegos

architecture/recoverability.md

@@ -1,7 +1,7 @@
 ---
 title: Recoverability
 summary: Techniques for message recoverability. Handle transient and persistent failures with immediate/delayed retries, error queues, and Particular Platform tools.
-reviewed: 2025-07-03
+reviewed: 2026-01-05
 callsToAction: ['solution-architect']
 ---
 
@@ -42,7 +42,7 @@ Once the root cause of a persistent error has been resolved, messages can be mov
 > - 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.
+> - [ServicePulse](/servicepulse/intro-failed-messages.md) offers monitoring and inspection of failed messages as well as advanced retry functionality.
 
 ## Best practices
 

architecture/workflows.md

@@ -1,7 +1,7 @@
 ---
 title: Workflows
 summary: Stateful workflow techniques in distributed systems using NServiceBus sagas for choreographed and orchestrated business processes
-reviewed: 2025-06-30
+reviewed: 2026-01-05
 callsToAction: ['solution-architect']
 ---
 
@@ -14,9 +14,9 @@ Business processes typically involve various distributed components that need to
 
 Choreographed workflows are implemented by an implicit flow of events between services instead of a central owner of a process. Services are highly decoupled by the use of [publish/subscribe](/architecture/messaging.md#communication-styles-publishsubscribe-pattern). Published messages are called _events_ because they describe a fact about something that happened to the rest of the system. Subscribers react to events as required. There is no central state of the workflow.
 
-![](/serviceinsight/images/overview-sequence-diagram.png)
+![](/servicepulse/images/sequence-diagram.png)
 
-_A choreographed event-driven workflow across multiple endpoints, visualized by a [ServiceInsight sequence diagram](/serviceinsight/sequence-diagram)._
+_A choreographed event-driven workflow across multiple endpoints, visualized by a [ServicePulse sequence diagram](/servicepulse/sequence-diagram.md)._
 
 ### Implementing choreographed workflows
 
@@ -41,9 +41,9 @@ Orchestrated workflows are managed by a central process that instructs component
 
 NServiceBus is designed to handle long-running business processes in a robust and scalable way using the [saga feature](/nservicebus/sagas/). NServiceBus sagas are a convenient programming model to implement orchestrated, long-running business workflows or state machines using regular C# (or any other .NET language). Sagas handle recoverability, shared state, message correlation, timeouts, and more.
 
-![](/serviceinsight/images/overview-sagaview.png)
+![](/servicepulse/images/saga-diagram.png)
 
-_An orchestrated workflow implemented as an NServiceBus Saga, visualized by [ServiceInsight](/serviceinsight)._
+_An orchestrated workflow implemented as an NServiceBus Saga, visualized by [ServicePulse](/servicepulse)._
 
 [**Tutorial: Introduction to NServiceBus sagas →**](/tutorials/nservicebus-sagas/1-saga-basics/)
 

get-started/high-level-content.md

@@ -1,11 +1,11 @@
 ---
 title: High-level content
-summary: Introductory guide to the Particular Service Platform with an overview of NServiceBus, ServiceControl, ServiceInsight, architecture, and hosting resources.
-reviewed: 2024-11-06
+summary: Introductory guide to the Particular Service Platform with an overview of NServiceBus, ServiceControl, ServicePulse, architecture, and hosting resources.
+reviewed: 2026-01-05
 ---
 
 These articles are recommended to gain an understanding of the key concepts and technologies used within the Particular Service Platform.
 
-* [Service Platform Overview](/platform/): An overview of the various parts of the Platform; [NServiceBus](/nservicebus/), [ServiceControl](/servicecontrol/), [ServiceInsight](/serviceinsight/) and [ServicePulse](/servicepulse/).
+* [Service Platform Overview](/platform/): An overview of the various parts of the Platform; [NServiceBus](/nservicebus/), [ServiceControl](/servicecontrol/) and [ServicePulse](/servicepulse/).
 * [Architectural concepts](/architecture/) of distributed systems
 * [Hosting](/nservicebus/hosting/): Information on the various approaches to hosting an instance of NServiceBus.

get-started/index.md

@@ -5,7 +5,7 @@ reviewed: 2025-10-29
 suppressRelated: true
 ---
 
-NServiceBus makes it quick and easy to send, process, and publish messages across a wide variety of on-premises and cloud-based queuing technologies. All the low-level serialization, threading, and transaction management is handled out-of-the box. Monitoring and debugging are easy to set up thanks to ServicePulse and ServiceInsight.
+NServiceBus makes it quick and easy to send, process, and publish messages across a wide variety of on-premises and cloud-based queuing technologies. All the low-level serialization, threading, and transaction management is handled out-of-the box. Monitoring and debugging are easy to set up thanks to ServicePulse.
 
 ### Start the journey with NServiceBus using these handy resources: