From 4d9124c009a09bd19817948847627a563706fc51 Mon Sep 17 00:00:00 2001
From: Herman Slatman <hermanslatman@hotmail.com>
Date: Mon, 17 Feb 2025 13:13:35 +0100
Subject: [PATCH] Consistently use `my_scep_provisioner` in SCEP provisioner
 example

---
 step-ca/provisioners.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/step-ca/provisioners.mdx b/step-ca/provisioners.mdx
index d4eea8e2..87ce00cb 100644
--- a/step-ca/provisioners.mdx
+++ b/step-ca/provisioners.mdx
@@ -1285,7 +1285,7 @@ Here's an example of a SCEP provisioner in `$(step path)/config/ca.json`:
 ```json
 {
     "type": "SCEP",
-    "name": "scepca",
+    "name": "my_scep_provisioner",
     "forceCN": true,
     "challenge": "secret1234",
     "minimumPublicKeyLength": 2048,
@@ -1323,7 +1323,7 @@ Enable this by filling in the `"insecureAddress"` property to your top-level CA
 ```
 
 Finally, restart `step-ca`.
-Your SCEP provisioner is now available at the endpoint `http://ca.example.com:8080/scep/scepca`.
+Your SCEP provisioner is now available at the endpoint `http://ca.example.com:8080/scep/my_scep_provisioner`.
 
 <Alert severity="info">
   <div>