[Docs] Fix 404s/broken links in main branch (#10556)

Cleaning up broken links reported against the main branch.

---------

Co-authored-by: Jack Baldry <jack.baldry@grafana.com>

docs/sources/setup/install/helm/monitor-and-alert/with-grafana-cloud.md

@@ -19,13 +19,13 @@ This topic will walk you through using Grafana Cloud to monitor a Loki installat
 **Before you begin:**
 
 - Helm 3 or above. See [Installing Helm](https://helm.sh/docs/intro/install/).
-- A Grafana Cloud account and stack (including Cloud Grafana, Cloud Metrics, and Cloud Logs)
-- [Grafana Kubernetes Monitoring using Agent](/docs/grafana-cloud/monitor-infrastructure/kubernetes-monitoring/configuration/) configured for the Kubernetes cluster
-- A running Loki deployment installed in that Kubernetes cluster via the Helm chart
+- A Grafana Cloud account and stack (including Cloud Grafana, Cloud Metrics, and Cloud Logs).
+- [Grafana Kubernetes Monitoring using Agent Flow](/docs/grafana-cloud/monitor-infrastructure/kubernetes-monitoring/configuration/config-k8s-agent-flow/) configured for the Kubernetes cluster.
+- A running Loki deployment installed in that Kubernetes cluster via the Helm chart.
 
 **Prequisites for Monitoring Loki:**
 
-You must setup the Grafana Kubernetes Integration following the instructions in [Grafana Kubernetes Monitoring using Agent](/docs/grafana-cloud/monitor-infrastructure/kubernetes-monitoring/configuration/) as this will install necessary components for collecting metrics about your Kubernetes cluster and sending them to Grafana Cloud. Many of the dashboards installed as a part of the Loki integration rely on these metrics.
+You must setup the Grafana Kubernetes Integration following the instructions in [Grafana Kubernetes Monitoring using Agent Flow](/docs/grafana-cloud/monitor-infrastructure/kubernetes-monitoring/configuration/config-k8s-agent-flow/) as this will install necessary components for collecting metrics about your Kubernetes cluster and sending them to Grafana Cloud. Many of the dashboards installed as a part of the Loki integration rely on these metrics.
 
 Walking through this installation will create two Grafana Agent configurations, one for metrics and one for logs, that will add the external label `cluster: cloud`. In order for the Dashboards in the self-hosted Grafana Loki integration to work, the cluster name needs to match your Helm installation name. If you installed Loki using the command `helm install best-loki-cluster grafana/loki`, you would need to change the `cluster` value in both Grafana Agent configurations from `cloud` to `best-loki-cluster` when setting up the Grafana Kubernetes integration.