diff --git a/website/content/en/docs/How it works/_index.md b/website/content/en/docs/How it works/_index.md index 247dcf33..86e8999b 100644 --- a/website/content/en/docs/How it works/_index.md +++ b/website/content/en/docs/How it works/_index.md @@ -8,6 +8,6 @@ description: > --- {{% pageinfo %}} -This document describes a high level overview how jenkins-operator works. +This document describes a high level overview of how jenkins-operator works. {{% /pageinfo %}} diff --git a/website/content/en/docs/How it works/architecture-and-design.md b/website/content/en/docs/How it works/architecture-and-design.md index dda2cc01..c9434c7d 100644 --- a/website/content/en/docs/How it works/architecture-and-design.md +++ b/website/content/en/docs/How it works/architecture-and-design.md @@ -17,7 +17,7 @@ The **Jenkins Operator** design incorporates the following concepts: **Base** reconciliation loop takes care of reconciling base Jenkins configuration, which consists of: - Ensure Manifests - monitors any changes in manifests -- Ensure Jenkins Pod - creates and verifies status of Jenkins master Pod +- Ensure Jenkins Pod - creates and verifies the status of Jenkins master Pod - Ensure Jenkins Configuration - configures Jenkins instance including hardening, initial configuration for plugins, etc. - Ensure Jenkins API token - generates Jenkins API token and initialized Jenkins client @@ -26,12 +26,12 @@ The **Jenkins Operator** design incorporates the following concepts: - Ensure Restore Job - creates Restore job and ensures that restore has been successfully performed - Ensure Seed Jobs - creates Seed Jobs and ensures that all of them have been successfully executed - Ensure User Configuration - executed user provided configuration, like groovy scripts, configuration as code or plugins -- Ensure Backup Job - creates Backup job and ensures that backup has been successfully performed +- Ensure Backup Job - creates a Backup job and ensures that backup has been successfully performed ![reconcile](/kubernetes-operator/img/phases.png) ## Operator State -Operator state is kept in custom resource status section, which is used for storing any configuration events or job statuses managed by the operator. +Operator state is kept in the custom resource status section, which is used for storing any configuration events or job statuses managed by the operator. -It helps to maintain or recover desired state even after operator or Jenkins restarts. +It helps to maintain or recover the desired state even after the operator or Jenkins restarts.