[EN] update GitOps (#2121)

Signed-off-by: Nate W <[email protected]>
Signed-off-by: Noah Ispas <[email protected]>
Co-authored-by: Nate W <[email protected]>
Co-authored-by: Hilliary Lipsig <[email protected]>
Co-authored-by: Noah Ispas <[email protected]>

Author: 4 people

content/en/gitops.md

@@ -1,29 +1,28 @@
 ---
 title: GitOps
-status: Feedback Appreciated
+status: Completed
 category: Concept
 tags: ["methodology", "", ""]
 ---
 
-GitOps is a set of best practices based on [shared principles](https://opengitops.dev/), 
-applied to a workflow that depends on software agents that 
-enable automation to reconcile a declared system state or configuration in a git repository.
-These software agents and practices are used to execute a cohesive workflow that 
-leverages a source control system like Git as the “single source of truth” and 
-extends this practice to applications, infrastructure, and operational procedures.
+GitOps is a set of practices for managing software applications and infrastructure by continuously evaluating 
+and reconciling their desired states as defined in a version control system such as Git against their actual state. 
+Reconciling states includes changing the resources to match the defined state via deployment or updates.
+
+In GitOps, the state or configuration of a system is fully described in files stored in the source of truth, usually the version control system. 
+It could, however, be another source of truth, such as a Kubernetes Operator or Artifact Storage.
+The source of truth is evaluated by the automated processes that align the live system with the defined state. 
+These processes adjust the live system as needed, ensuring consistency across applications, infrastructure, and operational tasks.
 
 ## Problem it addresses
 
-Existing processes for infrastructure configuration management can face challenges 
-such as configuration drift, failed deployments, relying on a system's previous state for success, 
-missing documentation, or unknown development history.
-Adopting a GitOps workflow can help alleviate these issues, among several others.
+Traditional approaches to managing infrastructure and application configurations can result in configuration drift, failed deployments, inconsistent environments, deployment failures, and difficulty tracking historical changes.
+These issues can cause instability and increase maintenance overhead.
+Configuration drift can be hard to detect and resolve without a source of truth governing it, increasing the time to resolve outages or failures. 
 
 ## How it helps
 
-GitOps is a paradigm that can be applied to a workflow 
-to help manage an application and cloud system infrastructure. 
-It enables organizations several advantages 
-such as better coordination, transparency, stability, and reliability of a system.
-Operating in a close loop ensures the current live state of a system matches 
-against the desired target state, specified in the git repository.
+GitOps helps organizations manage the entire infrastructure, application development, and deployment lifecycle using a single and unified process.
+
+GitOps brings organizations several other advantages, such as transparency and traceability of changes, reliability 
+and security through declarative states, and rollback, revert, and self-healing attributes.