review legacy docs (#7058)

Author: soujay

nservicebus/gateway/troubleshooting.md

@@ -1,7 +1,7 @@
 ---
 title: Gateway Troubleshooting
 summary: How to solve common issues that arise with the gateway
-reviewed: 2022-12-16
+reviewed: 2025-03-21
 redirects:
  - nservicebus/gateway-trouble-shooting
  - nservicebus/gateway-service-point-manager
@@ -28,15 +28,15 @@ Url reservation add failed, Error: 183
 Cannot create a file when that file already exists.
 ```
 
-This warning can usually be safely ignored. However when urlacls are corrupted the same behaviors occurs. This problem will manifest in that everything seems to be working correctly except that the gateway will not be listening on the port.
+This warning can usually be safely ignored. However, if the urlacls are corrupted the same behavior as above occurs. In this case, everything may appear to be functioning normally, except that the gateway will not be listening on the port.
 
-To verify this problem navigate to the url (in this case `http://localhost:25894/MyEndpoint/`) in a browser. If the gateway is listening the following will be received:
+To verify this issue, navigate to the url (in this case `http://localhost:25894/MyEndpoint/`) in a browser. If the gateway is listening, the following will be received:
 
 ```
 EndpointName:MyEndpoint - Status: Ok
 ```
 
-If the gateway is not listening no response will be received.
+If the gateway is not listening, no response will be received.
 
 To clean and recreate the url acl manually run the following commands from an admin console:
 

security-advisories/index.md

@@ -1,6 +1,6 @@
 ---
 title: Security Advisories
-reviewed: 2022-12-05
+reviewed: 2025-03-18
 suppressRelated: true
 ---
 

transports/azure-service-bus/configuration.md

@@ -2,7 +2,7 @@
 title: Configuration
 summary: Explains the configuration options
 component: ASBS
-reviewed: 2022-11-15
+reviewed: 2025-03-21
 ---
 
 ## Configuring an endpoint
@@ -26,7 +26,7 @@ partial: custom-token-credentials
 These settings control how the transport creates entities in the Azure Service Bus namespace.
 
 > [!WARNING]
-> Entity creation settings are applied only at creation time of the corresponding entities; they are not updated on subsequent startups.
+> Entity creation settings are applied only at the time the corresponding entities are created; they are not updated on subsequent startups.
 
 partial: access-rights
 

transports/sql/sql-statements.md

@@ -2,7 +2,7 @@
 title: SQL Server transport SQL statements
 summary: Overview of the SQL statements used to manage the SQL Server transport
 component: SqlTransport
-reviewed: 2022-11-24
+reviewed: 2025-03-21
 versions: '[3,)'
 redirects:
 - nservicebus/sqlserver/runtime-sql
@@ -21,21 +21,21 @@ partial: create-subscriptions-table
 
 ### Creating table structure in production
 
-There are some special considerations for creating the queue tables in production environments.
+When creating the queue tables in production environments, there are specific considerations to keep in mind.
 
 
 #### NServiceBus installers
 
-When using NServiceBus [installers](/nservicebus/operations/installers.md) the queue tables are created automatically before the endpoint is started.
+When using NServiceBus [installers](/nservicebus/operations/installers.md), the queue tables are created automatically before the endpoint is started.
 
-the user account under which the installation of the host is performed must have `CREATE TABLE` and `VIEW DEFINITION` permissions on the database where the queues are to be created. The account under which the service runs does not have to have these permissions. Standard read/write/delete permissions (e.g. `db_datawriter` and `db_datareader` roles) are enough.
+The user account under which the installation of the host is performed, must have `CREATE TABLE` and `VIEW DEFINITION` permissions on the database where the queues are to be created. The service account does not need to have these permissions. Standard read/write/delete permissions (e.g. `db_datawriter` and `db_datareader` roles) are sufficient.
 
 
 #### Scripted
 
-Using NServiceBus installers does not allow review of the actual T-SQL statements that are going be executed. For that reason, some prefer to store the actual scripts in a version control system.
+Using NServiceBus installers does not allow review of the actual T-SQL statements that are going be executed. Hence, some prefer to store the actual scripts in a version control system.
 
-The script above is parametrized at execution time with the queue name so it cannot be used as-is. Alternatively, the scripts could be generated from the development or staging environments, then directly executed on a production environment by DBAs to replicate that table structure.
+The script above is parametrized at execution time with the queue name so it cannot be used as-is. Alternatively, the scripts could be generated from the development or staging environments,and then executed on a production environment by DBAs to replicate that table structure.
 
 To capture the script for later execution use SQL Server Management Studio. Connect to the server (e.g. development or staging) and right-click the database with the queue tables. From "Tasks" menu choose "Generate Scripts..." and generate the scripts for relevant tables.