diff --git a/website/content/en/docs/Getting Started/latest/customization-with-groovy-scripts-and-casc.md b/website/content/en/docs/Getting Started/latest/customizing-jenkins.md
similarity index 98%
rename from website/content/en/docs/Getting Started/latest/customization-with-groovy-scripts-and-casc.md
rename to website/content/en/docs/Getting Started/latest/customizing-jenkins.md
index 08cac592..994baa6b 100644
--- a/website/content/en/docs/Getting Started/latest/customization-with-groovy-scripts-and-casc.md	
+++ b/website/content/en/docs/Getting Started/latest/customizing-jenkins.md	
@@ -1,6 +1,6 @@
 ---
-title: "Customization with Groovy Scripts and CasC"
-linkTitle: "Customization with Groovy Scripts and CasC"
+title: "Customizing Jenkins"
+linkTitle: "Customizing Jenkins"
 weight: 3
 date: 2021-08-19
 description: >
diff --git a/website/content/en/docs/Getting Started/latest/installing-the-operator.md b/website/content/en/docs/Getting Started/latest/installing-the-operator.md
index 27012aad..6a556485 100644
--- a/website/content/en/docs/Getting Started/latest/installing-the-operator.md	
+++ b/website/content/en/docs/Getting Started/latest/installing-the-operator.md	
@@ -43,7 +43,7 @@ kubectl get pods -w
 ```
 
 Now **Jenkins Operator** should be up and running in the `default` namespace.
-For deploying Jenkins, refer to [Deploy Jenkins section](/kubernetes-operator/docs/getting-started/latest/deploy-jenkins/).
+For deploying Jenkins, refer to [Deploy Jenkins section](/kubernetes-operator/docs/getting-started/latest/deploying-jenkins/).
 
 ## Deploy Jenkins Operator using Helm Chart
 
@@ -296,8 +296,8 @@ plugins:
 </td>
 <td>
 Placeholder for jenkins seed jobs
-For seed job creation tutorial, check:<br /> <a href="https://jenkinsci.github.io/kubernetes-operator/docs/getting-started/latest/configuration/#prepare-job-definitions-and-pipelines">Prepare seed jobs</a>
-<br /><a href="https://jenkinsci.github.io/kubernetes-operator/docs/getting-started/latest/configuration/#configure-seed-jobs">Configure seed jobs</a>
+For seed job creation tutorial, check:<br /> <a href="https://jenkinsci.github.io/kubernetes-operator/docs/getting-started/latest/configuring-seed-jobs-and-pipelines/#prepare-job-definitions-and-pipelines">Prepare seed jobs</a>
+<br /><a href="https://jenkinsci.github.io/kubernetes-operator/docs/getting-started/latest/configuring-seed-jobs-and-pipelines/#configure-seed-jobs">Configure seed jobs</a>
 <br />Example:
 <code>
 <pre>
@@ -442,8 +442,8 @@ Backup
 <td>
 Backup is section for configuring operator's backup feature
 By default backup feature is enabled and pre-configured
-This section simplifies the configuration described here: <a href="https://jenkinsci.github.io/kubernetes-operator/docs/getting-started/latest/configure-backup-and-restore/">Configure backup and restore</a>
-For customization tips see <a href="https://jenkinsci.github.io/kubernetes-operator/docs/getting-started/latest/custom-backup-and-restore/">Custom backup and restore</a>
+This section simplifies the configuration described here: <a href="https://jenkinsci.github.io/kubernetes-operator/docs/getting-started/latest/configuring-backup-and-restore/">Configuring backup and restore</a>
+For customization tips see <a href="https://jenkinsci.github.io/kubernetes-operator/docs/getting-started/latest/custom-backup-and-restore">Custom backup and restore</a>
 </td>
 </tr>
 <tr>
@@ -460,7 +460,7 @@ Configuration
 <td></td>
 <td>
 Section where we can configure Jenkins instance. 
-See <a href="https://jenkinsci.github.io/kubernetes-operator/docs/getting-started/latest/customization/">Customization</a> for details
+See <a href="https://jenkinsci.github.io/kubernetes-operator/docs/getting-started/latest/customizing-jenkins/">Customizing Jenkins</a> for details
 </td>
 </tr>
 </table>
diff --git a/website/content/en/docs/Getting Started/latest/schema.md b/website/content/en/docs/Getting Started/latest/schema.md
index e62a1a8c..d94806c9 100644
--- a/website/content/en/docs/Getting Started/latest/schema.md	
+++ b/website/content/en/docs/Getting Started/latest/schema.md	
@@ -109,7 +109,7 @@ Every single change here requires a pod restart.</p>
 <td>
 <em>(Optional)</em>
 <p>SeedJobs defines list of Jenkins Seed Job configurations
-More info: <a href="https://jenkinsci.github.io/kubernetes-operator/docs/getting-started/latest/configuration#configure-seed-jobs-and-pipelines">https://jenkinsci.github.io/kubernetes-operator/docs/getting-started/latest/configuration#configure-seed-jobs-and-pipelines</a></p>
+More info: <a href="https://jenkinsci.github.io/kubernetes-operator/docs/getting-started/latest/configuring-seed-jobs-and-pipelines#configure-seed-jobs-and-pipelines">https://jenkinsci.github.io/kubernetes-operator/docs/getting-started/latest/configuration#configure-seed-jobs-and-pipelines</a></p>
 </td>
 </tr>
 <tr>
diff --git a/website/content/en/docs/Getting Started/latest/security.md b/website/content/en/docs/Getting Started/latest/security.md
index b2a76260..19a599f3 100644
--- a/website/content/en/docs/Getting Started/latest/security.md	
+++ b/website/content/en/docs/Getting Started/latest/security.md	
@@ -14,7 +14,7 @@ via groovy scripts to prevent any security gaps.
 
 Currently **Jenkins Operator** generates a username and random password and stores them in a Kubernetes Secret.
 However any other authorization mechanisms are possible and can be done via groovy scripts or configuration as code plugin.
-For more information take a look at [getting-started#jenkins-customization](/kubernetes-operator/docs/getting-started/latest/customization/).
+For more information take a look at [getting-started#jenkins-customization](/kubernetes-operator/docs/getting-started/latest/customizing-jenkins/).
 
 Any change to Security Realm or Authorization requires that user called `jenkins-operator` must have admin rights 
 because **Jenkins Operator** calls Jenkins API.
@@ -42,8 +42,8 @@ and stores it in a Kubernetes Secret.
 
 Kubernetes API permissions are limited by the following roles:
 
-- [jenkins-operator role](kubernetes-operator/blob/v0.6.0/deploy/all-in-one-v1alpha2.yaml)  
-- [Jenkins Master role](kubernetes-operator/blob/v0.6.0/pkg/configuration/base/resources/rbac.go)
+- [jenkins-operator role](https://github.com/jenkinsci/kubernetes-operator/blob/v0.6.0/deploy/all-in-one-v1alpha2.yaml)  
+- [Jenkins Master role](https://github.com/jenkinsci/kubernetes-operator/blob/v0.6.0/pkg/configuration/base/resources/rbac.go)
 
 Since **Jenkins Operator** must be able to grant permission for its deployed Jenkins masters 
 to spawn pods (the `Jenkins Master role` above),