From 332eabe8d75f95fdfbfb78789852d299ae0118c1 Mon Sep 17 00:00:00 2001
From: Aniket Shitole <91371143+AniketNS@users.noreply.github.com>
Date: Sun, 4 Feb 2024 15:54:47 +0530
Subject: [PATCH] Modified ldap.md for issue #937 (#951)

---
 .../en/docs/Getting Started/v0.7.x/ldap.md    | 49 +++++++++----------
 1 file changed, 24 insertions(+), 25 deletions(-)

diff --git a/website/content/en/docs/Getting Started/v0.7.x/ldap.md b/website/content/en/docs/Getting Started/v0.7.x/ldap.md
index ca2b1179a..b745caf86 100644
--- a/website/content/en/docs/Getting Started/v0.7.x/ldap.md	
+++ b/website/content/en/docs/Getting Started/v0.7.x/ldap.md	
@@ -77,31 +77,30 @@ data:
           userIdStrategy: "caseInsensitive"
 ```
 
-> Note the use of `${LDAP_MANAGER_PASSWORD}` above. You can reference
-> Kubernetes secrets in your JCasC ConfigMaps by adding the following to your
-> Jenkins object:
->
-> ```yaml
-> kind: Jenkins
-> spec:
->   configurationAsCode:
->     configurations:
->       - name: jenkins-casc
->     secret:
->       # This here
->       name: jenkins-casc-secrets
-> ```
->
-> ```yaml
-> apiVersion: v1
-> kind: Secret
-> metadata:
->   name: jenkins-cred-conf-secrets
-> stringData:
->   LDAP_MANAGER_PASSWORD: <password-for-manager-created-in-ldap>
-> ```
->
-> Schema reference: [v1alpha2.ConfigurationAsCode](./schema/#github.com/jenkinsci/kubernetes-operator/pkg/apis/jenkins/v1alpha2.ConfigurationAsCode)
+>Note the use of `${LDAP_MANAGER_PASSWORD}` above. You can reference
+>Kubernetes secrets in your JCasC ConfigMaps by adding the following to your
+
+Jenkins object:
+
+```yaml
+kind: Jenkins
+spec:
+  configurationAsCode:
+    configurations:
+      - name: jenkins-casc
+    secret:
+      # This here
+      name: jenkins-casc-secrets
+```
+```yaml
+apiVersion: v1
+kind: Secret
+metadata:
+  name: jenkins-cred-conf-secrets
+stringData:
+  LDAP_MANAGER_PASSWORD: <password-for-manager-created-in-ldap>
+```
+Schema reference: [v1alpha2.ConfigurationAsCode](./schema/#github.com/jenkinsci/kubernetes-operator/pkg/apis/jenkins/v1alpha2.ConfigurationAsCode)
 
 Finally you must configure the Jenkins operator to use the manager's
 credentials from the AD.