lowercase key provider in prose

Author: pranavjain97

README.md

@@ -16,7 +16,7 @@ Advanced wallets operate in two modes:
 Key features include:
 
 - **Complete Infrastructure Control** - Host and manage all components in your own secure environment.
-- **KMS/HSM Integration** - Bring your own KMS or HSM by implementing the provided [Advanced Wallets Key Provider API interface specification](./key-provider-api-spec.yaml). Reference implementations available for [AWS HSM](./demo-key-provider-script/aws-interface.md) and [Dinamo HSM](./demo-key-provider-script/dinamo-interface.md).
+- **KMS/HSM Integration** - Bring your own KMS or HSM by implementing the provided [advanced wallets key provider API interface specification](./key-provider-api-spec.yaml). Reference implementations available for [AWS HSM](./demo-key-provider-script/aws-interface.md) and [Dinamo HSM](./demo-key-provider-script/dinamo-interface.md).
 - **Network Isolation** - Advanced Wallet Manager operates in a completely isolated network segment with no external internet access.
 - **mTLS Security** - Optional mutual TLS with client certificate validation for secure inter-service communications.
 - **Flexible Configuration** - Environment-based setup with file or variable-based certificates.
@@ -38,7 +38,7 @@ Key features include:
 
 ## Architecture
 
