full edit management topics(1) + bulk Note wording change

Author: anita-flegg

api/v4/configuration/decryption-provider.md

@@ -107,5 +107,5 @@ var builder = WebApplication.CreateBuilder(args);
 builder.Configuration.AddDecryption(new ExampleTextDecryptor(), NullLoggerFactory.Instance);
 ```
 
-> [!WARNING]
+> [!CAUTION]
 > Creating encryption algorithms is notoriously difficult. Use this only if you know what you are doing.

api/v4/management/cloud-foundry.md

@@ -48,7 +48,7 @@ builder.Services.AddCloudFoundryActuator();
 ```
 
 > [!TIP]
-> It's recommended to use `AddAllActuators()` instead of adding individual actuators,
+> It is recommended that you use `AddAllActuators()` instead of adding individual actuators,
 > which enables individually turning them on/off at runtime via configuration.
 
 ### Cross Origin Resource Sharing

api/v4/management/dbmigrations.md

@@ -1,29 +1,29 @@
 # Database Migrations
 
-The Steeltoe Database Migrations endpoint exposes information about database migrations that are available to an application's data source that has been built with Entity Framework Core (EF Core). EF Core migrations give developers the ability to update an application's database schema while staying consistent with the application's data model without removing any existing data.
+The Steeltoe Database Migrations endpoint exposes information about database migrations that are available to an application's data source that has been built with Entity Framework Core (EF Core). EF Core migrations give developers the ability to update an application's database schema while staying consistent with the application's data model, and without removing any existing data.
 
 > [!NOTE]
-> Please review Microsoft's [EF Core Migrations Overview](https://learn.microsoft.com/ef/core/managing-schemas/migrations) for more in-depth information.
+> For more detailed information, see [EF Core Migrations Overview](https://learn.microsoft.com/ef/core/managing-schemas/migrations) in the Microsoft documentation.
 
 ## Configure Settings
 
 The following table describes the configuration settings that you can apply to the endpoint.
 Each key must be prefixed with `Management:Endpoints:DbMigrations:`.
 
 | Key | Description | Default |
-| --- | --- | --- |
-| `Enabled` | Whether the endpoint is enabled. | `true` |
-| `ID` | The unique ID of the endpoint. | `dbmigrations` |
-| `Path` | The relative path at which the endpoint is exposed. | same as `ID` |
-| `RequiredPermissions` | Permissions required to access the endpoint, when running on Cloud Foundry. | `Restricted` |
-| `AllowedVerbs` | An array of HTTP verbs the endpoint is exposed at. | `GET` |
+| --- | ----------- | ------- |
+| `Enabled` | Whether the endpoint is enabled | `true` |
+| `ID`      | The unique ID of the endpoint | `dbmigrations` |
+| `Path`    | The relative path at which the endpoint is exposed | same as `ID` |
+| `RequiredPermissions` | Permissions required to access the endpoint when running on Cloud Foundry | `Restricted` |
+| `AllowedVerbs` | An array of HTTP verbs at which the endpoint is exposed | `GET` |
 
 ## Enable HTTP Access
 
-The URL path to the endpoint is computed by combining the global `Management:Endpoints:Path` setting together with the `Path` setting described in the preceding section.
+The URL path to the endpoint is computed by combining the global `Management:Endpoints:Path` setting with the `Path` setting described in the preceding section.
 The default path is `/actuator/dbmigrations`.
 
-See the [Exposing Endpoints](./using-endpoints.md#exposing-endpoints) and [HTTP Access](./using-endpoints.md#http-access) sections for the overall steps required to enable HTTP access to endpoints in an ASP.NET Core application.
+See the [Exposing Endpoints](./using-endpoints.md#exposing-endpoints) and [HTTP Access](./using-endpoints.md#http-access) sections for the steps required to enable HTTP access to endpoints in an ASP.NET Core application.
 
 To add the actuator to the service container and map its route, use the `AddDbMigrationsActuator` extension method.
 
@@ -37,14 +37,14 @@ builder.Services.AddDbMigrationsActuator();
 ```
 
 > [!TIP]
-> It's recommended to use `AddAllActuators()` instead of adding individual actuators,
+> It is recommended that you use `AddAllActuators()` instead of adding individual actuators,
 > which enables individually turning them on/off at runtime via configuration.
 
 ## Sample Output
 
 This endpoint returns a list of objects representing each registered `DbContext` along with its migrations, grouped by status (pending or applied).
 
-The response will always be returned as JSON, like this:
+The response is always returned as JSON, as shown here:
 
 ```json
 {

api/v4/management/env.md

@@ -8,22 +8,22 @@ The following table describes the configuration settings that you can apply to t
 Each key must be prefixed with `Management:Endpoints:Env:`.
 
 | Key | Description | Default |
-| --- | --- | --- |
-| `Enabled` | Whether the endpoint is enabled. | `true` |
-| `ID` | The unique ID of the endpoint. | `env` |
-| `Path` | The relative path at which the endpoint is exposed. | same as `ID` |
-| `RequiredPermissions` | Permissions required to access the endpoint, when running on Cloud Foundry. | `Restricted` |
-| `AllowedVerbs` | An array of HTTP verbs the endpoint is exposed at. | `GET` |
-| `KeysToSanitize` | An array of keys to sanitize. [^1] | `[ "password", "secret", "key", "token", ".*credentials.*", "vcap_services" ]` |
+| --- | ----------- | ------- |
+| `Enabled` | Whether the endpoint is enabled | `true` |
+| `ID`      | The unique ID of the endpoint | `env` |
+| `Path`    | The relative path at which the endpoint is exposed | same as `ID` |
+| `RequiredPermissions` | Permissions required to access the endpoint, when running on Cloud Foundry | `Restricted` |
+| `AllowedVerbs` | An array of HTTP verbs at which the endpoint is exposed | `GET` |
+| `KeysToSanitize` | An array of keys to sanitize [^1] | `[ "password", "secret", "key", "token", ".*credentials.*", "vcap_services" ]` |
 
 [^1]: A key can be a simple string that the property must end with, or a regular expression. A case-insensitive match is always performed. Use a single-element empty string to disable sanitization.
 
 ## Enable HTTP Access
 
-The URL path to the endpoint is computed by combining the global `Management:Endpoints:Path` setting together with the `Path` setting described in the preceding section.
+The URL path to the endpoint is computed by combining the global `Management:Endpoints:Path` setting with the `Path` setting described in the preceding section.
 The default path is `/actuator/env`.
 
-See the [Exposing Endpoints](./using-endpoints.md#exposing-endpoints) and [HTTP Access](./using-endpoints.md#http-access) sections for the overall steps required to enable HTTP access to endpoints in an ASP.NET Core application.
+See the [Exposing Endpoints](./using-endpoints.md#exposing-endpoints) and [HTTP Access](./using-endpoints.md#http-access) sections for the steps required to enable HTTP access to endpoints in an ASP.NET Core application.
 
 To add the actuator to the service container and map its route, use the `AddEnvironmentActuator` extension method.
 
@@ -36,15 +36,15 @@ var builder = WebApplication.CreateBuilder(args);
 builder.Services.AddEnvironmentActuator();
 ```
 
-> [!TIP]
-> It's recommended to use `AddAllActuators()` instead of adding individual actuators,
+> [!NOTE]
+> It is recommended that you use `AddAllActuators()` instead of adding individual actuators,
 > which enables individually turning them on/off at runtime via configuration.
 
 ## Sample Output
 
 This endpoint returns a list of objects representing information from `IConfiguration`.
 
-The response will always be returned as JSON, like this:
+The response is always returned as JSON, like this:
 
 ```json
 {