From 4e087df473c58a2e9cffe0a938641ce1a478239a Mon Sep 17 00:00:00 2001 From: Anuj Singh <30765911+underscoreanuj@users.noreply.github.com> Date: Thu, 31 Oct 2019 10:40:33 +0530 Subject: [PATCH] Update customization.md --- .../content/en/docs/Getting Started/v0.1.x/customization.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/content/en/docs/Getting Started/v0.1.x/customization.md b/website/content/en/docs/Getting Started/v0.1.x/customization.md index 611d7361..ce113ef9 100644 --- a/website/content/en/docs/Getting Started/v0.1.x/customization.md +++ b/website/content/en/docs/Getting Started/v0.1.x/customization.md @@ -7,12 +7,12 @@ description: > How to customize Jenkins --- -Jenkins can be customized using by groovy scripts or the Jenkins Configuration as Code Plugin. All custom configuration is stored in +Jenkins can be customized by using groovy scripts or the Jenkins Configuration as a Code Plugin. All custom configuration is stored in the **jenkins-operator-user-configuration-** ConfigMap, which is automatically created by the **Jenkins Operator**. The **Jenkins Operator** creates a **jenkins-operator-user-configuration-** secret where the user can store sensitive information used for custom configuration. If you have an entry in the secret named `PASSWORD` then you can use it in the -Jenkins Configuration as Code Plugin as `adminAddress: "${PASSWORD}"`. +Jenkins Configuration as a Code Plugin as `adminAddress: "${PASSWORD}"`. ``` kubectl get secret jenkins-operator-user-configuration- -o yaml