full edit Security topics + some consistency changes

Author: anita-flegg

api/v4/connectors/redis.md

@@ -1,7 +1,12 @@
-# Redis
+# Redis/Valkey
 
 This connector simplifies accessing [Redis](https://redis.io/) databases.
+
+> [!NOTE]
+> Redis has been updated to [Valkey](https://valkey.io/topics/migration/).
+
 It supports the following .NET drivers:
+
 - [StackExchange.Redis](https://www.nuget.org/packages/StackExchange.Redis), which provides an `IConnectionMultiplexer`.
 - [Microsoft.Extensions.Caching.StackExchangeRedis](https://www.nuget.org/packages/Microsoft.Extensions.Caching.StackExchangeRedis), which provides an `IDistributedCache`.
 

api/v4/management/prometheus.md

@@ -153,7 +153,7 @@ The specific port is not important to Steeltoe, it only matters that the binding
 
 Install the metrics-registrar plugin and use it to register your endpoint:
 
-```shell
+```bash
 cf install-plugin -r CF-Community "metric-registrar"
 cf register-metrics-endpoint APP-NAME /actuator/prometheus --internal-port 8091
 ```
@@ -166,7 +166,7 @@ cf register-metrics-endpoint APP-NAME /actuator/prometheus --internal-port 8091
 
 The result of using the metrics registrar plugin is a user-provided service, which can also be created and bound manually.
 
-```shell
+```bash
 cf create-user-provided-service APP-NAME -l secure-endpoint://:8091/actuator/prometheus
 cf bind-service APP-NAME SERVICE-NAME
 ```

api/v4/management/tasks.md

@@ -111,7 +111,7 @@ As a matter of best practice, it is recommended that you provide the `RunTask` v
 However, due to the way .NET configuration works, it doesn't matter which configuration provider is used to provide the task name.
 Invoking the command on Cloud Foundry looks similar to this:
 
-```
+```bash
 cf run-task YourAppName "dotnet run -- RunTask=ExampleTaskName" --name ExampleTaskName
 ```
 

api/v4/security/certificate.md

@@ -5,31 +5,31 @@ Certificate Authentication, also known as Mutual TLS, is a way for a client and
 This library is a supplement to [ASP.NET Core Certificate Authentication](https://learn.microsoft.com/aspnet/core/security/authentication/certauth), adding functionality that helps you use [Cloud Foundry Instance Identity certificates](https://docs.cloudfoundry.org/devguide/deploy-apps/instance-identity.html) and authorization policies based on certificate data.
 Additionally, resources are included for automatically generating certificates for local development that resemble what is found on the platform.
 
-## Usage
+## Using Mutual TLS in ASP.NET Core
 
-In order to use this provider, the following steps are required:
+To use this provider, the following steps are required:
 
-1. Add NuGet package reference
-1. Add identity certificates to the configuration
-1. Add and use the security provider in the application
-1. Secure your endpoints
-1. Attach certificate to requests to secured endpoints
+1. Add NuGet package reference.
+1. Add identity certificates to the configuration.
+1. Add and use the security provider in the application.
+1. Secure your endpoints.
+1. Attach certificate to requests to secured endpoints.
 
 ### Add NuGet Reference
 
 > [!NOTE]
-> This step is required on all applications that are sending or receiving certificate-authorized requests.
+> This step is required for all applications that are sending or receiving certificate-authorized requests.
 
-To use Certificate Authorization, you need to add a reference to the `Steeltoe.Security.Authorization.Certificate` NuGet package.
+To use Certificate Authorization, add a reference to the `Steeltoe.Security.Authorization.Certificate` NuGet package.
 
 ### Add Identity Certificates to Configuration
 
 > [!NOTE]
-> This step is required on all applications that are sending or receiving certificate-authorized requests.
+> This step is required for all applications that are sending or receiving certificate-authorized requests.
 
 In a Cloud Foundry environment, instance identity certificates are automatically provisioned (and rotated on a regular basis) for each application instance.
 Steeltoe provides the extension method `AddAppInstanceIdentityCertificate` to find the location of the certificate files from the environment variables `CF_INSTANCE_CERT` and `CF_INSTANCE_KEY`.
-When running outside of Cloud Foundry, this method will automatically generate similar certificates.
+When running outside of Cloud Foundry, this method automatically generates similar certificates.
 Use the optional parameters to coordinate `orgId` and/or `spaceId` between your applications to facilitate communication when running outside of Cloud Foundry.
 
 This code adds the certificate paths to the configuration for use later (and generates the instance identity certificate when running outside Cloud Foundry):
@@ -44,25 +44,25 @@ var builder = WebApplication.CreateBuilder(args);
 builder.Configuration.AddAppInstanceIdentityCertificate(new Guid(orgId), new Guid(spaceId));
 ```
 
-When running locally, the code shown above will create a chain of self-signed certificates and the application instance identity certificate will have a subject containing an OrgId of `a8fef16f-94c0-49e3-aa0b-ced7c3da6229` and a SpaceId of `122b942a-d7b9-4839-b26e-836654b9785f`.
+When running locally, the preceding code sample creates a chain of self-signed certificates. The application instance identity certificate is created with a subject containing an OrgId of `a8fef16f-94c0-49e3-aa0b-ced7c3da6229` and a SpaceId of `122b942a-d7b9-4839-b26e-836654b9785f`.
 A root certificate and intermediate certificate are created on disk one level above the current project in a directory named `GeneratedCertificates`.
-The root and intermediate certificates will automatically be shared between applications housed within the same solution, so that the applications will be able to trust each other.
+The root and intermediate certificates are automatically shared between applications housed within the same solution, so that the applications can trust each other.
 
 ### Add and use Certificate Authentication
 
 > [!NOTE]
-> This section is only required on applications that are receiving certificate-authorized requests.
+> This section is required only on applications that are receiving certificate-authorized requests.
 
 Several steps need to happen before certificate authorization policies can be used to secure resources:
 
-1. Configuration values need to be bound into named `CertificateOptions`
-1. Certificate files need to be monitored for changes (to stay up to date when certificates are rotated)
-1. Certificate forwarding needs to be configured (so that ASP.NET reads the certificate out of an HTTP Header)
-1. Authentication services need to be added
-1. Authorization services and policies need to be added
-1. Middleware needs to be activated
+1. Bind configuration values into named `CertificateOptions`.
+2. Monitor certificate files for changes (to stay up to date when certificates are rotated).
+3. Configure certificate forwarding (so that ASP.NET reads the certificate from an HTTP Header).
+4. Add authentication services.
+5. Add authorization services and policies.
+6. Activate middleware.
 
-Fortunately, all of the requirements can be satisfied with a handful of extension methods:
+Fortunately, all of these requirements can be satisfied with a handful of extension methods:
 
 ```csharp
 using Steeltoe.Security.Authorization.Certificate;
@@ -108,12 +108,12 @@ app.UseCertificateAuthorization();
 ### Securing Endpoints
 
 > [!NOTE]
-> This step is only required on applications that are receiving certificate-authorized requests.
+> This step is required only on applications that are receiving certificate-authorized requests.
 
-As implied by the name of the extension method `AddOrgAndSpacePolicies` from the previous section on this page, Steeltoe provides policies for validating that a request came from an application in the same org and/or the same space. You can secure endpoints by using the standard ASP.NET Core `Authorize` attribute with these security policies.
+As implied by the name of the extension method `AddOrgAndSpacePolicies` (from the previous section in this topic), Steeltoe provides policies for validating that a request came from an application in the same org and/or the same space. You can secure endpoints using the standard ASP.NET Core `Authorize` attribute with these security policies.
 
 > [!NOTE]
-> If needed, see the Microsoft documentation about [authorization in ASP.NET Core](https://learn.microsoft.com/aspnet/core/security/authorization/introduction) for a better understanding of how to use these attributes.
+> For more information about authorization in ASP.NET Core, see the [Microsoft documentation](https://learn.microsoft.com/aspnet/core/security/authorization/introduction).
 
 The following example shows a controller using the security attributes with the included policies:
 
@@ -153,18 +153,18 @@ In the preceding example, when an incoming request is made to the `SameOrgCheck`
 
 ### Communicating with Secured Services
 
-In order to use app instance identity certificates in a client application, services need to be configured, but nothing needs to be activated in the ASP.NET Core request pipeline.
+To use app instance identity certificates in a client application, services must be configured, but nothing needs to be activated in the ASP.NET Core request pipeline.
 
 #### IHttpClientFactory integration
 
 > [!NOTE]
-> This step is only required on applications that are sending certificate-authorized requests.
+> This step is required only on applications that are sending certificate-authorized requests.
 
-For applications that need to send identity certificates in outgoing requests, Steeltoe provides a smooth experience through an extension method on `IHttpClientBuilder` named `AddAppInstanceIdentityCertificate`.
+For applications that need to send identity certificates in outgoing requests, Steeltoe provides a smooth experience through an extension method on `IHttpClientBuilder` called `AddAppInstanceIdentityCertificate`.
 This method invokes code that handles loading certificates from paths defined in the application's configuration, monitors those file paths and their content for changes, and places the certificate in an HTTP header named `X-Client-Cert` on all outbound requests.
 
 > [!NOTE]
-> If needed, see the Microsoft documentation about [IHttpClientFactory](https://learn.microsoft.com/aspnet/core/fundamentals/http-requests) for details.
+> For more information about IHttpClientFactory, see the [Microsoft documentation](https://learn.microsoft.com/aspnet/core/fundamentals/http-requests).
 
 ```csharp
 using Steeltoe.Security.Authorization.Certificate;

api/v4/security/index.md

@@ -11,3 +11,6 @@ Choose from the following options when using Cloud Foundry security integration:
 In addition to authentication and authorization providers, Steeltoe security offers:
 
 * [A security provider for using Redis on Cloud Foundry with ASP.NET Core Data Protection Key Ring storage](redis-key-storage-provider.md)
+
+> [!NOTE]
+> Redis has been updated to [Valkey](https://valkey.io/topics/migration/).