Fixes typos, hides CI integration and simplifies overview section

Author: shirolk

_data/docs_nav.yml

@@ -34,8 +34,8 @@
       url: /docs/core-concepts/navigating-openchoreo/
 - title: Integrating with OpenChoreo
   children:
-    - title: CI Integration
-      url: /docs/integrating-with-openchoreo/ci-integration/
+    # - title: CI Integration
+    #   url: /docs/integrating-with-openchoreo/ci-integration/
     - title: GitOps
       url: /docs/integrating-with-openchoreo/gitops/
 - title: Reference

docs/core-concepts/navigating-openchoreo.md

@@ -238,10 +238,10 @@ Developers use OpenChoreo's abstractions to focus on application logic while the
      deploymentPipelineRef: "standard-pipeline"
    ```
 
-2. **Define ComponentV2** - Create deployable units
+2. **Define Component** - Create deployable units
    ```yaml
    apiVersion: choreo.dev/v1alpha1
-   kind: ComponentV2
+   kind: Component
    spec:
      componentOwner:
        projectRef: "payment-service"
@@ -264,8 +264,8 @@ Developers use OpenChoreo's abstractions to focus on application logic while the
 **Objective**: Transform source code into deployable artifacts
 
 **Workflow Steps**:
-1. **Build Execution** - Automatic BuildV2 creation from ComponentV2
-   - ComponentV2 specifications trigger BuildV2 resource creation
+1. **Build Execution** - Automatic Build creation from Component
+   - Component specifications trigger Build resource creation
    - Argo Workflows execute builds on dedicated BuildPlanes
    - Support for Docker and Buildpack build strategies
    - Build status tracking and logging through Observer API

docs/overview/what-is-openchoreo.md

@@ -99,35 +99,15 @@ The platform team defines the rules (networking, security, observability, and op
 
 ## Architecture Philosophy
 
-OpenChoreo is built on several key architectural principles:
-
-### **Declarative Everything**
-All platform state is declared through YAML configurations, enabling:
-- Version control and audit trails
-- Reproducible environments
-- Automated reconciliation
-- GitOps workflows
-
-### **Kubernetes Native**
-Built as a set of Kubernetes operators that:
-- Extend the Kubernetes API
-- Follow cloud-native patterns
-- Integrate with the CNCF ecosystem
-- Provide familiar operational models
-
-### **Composable Platform**
-Modular architecture allows organizations to:
-- Adopt incrementally
-- Customize components
-- Integrate existing tools
-- Evolve platform capabilities
-
-### **Open Source First**
-Community-driven development ensures:
-- Transparency and trust
-- Vendor neutrality
-- Extensibility and customization
-- Collaborative innovation
+OpenChoreo is built on key architectural principles that ensure reliability, flexibility, and ease of adoption.
+
+**Declarative Everything**: All platform state is declared through YAML configurations, enabling version control, reproducible environments, automated reconciliation, and GitOps workflows.
+
+**Kubernetes Native**: Built as Kubernetes operators that extend the API, follow cloud-native patterns, integrate with CNCF ecosystem, and provide familiar operational models.
+
+**Composable Platform**: Modular architecture allows incremental adoption, component customization, existing tool integration, and platform capability evolution.
+
+**Open Source First**: Community-driven development ensures transparency, vendor neutrality, extensibility, and collaborative innovation.
 
 ## Technology Stack