From 785ae326bb207b1445077f7facc0a895550c976c Mon Sep 17 00:00:00 2001
From: Ben Moskovitz <ben.m@buildkite.com>
Date: Fri, 24 Nov 2023 14:10:15 +1100
Subject: [PATCH] keyset -> key set

---
 pages/agent/v3/signed_pipelines.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/pages/agent/v3/signed_pipelines.md b/pages/agent/v3/signed_pipelines.md
index b11603cdb5..62049bd20b 100644
--- a/pages/agent/v3/signed_pipelines.md
+++ b/pages/agent/v3/signed_pipelines.md
@@ -98,9 +98,9 @@ buildkite-agent tool keygen --help
 Next, you need to configure your agents to use the keys you generated. On agents that upload pipelines, add the following to the agent's config file:
 
 ```ini
-signing-jwks-file=<path to private keyset>
+signing-jwks-file=<path to private key set>
 signing-jwks-key-id=<the key id you generated earlier>
-verification-jwks-file=<path to public keyset>
+verification-jwks-file=<path to public key set>
 ```
 
 This ensures that whenever those agents upload steps to Buildkite, they'll generate signatures using the private key you generated earlier. It also ensures that those agents verify the signatures of any steps they run, using the public key.
@@ -133,7 +133,7 @@ buildkite-agent tool sign \
 Replacing the following:
 
 - `<token>` with a Buildkite GraphQL token that has the `write_pipelines` scope.
-- `<path to signing jwks>` with the path to the private keyset you generated earlier.
+- `<path to signing jwks>` with the path to the private key set you generated earlier.
 - `<signing key id>` with the key ID from earlier.
 - `<org slug>` with the slug of the organization the pipeline is in.
 - `<pipeline slug>` with the slug of the pipeline you want to sign.