address minor comments

Signed-off-by: Arvind Thirumurugan <arvindth@microsoft.com>

Author: Arvind Thirumurugan

approval-controller-metric-collector/README.md

@@ -32,7 +32,7 @@ This solution introduces three new CRDs that work together with KubeFleet's nati
 3. **ClusterStagedWorkloadTracker** (cluster-scoped)
    - Defines which workloads to monitor for a ClusterStagedUpdateRun
    - The name must match the ClusterStagedUpdateRun name
-   - Specifies namespace, workload name, and expected health status
+   - Specifies workload's name, namespace and expected health status
    - Used by approval-request-controller to determine if stage is ready for approval
 
 4. **StagedWorkloadTracker** (namespaced)
@@ -49,7 +49,7 @@ This solution introduces three new CRDs that work together with KubeFleet's nati
    - The ApprovalRequest enters "Pending" state, waiting for approval
 
 2. **Metric Collector Deployment**
-   - Approval-request-controller watches the CAR
+   - Approval-request-controller watches the `ClusterApprovalRequest`, `ApprovalRequest` objects
    - Creates a `MetricCollector` resource on the hub (cluster-scoped)
    - Creates a `ClusterResourceOverride` with per-cluster customization rules
      - Each cluster gets a unique `reportNamespace`: `fleet-member-<cluster-name>`
@@ -295,14 +295,13 @@ Output:
 ```bash
 NAME              GEN   SCHEDULED   SCHEDULED-GEN   AVAILABLE   AVAILABLE-GEN   AGE
 ns-only-crp       1     True        1               True        1               5s
-proemetheus-crp   1     True        1               True        1               2m34s
+prometheus-crp   1     True        1               True        1               2m34s
 ```
 
 ```bash
 # Apply StagedUpdateStrategy
 kubectl apply -f ./examples/updateRun/example-sus.yaml
 
-```bash
 # Apply ResourcePlacement
 kubectl apply -f ./examples/updateRun/example-rp.yaml
 
@@ -389,13 +388,6 @@ fleet-member-kind-cluster-1   mc-example-staged-run-staging   1           27s
 ```
 
 The approval controller will automatically approve stages when the metric collectors report that workloads are healthy.
-1. Builds the `metric-collector:latest` image
-2. Builds the `metric-app:local` image
-3. Loads both images into each kind cluster
-4. Creates hub token secret with proper RBAC
-5. Installs the metric-collector via Helm
-
-The `metric-app:local` image is pre-loaded so it's available when you propagate the sample-metric-app deployment from hub to member clusters.
 
 ## Verification
 

approval-controller-metric-collector/approval-request-controller/apis/metric/v1alpha1/metriccollector_types.go

@@ -64,7 +64,7 @@ type MetricCollectorSpec struct {
 	ReportNamespace string `json:"reportNamespace"`
 }
 
-// MetricsEndpointSpec defines how to access the metrics endpoint.ctor.
+// MetricCollectorStatus defines the observed state of MetricCollector.
 type MetricCollectorStatus struct {
 	// Conditions is an array of current observed conditions.
 	// +optional

approval-controller-metric-collector/approval-request-controller/examples/prometheus/prometheus-crp.yaml

@@ -1,7 +1,7 @@
 apiVersion: placement.kubernetes-fleet.io/v1beta1
 kind: ClusterResourcePlacement
 metadata:
-  name: proemetheus-crp
+  name: prometheus-crp
 spec:
   resourceSelectors:
     - group: ""