Documentation review

nservicebus/hosting/nservicebus-host/profiles.md

@@ -6,7 +6,7 @@ redirects:
  - nservicebus/more-on-profiles
  - nservicebus/nservicebus/hosting/nservicebus-host/more-on-profiles
 component: Host
-reviewed: 2023-05-14
+reviewed: 2025-05-06
 ---
 
 include: host-deprecated-warning
@@ -23,8 +23,8 @@ There are two categories of profile:
 
 ## Default profiles
 
-By default, NServiceBus comes with a set of predefined environments and feature profiles. It's also possible to create custom profiles or customize the default profiles; to learn more about those options, refer to the [NServiceBus host profiles customization](/nservicebus/hosting/nservicebus-host/profiles-customization.md) article.
-
+By default, NServiceBus comes with a set of predefined environments and feature profiles.
+It's also possible to create custom profiles or customize the default profiles; to learn more about those options, refer to the [NServiceBus host profiles customization options](/nservicebus/hosting/nservicebus-host/profiles-customization.md).
 
 ## Environment profiles
 
@@ -59,7 +59,7 @@ The default if no explicit profile is defined. This profile configures the endpo
 
 ## Specifying which profiles to run
 
-If the host is run without specifying a profile, NServiceBus defaults to the `Production` profile.
+If the host runs without specifying a profile, NServiceBus defaults to the `Production` profile.
 
 To activate a specific profile, pass the full name of the profile in the command line when starting the host. Type names are case-insensitive. Profiles can be combined by separating them with white space.
 
@@ -92,9 +92,6 @@ Refer to the [logging configuration](/nservicebus/hosting/nservicebus-host/loggi
 
 ## Persistence
 
-> [!NOTE]
-> In NServiceBus version 5 and above, persistence must be explicitly configured.
-
 The built-in profiles use the following default persistence settings:
 
 | -              | Lite     | Integration  | Production   |

servicecontrol/monitoring-instances/index.md

@@ -1,7 +1,7 @@
 ---
 title: Monitoring instances
 summary: Information about monitoring instances in ServiceControl
-reviewed: 2023-04-14
+reviewed: 2025-05-06
 component: ServiceControl
 ---
 
@@ -25,6 +25,7 @@ graph LR
 ```
 
 > [!NOTE]
-> Monitoring instances store data about each endpoint in memory for 10 minutes. Monitoring instances do not store persistent data. Restarting the monitoring instance will clear the in-memory cache.
+> Monitoring instances store data about each endpoint in memory for 10 minutes. Monitoring instances do not store data in a persistent store.
+> Restarting the monitoring instance will clear the in-memory cache.
 
 Each environment should have a single monitoring instance that all endpoints are configured to use.

transports/msmq/routing-extensibility.md

@@ -1,7 +1,7 @@
 ---
 title: Routing system extensibility points for MSMQ
-summary: Extending MSMQ's physical routing 
-reviewed: 2023-05-14
+summary: Extending MSMQ's physical routing
+reviewed: 2025-05-06
 component: MsmqTransport
 related:
  - nservicebus/messaging/routing

transports/sqs/performance-tuning.md

@@ -2,7 +2,7 @@
 title: Performance Tuning
 summary: Guidance to tweak the performance of the SQS transport
 component: SQS
-reviewed: 2023-05-02
+reviewed: 2025-05-06
 ---
 
 > [!NOTE]
@@ -62,12 +62,12 @@ var servicePoint = ServicePointManager.FindServicePoint(new Uri("sqs-endpoint-ur
 servicePoint.UseNagleAlgorithm = false;
 ```
 
-to find the endpoint URIs used, consult the [AWS Regions and Endpoints](https://docs.aws.amazon.com/general/latest/gr/rande.html) documentation. It is also possible to disable Nagle globally for the Application Domain by applying:
+To find the endpoint URIs used, consult the [AWS Regions and Endpoints](https://docs.aws.amazon.com/general/latest/gr/rande.html) documentation. It is also possible to disable Nagle's Algorithm globally for the Application Domain by applying:
 
 ```
 ServicePointManager.UseNagleAlgorithm = false;
 ```
 
 ## Known Limitations
 
-- The transport uses a single client for all operations on SQS. The throughput of a single endpoint is thus limited to the number of connections a single client can handle
+The transport uses a single client for all operations on SQS. The throughput of a single endpoint is thus limited to the number of connections a single client can handle.