-- **Advanced Wallet Manager** (Port 3080) - An isolated signing server with no internet access that only connects to your Key Provider API implementation for key operations.
+- **Advanced Wallet Manager** (Port 3080) - An isolated signing server with no internet access that only connects to your key provider API implementation for key operations.
 - **Master Express** (Port 3081) - An API gateway providing end-to-end wallet creation and transaction support, integrating [BitGo APIs](https://developers.bitgo.com/reference/overview#/) with secure communication to Advanced Wallet Manager.
 
 ## Installation
@@ -49,7 +49,7 @@ Key features include:
 - **npm** or **yarn** package manager.
 - **OpenSSL** for certificate generation.
 - **Docker** and **Docker Compose** for containerized deployment (or you can use **Podman** as alternative to Docker).
-- **Key Provider API Implementation** - You must implement the [Key Provider API interface specification](./key-provider-api-spec.yaml) to connect your KMS/HSM to the Advanced Wallet Manager. Reference implementations available:
+- **key provider API implementation** - You must implement the [key provider API interface specification](./key-provider-api-spec.yaml) to connect your KMS/HSM to the Advanced Wallet Manager. Reference implementations available:
   - [AWS HSM Implementation Example](./demo-key-provider-script/aws-interface.md)
   - [Dinamo HSM Implementation Example](./demo-key-provider-script/dinamo-interface.md)
 
@@ -168,9 +168,9 @@ curl -X POST http://localhost:3081/ping/advancedWalletManager
 | Variable                       | Description                        | Default | Required |
 | ------------------------------ | ---------------------------------- | ------- | -------- |
 | `ADVANCED_WALLET_MANAGER_PORT` | Port to listen on                  | `3080`  | ❌       |
-| `KEY_PROVIDER_URL`             | URL to your Key Provider API implementation | -       | ✅       |
+| `KEY_PROVIDER_URL`             | URL to your key provider API implementation | -       | ✅       |
 
-> **Note:** The `KEY_PROVIDER_URL` points to your implementation of the Key Provider API interface. You must implement this interface to connect your KMS/HSM. See [Prerequisites](#prerequisites) for the specification and examples.
+> **Note:** The `KEY_PROVIDER_URL` points to your implementation of the key provider API interface. You must implement this interface to connect your KMS/HSM. See [Prerequisites](#prerequisites) for the specification and examples.
 
 ### Master Express Settings
 
@@ -232,16 +232,16 @@ curl -X POST http://localhost:3081/ping/advancedWalletManager
 | `AWM_SERVER_CA_CERT`                | AWM server CA certificate (alternative)   | PEM string                 |
 | `AWM_SERVER_CERT_ALLOW_SELF_SIGNED` | Allow self-signed AWM server certificates | Boolean (default: `false`) |
 
-**For Advanced Wallet Manager → Key Provider:**
+**For Advanced Wallet Manager → key provider:**
 
 | Variable                                    | Description                                        | Format                     |
 | ------------------------------------------- | -------------------------------------------------- | -------------------------- |
 | `KEY_PROVIDER_CLIENT_TLS_KEY_PATH`           | Client private key file path                       | File path                  |
 | `KEY_PROVIDER_CLIENT_TLS_KEY`                | Client private key (alternative)                   | PEM string                 |
 | `KEY_PROVIDER_CLIENT_TLS_CERT_PATH`          | Client certificate file path                       | File path                  |
 | `KEY_PROVIDER_CLIENT_TLS_CERT`               | Client certificate (alternative)                   | PEM string                 |
-| `KEY_PROVIDER_SERVER_CA_CERT_PATH`           | key provider server CA certificate file path       | File path                  |
-| `KEY_PROVIDER_SERVER_CA_CERT`                | key provider server CA certificate (alternative)   | PEM string                 |
+| `KEY_PROVIDER_SERVER_CA_CERT_PATH`           | Key provider server CA certificate file path       | File path                  |
+| `KEY_PROVIDER_SERVER_CA_CERT`                | Key provider server CA certificate (alternative)   | PEM string                 |
 | `KEY_PROVIDER_SERVER_CERT_ALLOW_SELF_SIGNED` | Allow self-signed key provider server certificates | Boolean (default: `false`) |
 
 > **Note:** For security reasons, when `TLS_MODE=mtls`, outbound client certificates are required and cannot reuse server certificates. When `TLS_MODE=disabled`, these certificates aren't required.
@@ -351,7 +351,7 @@ The setup creates two distinct networks:
 ### Prerequisites
 
 1. **Install Docker and Docker Compose**
-2. **Ensure your Key Provider API implementation is running** on your host machine (typically on port 3000)
+2. **Ensure your key provider API implementation is running** on your host machine (typically on port 3000)
 
 ### Quick Start
 

demo-key-provider-script/aws-interface.md

@@ -1,10 +1,10 @@
 # AWS HSM Key Provider Implementation Documentation
 
-This document provides a reference implementation for integrating the 4 Key Provider API's with AWS HSM, covering the complete request-response flow from API handlers to HSM operations.
+This document provides a reference implementation for integrating the 4 key provider API's with AWS HSM, covering the complete request-response flow from API handlers to HSM operations.
 
 ## ⚠️ Security Recommendation
 
-For production key provider implementations, consider implementing the Key Provider API in a C++ like language, because JavaScript does not support low-level memory management. Depending on your solution, direct memory management with explicit memory allocation/deallocation might be desirable.
+For production key provider implementations, consider implementing the key provider API in a C++ like language, because JavaScript does not support low-level memory management. Depending on your solution, direct memory management with explicit memory allocation/deallocation might be desirable.
 
 Also consider implementing low level cryptographic operations using low-level languages like C++ or Rust. They typically provide easier and more efficient data manipulation and transaformation.
 
@@ -14,7 +14,7 @@ When working with AWS HSM, adhere to their guidances and best practices for the
 
 ## API Overview
 
-The Key Provider API provides secure key management through four main endpoints that integrate with AWS HSM:
+The key provider API provides secure key management through four main endpoints that integrate with AWS HSM:
 
 - `POST /key` - Store private keys using envelope encryption
 - `GET /key/{pub}` - Retrieve private keys using envelope decryption  
@@ -25,10 +25,10 @@ The Key Provider API provides secure key management through four main endpoints
 All 4 API's implementation should follow roughly the same dataflow as outlined bellow:
 
 ```
-API Request → Handler → Key Provider → AWS HSM → Key Provider → Database (if required) → Response
+API Request → Handler → key provider → AWS HSM → key provider → Database (if required) → Response
 ```
 
-A Key Provider is the implementation of the code that is in charge of making the necessary calls to the HSM directly. You might have multiple providers in your solution, one for each 3rd party HSM that you wish to use, for example.
+A key provider is the implementation of the code that is in charge of making the necessary calls to the HSM directly. You might have multiple providers in your solution, one for each 3rd party HSM that you wish to use, for example.
 
 ### Handler-to-Provider Mapping
 
@@ -67,7 +67,7 @@ The 3 levels consist of the root-level key from the KMS/HSM, 2nd level data keys
 
 ### Root Key Creation
 
-This following needs to be only run once. The Key Provider should be functional with just one root-level key.
+This following needs to be only run once. The key provider should be functional with just one root-level key.
 
 ```typescript
 import * as awskms from '@aws-sdk/client-kms';

demo-key-provider-script/dinamo-interface.md

@@ -2,15 +2,15 @@
 
 ## ⚠️ Security Recommendation
 
-**For production key provider implementations, consider implementing the Key Provider API in a C++ like language, or use typed arrays like Uint8Array for all sensitive data because JavaScript does not support secure memory management.**
+**For production key provider implementations, consider implementing the key provider API in a C++ like language, or use typed arrays like Uint8Array for all sensitive data because JavaScript does not support secure memory management.**
 
 **Recommended Alternatives:**
 - **C++/Rust**: Languages with explicit memory management and secure allocation
 - **Node.js Typed Arrays**: Use `Uint8Array` for sensitive data with explicit zeroing
 - **Native Addons**: Implement cryptographic operations in native C++ modules
 - **Hardware Security**: Use HSM-backed secure memory when available
 
-This document provides a reference implementation for integrating the 4 Key Provider API's with Dinamo HSM, covering the complete request-response flow from API handlers to HSM operations.
+This document provides a reference implementation for integrating the 4 key provider API's with Dinamo HSM, covering the complete request-response flow from API handlers to HSM operations.
 
 ## Demo Scripts
 
@@ -20,7 +20,7 @@ This document provides a reference implementation for integrating the 4 Key Prov
 
 ## Quick Overview
 
-The Key Provider API provides secure key management through four main endpoints that integrate with Dinamo HSM:
+The key provider API provides secure key management through four main endpoints that integrate with Dinamo HSM:
 
 - `POST /key` - Store private keys using envelope encryption
 - `GET /key/{pub}` - Retrieve private keys using envelope decryption  
@@ -30,7 +30,7 @@ The Key Provider API provides secure key management through four main endpoints
 ## Architecture Flow
 
 ```
-API Request → Handler → Key Provider → Dinamo HSM → Database → Response
+API Request → Handler → key provider → Dinamo HSM → Database → Response
 ```
 
 ### Handler-to-Provider Mapping

docker-compose.yml

@@ -22,7 +22,7 @@ services:
       - TLS_MODE=disabled
       - CLIENT_CERT_ALLOW_SELF_SIGNED=true
 
-      # key provider settings (required)
+      # Key provider settings (required)
       - KEY_PROVIDER_URL=http://172.20.0.1:3000 # UPDATE TO YOUR OWN key provider URL
       - KEY_PROVIDER_SERVER_CERT_ALLOW_SELF_SIGNED=true
 

key-provider-api-spec.yaml

@@ -7,11 +7,11 @@ info:
     # API Interface for Advanced Wallet Integration
 
     This specification defines the required API interface that must be implemented by clients to integrate
-    their KMS/HSM provider with advanced wallets through the Advanced Wallets Key Provider interface.
+    their KMS/HSM provider with advanced wallets through the advanced wallets key provider interface.
 
     ## Purpose
 
-    Clients must implement this Advanced Wallets Key Provider API specification to enable secure cryptographic key storage and management
+    Clients must implement this advanced wallets key provider API specification to enable secure cryptographic key storage and management
     for advanced wallets. The implementation should connect to your organization's KMS/HSM provider.
 
     ## Implementation Requirements