full edit management topics(3)

Author: anita-flegg

api/v4/management/cloud-foundry.md

@@ -5,36 +5,36 @@ Integration with [Tanzu Apps Manager](https://techdocs.broadcom.com/us/en/vmware
 When used, this endpoint enables the following additional functionality on Cloud Foundry:
 
 * A variant of the [hypermedia](./hypermedia.md) endpoint is registered at `/cloudfoundryapplication`.
-* All endpoints are additionally mapped under the base path `/cloudfoundryapplication`.
+* All endpoints are also mapped under the base path `/cloudfoundryapplication`.
 * [Authentication and authorization](#security) for your Cloud Foundry environment is added to the request pipeline.
 
 > [!NOTE]
-> The Cloud Foundry integration will not work unless the [Cloud Foundry Configuration Provider](../configuration/cloud-foundry-provider.md) has also been configured.
+> The Cloud Foundry integration works only when the [Cloud Foundry Configuration Provider](../configuration/cloud-foundry-provider.md) has also been configured.
 
 ## Configure Settings
 
 Typically, no additional configuration is needed. However, the following table describes the configuration settings that you can apply to the Cloud Foundry endpoint.
 Each key must be prefixed with `Management:Endpoints:CloudFoundry`.
 
 | Key | Description | Default |
-| --- | --- | --- |
-| `Enabled` | Whether the endpoint is enabled. | `true` |
-| `ID` | The unique ID of the endpoint. | `""` |
-| `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` |
-| `ValidateCertificates` | Whether to validate server certificates. | `true` |
-| `ApplicationId` | The ID of the application used in permission checks. | |
-| `CloudFoundryApi` | The URL of the Cloud Foundry API. | |
+| --- | ----------- | ------- |
+| `Enabled` | Whether the endpoint is enabled | `true` |
+| `ID` | The unique ID of the endpoint | `""` |
+| `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` |
+| `ValidateCertificates` | Whether to validate server certificates | `true` |
+| `ApplicationId` | The ID of the application used in permission checks | |
+| `CloudFoundryApi` | The URL of the Cloud Foundry API | |
 
 ## 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 `/cloudfoundryapplication`.
 
-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, add a [CORS](#cross-origin-resource-sharing) policy, register security middleware and map its route, use the `AddCloudFoundryActuator` extension method.
+To add the actuator to the service container, add a [CORS](#cross-origin-resource-sharing) policy, register security middleware and map its route, and use the `AddCloudFoundryActuator` extension method.
 
 Add the following code to `Program.cs` to use the actuator endpoint:
 
@@ -53,10 +53,10 @@ builder.Services.AddCloudFoundryActuator();
 
 ### Cross Origin Resource Sharing
 
-When viewing an application in Apps Manager, HTTP requests are sent directly to application instances with the bearer token of the logged-in user attached.
+When viewing an application in Apps Manager, HTTP requests are sent directly to application instances, with the bearer token of the logged-in user attached.
 The nature of this integration requires the use of Cross Origin Resource Sharing ([CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS)).
-The policy defined in Steeltoe intends to limit sharing to the minimum required for the endpoints to function, however there is no way for Steeltoe to discover or even guess at what the origin of an Apps Manager instance could be.
-As such, the default policy will allow any origin, unless the policy is customized. You should consider [customizing the CORS policy](./using-endpoints.md#customizing-the-cors-policy) to be more specific.
+The policy defined in Steeltoe intends to limit sharing to the minimum required for the endpoints to function; however, there is no way for Steeltoe to discover or infer what the origin of an Apps Manager instance could be.
+As such, the default policy allows any origin, unless the policy is customized. You should consider [customizing the CORS policy](./using-endpoints.md#customizing-the-cors-policy) to be more specific.
 
 ## Security
 
@@ -65,7 +65,7 @@ The Cloud Foundry security middleware requires a valid UAA access token to be pr
 Additionally, the security middleware evaluates the token to determine whether the authenticated user has permission to access the management endpoint.
 
 > [!NOTE]
-> The Cloud Foundry security middleware is only active when your application is running on Cloud Foundry.
+> The Cloud Foundry security middleware is active only when your application is running on Cloud Foundry.
 
 ## External access
 
@@ -77,5 +77,5 @@ For this reason, all endpoints are exposed by default at `/cloudfoundryapplicati
 In addition, the endpoints may be secured by whatever security mechanism the application itself uses. For more details, see [securing actuators](./using-endpoints.md#securing-endpoints).
 
 > [!CAUTION]
-> Applying an authorization policy on `/actuator` will also impact `/cloudfoundryapplication`, which will break the integration with Apps Manager.
-> In order to prevent public access to `/actuator` when running on Cloud Foundry, consider configuring actuators to [use an alternate port](./using-endpoints.md#configure-global-settings).
+> Applying an authorization policy on `/actuator` also has an impact on `/cloudfoundryapplication`, which then breaks the integration with Apps Manager.
+> To prevent public access to `/actuator` when running on Cloud Foundry, consider configuring actuators to [use an alternate port](./using-endpoints.md#configure-global-settings).

api/v4/management/health.md

@@ -152,7 +152,7 @@ When `ShowComponents` and `ShowDetails` are set to `Always`, or when set to `Whe
 
 ## Health Groups
 
-If you need to check application health based on a subset of health contributors, you can specify the name of the grouping and a comma-separated list of contributors to include:
+If you want to check application health based on a subset of health contributors, you can specify the name of the grouping and a comma-separated list of contributors to include:
 
 ```json
 {

api/v4/management/prometheus.md

@@ -6,11 +6,11 @@ The Steeltoe Prometheus endpoint configures the [OpenTelemetry Prometheus Export
 
 The Prometheus endpoint does not automatically instrument your application, but does make it easy to export metrics in the Prometheus metrics format, which can be used by tools like [Prometheus Server](https://prometheus.io/) and the [Metric Registrar for Tanzu Platform for Cloud Foundry](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/tanzu-platform-for-cloud-foundry/10-0/tpcf/metric-registrar-index.html).
 
-The [Steeltoe Management samples](https://github.com/SteeltoeOSS/Samples/tree/main/Management/src/ActuatorWeb/README.md) can help you understand how to use this tool.
+See the [Steeltoe Management samples](https://github.com/SteeltoeOSS/Samples/tree/main/Management/src/ActuatorWeb/README.md) for more information about using this tool.
 
 ## Add NuGet Reference
 
-To use the Prometheus endpoint, you need to add a reference to the `Steeltoe.Management.Prometheus` NuGet package.
+To use the Prometheus endpoint, add a reference to the `Steeltoe.Management.Prometheus` NuGet package.
 
 ## Configure Settings
 
@@ -26,7 +26,7 @@ Each key must be prefixed with `Management:Endpoints:Prometheus:`.
 | `AllowedVerbs` | An array of HTTP verbs at which the endpoint is exposed | `GET` |
 
 > [!NOTE]
-> The `AllowedVerbs` setting is inherited from Steeltoe's `EndpointOptions`, but is not intended to work for the Prometheus exporter, which is only registered to respond to `GET` requests.
+> The `AllowedVerbs` setting is inherited from the Steeltoe `EndpointOptions`, but is not intended to work for the Prometheus exporter, which is only registered to respond to `GET` requests.
 
 ## Enable HTTP Access
 
@@ -49,59 +49,65 @@ builder.Services.AddPrometheusActuator();
 ### Configuring the request pipeline for Prometheus
 
 In addition to the options described in [using endpoints](./using-endpoints.md), `AddPrometheusActuator` exposes an `Action<IApplicationBuilder>?` that can be used to configure the branched request pipeline that is used in the underlying OpenTelemetry package.
-This pipeline would need to be configured if, as an example, you are configuring an authorization policy.
+This pipeline must be configured if, as an example, you are configuring an authorization policy.
 
 ```csharp
 builder.Services.AddPrometheusActuator(true, pipeline => pipeline.UseAuthorization());
 ```
 
 ## Instrumentation
 
-In order for the Prometheus endpoint to return metrics, the application and relevant libraries need to be instrumented.
-This page will cover the basics for elements that previous versions of Steeltoe configured automatically.
-Please refer to the [OpenTelemetry documentation](https://opentelemetry.io/docs/languages/net/instrumentation/) for more detailed information.
+For the Prometheus endpoint to return metrics, the application and relevant libraries must be instrumented.
+This topic covers the basics for elements that previous versions of Steeltoe configured automatically.
+Refer to the [OpenTelemetry documentation](https://opentelemetry.io/docs/languages/net/instrumentation/) for more detailed information.
 
 ### ASP.NET Core
 
-To instrument ASP.NET Core for metrics, start by adding a reference to the `OpenTelemetry.Instrumentation.AspNetCore` NuGet package.
+To instrument ASP.NET Core for metrics:
 
-Next, add the instrumentation to the `MeterProviderBuilder`:
+1. Add a reference to the `OpenTelemetry.Instrumentation.AspNetCore` NuGet package.
 
-```csharp
-using OpenTelemetry.Metrics;
+1. Add the instrumentation to the `MeterProviderBuilder`:
 
-builder.Services.AddOpenTelemetry().WithMetrics(metrics => metrics.AddAspNetCoreInstrumentation());
-```
+    ```csharp
+    using OpenTelemetry.Metrics;
+
+    builder.Services.AddOpenTelemetry().WithMetrics(metrics => metrics.AddAspNetCoreInstrumentation());
+    ```
 
-[Learn more about ASP.NET Core instrumentation for OpenTelemetry](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/blob/main/src/OpenTelemetry.Instrumentation.AspNetCore)
+For more information about ASP.NET Core instrumentation for OpenTelemetry, see the [OpenTelemetry documentation](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/blob/main/src/OpenTelemetry.Instrumentation.AspNetCore).
 
 ### HttpClient
 
-To instrument `HttpClient`s for metrics, start by adding a reference to the `OpenTelemetry.Instrumentation.Http` NuGet package.
+To instrument `HttpClient`s for metrics:
 
-Next, add the instrumentation to the `MeterProviderBuilder`:
+1. Add a reference to the `OpenTelemetry.Instrumentation.Http` NuGet package.
 
-```csharp
-using OpenTelemetry.Metrics;
+2. Add the instrumentation to the `MeterProviderBuilder`:
 
-builder.Services.AddOpenTelemetry().WithMetrics(metrics => metrics.AddHttpClientInstrumentation());
-```
+    ```csharp
+    using OpenTelemetry.Metrics;
 
-[Learn more about HttpClient instrumentation for OpenTelemetry](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/tree/main/src/OpenTelemetry.Instrumentation.Http)
+    builder.Services.AddOpenTelemetry().WithMetrics(metrics => metrics.AddHttpClientInstrumentation());
+    ```
+
+For more information about HttpClient instrumentation for OpenTelemetry, see the [OpenTelemetry documentation](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/tree/main/src/OpenTelemetry.Instrumentation.Http).
 
 ### .NET Runtime
 
-To instrument the .NET Runtime for metrics, start by adding a reference to the `OpenTelemetry.Instrumentation.Runtime` NuGet package.
+To instrument the .NET Runtime for metrics:
 
-Next, add the instrumentation to the `MeterProviderBuilder`:
+1. Add a reference to the `OpenTelemetry.Instrumentation.Runtime` NuGet package.
 
-```csharp
-using OpenTelemetry.Metrics;
+1. Add the instrumentation to the `MeterProviderBuilder`:
 
-builder.Services.AddOpenTelemetry().WithMetrics(metrics => metrics.AddRuntimeInstrumentation());
-```
+    ```csharp
+    using OpenTelemetry.Metrics;
+
+    builder.Services.AddOpenTelemetry().WithMetrics(metrics => metrics.AddRuntimeInstrumentation());
+    ```
 
-[Learn more about Runtime Instrumentation for OpenTelemetry .NET](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/tree/main/src/OpenTelemetry.Instrumentation.Runtime)
+For more information about Runtime Instrumentation for OpenTelemetry .NET, see the [OpenTelemetry documentation](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/tree/main/src/OpenTelemetry.Instrumentation.Runtime).
 
 ### Prometheus Server
 
@@ -111,7 +117,7 @@ As an example, the following `prometheus.yml` file configures metric scraping fo
 
 ```yml
 global:
-  scrape_interval: 15s # Set the scrape interval to every 15 seconds. The default is every 1 minute.
+  scrape_interval: 15 s # Set the scrape interval to every 15 seconds. The default is every 1 minute.
   evaluation_interval: 15s # Evaluate rules every 15 seconds. The default is every 1 minute.
   # scrape_timeout is set to the global default (10s).
 scrape_configs:
@@ -138,10 +144,10 @@ To emit custom metrics in Cloud Foundry, use [Metric Registrar](https://techdocs
 
 > [!CAUTION]
 > Authenticated endpoints are not supported with Metric Registrar.
-> For this scenario, configure actuators to [use an alternate port](./using-endpoints.md#configure-global-settings) and use that private network port to offer the metrics.
+> For this scenario, configure actuators to use an [alternate port](./using-endpoints.md#configure-global-settings) and use that private network port to offer the metrics.
 
-The examples below expect that actuators are mapped to an alternate port (8091 in this case).
-The specific port that is used is not important to Steeltoe, it only matters that the binding and Steeltoe configurations match.
+The following examples assume that actuators are mapped to an alternate port (8091 in this case).
+The specific port is not important to Steeltoe, it only matters that the binding and Steeltoe configurations match.
 
 #### Metrics Registrar Plugin
 
@@ -169,13 +175,13 @@ cf bind-service APP-NAME SERVICE-NAME
 
 This endpoint returns information about the instrumented application metrics and their values.
 
-If no instrumentation has been included, the response will be very short, like this:
+If no instrumentation has been included, the response is very short:
 
 ```text
 # EOF
 ```
 
-With the addition of [.NET Runtime instrumentation](#net-runtime), the response will be like this:
+With the addition of [.NET Runtime instrumentation](#net-runtime), the response is similar to the following:
 
 ```text
 # TYPE process_runtime_dotnet_gc_collections_count_total counter

api/v4/management/refresh.md

@@ -9,24 +9,24 @@ The following table describes the configuration settings that you can apply to t
 Each key must be prefixed with `Management:Endpoints:Refresh:`.
 
 | Key | Description | Default |
-| --- | --- | --- |
-| `Enabled` | Whether the endpoint is enabled. | `true` |
-| `ID` | The unique ID of the endpoint. | `refresh` |
-| `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. | `POST` |
-| `ReturnConfiguration` | Whether to return the configuration after refresh. | `true` |
+| --- | ----------- | ------- |
+| `Enabled` | Whether the endpoint is enabled | `true` |
+| `ID` | The unique ID of the endpoint | `refresh` |
+| `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 | `POST` |
+| `ReturnConfiguration` | Whether to return the configuration after refresh | `true` |
 
 > [!NOTE]
-> Despite being *possible* to configure this endpoint to respond to `GET` requests,
+> Despite it being *possible* to configure this endpoint to respond to `GET` requests,
 > this is discouraged because it is not a [Safe HTTP Method](https://developer.mozilla.org/en-US/docs/Glossary/Safe/HTTP).
 
 ## 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/refresh`.
 
-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 `AddRefreshActuator` extension method.
 
@@ -47,7 +47,7 @@ builder.Services.AddRefreshActuator();
 
 This endpoint returns an array of keys obtained from `IConfiguration`.
 
-The response will always be returned as JSON, like this:
+The response always returns as JSON:
 
 ```json
 [