fixes

Author: aantn

docs/configuration/alertmanager-integration/alert-custom-prometheus.rst

@@ -8,11 +8,10 @@ Create Custom Prometheus Alerts
 You can define new alerts in two ways using Robusta:
 
 1. Prometheus Alerts - Using PromQL
-2. Robusta Playbooks - Using :ref:`customPlaybooks YAML <What are Playbooks?>`
+2. Robusta Playbooks - Using :ref:`customPlaybooks YAML <Playbook Basics>`
 
 These methods are not mutually exclusive. Robusta playbooks can respond to Prometheus alerts, or they can generate
-alerts themselves by listening directly to the Kubernetes APIServer. To better understand the trade-offs, refer to
-:ref:`Should I generate alerts with Robusta or with Prometheus? <robusta-or-prometheus-alerts>`
+alerts themselves by listening directly to the Kubernetes APIServer.
 
 In this tutorial, we use the first method to generate a custom Prometheus alert using PromQL. In the next tutorial,
 we define a custom Robusta playbook that enhances the alert and makes it better.
@@ -109,4 +108,4 @@ Next Steps
 
 Learn how to enrich Prometheus alerts with more context, so that you can respond faster:
 
-* :ref:`Prometheus Alert Enrichment`
+* :ref:`Alert Enrichment <builtin-alert-enrichment>`

docs/configuration/holmesgpt/getting-started.rst

@@ -142,6 +142,8 @@ Instead of Robusta AI, you can use your own OpenAI, Azure, or AWS Bedrock accoun
                     name: holmes-secrets
                     key: awsSecretAccessKey
 
+.. _Reading the Robusta UI Token from a secret in HolmesGPT:
+
 Using Existing Secrets
 ----------------------
 

docs/configuration/resource-recommender.rst

@@ -1,13 +1,13 @@
 Cost Savings (KRR)
 ************************************************************
 
-Robustas `KRR <https://github.com/robusta-dev/krr>`_ is a CLI tool for optimizing resource allocation in Kubernetes clusters.
-It gathers pod usage data from Prometheus and recommends requests and limits for CPU and memory. This reduces costs and improves performance.
+`KRR <https://github.com/robusta-dev/krr>`_ is a CLI tool that optimizes resource allocation in Kubernetes clusters.
+It gathers pod usage data from Prometheus and recommends requests and limits for CPU and memory, reducing costs and improving performance.
 
-By optionally integrating KRR with Robusta you can:
+Robusta can run KRR scans on a :ref:`schedule <Scheduled>` using playbooks. Because KRR is so popular, it has dedicated documentation here. You can:
 
-1. Get weekly KRR scan reports in Slack via Robusta OSS (disabled by default, see below to configure)
-2. View KRR scans from all your clusters in the Robusta UI (enabled by default for UI users)
+1. Send weekly scan reports to Slack or other sinks via Robusta OSS (disabled by default, configure below)
+2. View scans from all your clusters in the Robusta UI (enabled by default for UI users)
 
 
 Sending Weekly KRR Scan Reports to Slack

docs/help.rst

@@ -250,7 +250,7 @@ Holmes
 
         It's often because the ``Robusta UI Token`` is pulled from a secret, and Holmes cannot read it.
 
-        See :ref:`Reading the Robusta UI Token from a secret in HolmesGPT` to configure Holmes to read the ``token``
+        See :ref:`Using Existing Secrets <Reading the Robusta UI Token from a secret in HolmesGPT>` to configure Holmes to read the ``token``
 
 Phase 4: Integration Issues
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^

docs/how-it-works/coverage.rst

@@ -20,7 +20,7 @@ Prometheus Alerts
 
 .. warning::
 
-    You must :ref:`send your Prometheus alerts to Robusta by webhook <Integrating with Prometheus>` for these to work.
+    You must send your Prometheus alerts to Robusta by webhook for these to work. See :doc:`AlertManager Integration </configuration/alertmanager-integration/index>`.
 
 Other errors
 ----------------
@@ -39,8 +39,7 @@ Change Tracking
 By default all changes to Deployments, DaemonSets, and StatefulSets are sent to the Robusta UI for correlation
 with Prometheus alerts and other errors.
 
-These changes are not sent to other sinks (e.g. Slack) by default because they are spammy. :ref:`Routing Cookbook`
-explains how to selectively track changes you care about in Slack as well.
+These changes are not sent to other sinks (e.g. Slack) by default because they are spammy. See :doc:`Notification Routing </notification-routing/index>` to learn how to selectively track changes you care about in Slack as well.
 
 We also wrote a blog post `Why everyone should track Kubernetes changes and top four ways to do so <https://home.robusta.dev/blog/why-everyone-should-track-and-audit-kubernetes-changes-and-top-ways/>`_
 

docs/index.rst

@@ -147,9 +147,9 @@
    Playbook Notifications <playbook-reference/defining-playbooks/creating-notifications>
    Alert Enrichment <playbook-reference/builtin-alert-enrichment>
    Automatic Remediation <playbook-reference/automatic-remediation-examples/index>
+   Change Tracking Playbooks <playbook-reference/kubernetes-examples/kubernetes-change-notifications>
    Silencer Playbooks <playbook-reference/defining-playbooks/silencer-playbooks>
    Log Based Alerting <playbook-reference/logs-triggers/index>
-   K8s Change Notification <playbook-reference/kubernetes-examples/kubernetes-change-notifications>
    Cost Savings - KRR <configuration/resource-recommender>
    Triggers Reference <playbook-reference/triggers/index>
    Actions Reference <playbook-reference/actions/index>

docs/notification-routing/configuring-sinks.rst

@@ -9,7 +9,7 @@ A Simple Sink Configuration
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 Sinks are defined in Robusta's Helm chart, using the ``sinksConfig`` value.
 
-For example, lets add a :ref:`Microsoft Teams Sink <MS Teams sink>`:
+For example, lets add a :ref:`Microsoft Teams Sink <MS Teams>`:
 
 .. code-block:: yaml
 

docs/notification-routing/index.rst

@@ -68,7 +68,7 @@ Popular Sinks
 
     .. grid-item-card:: PagerDuty
         :class-card: sd-bg-light sd-bg-text-light
-        :link: ../configuration/sinks/pagerduty
+        :link: ../configuration/sinks/PagerDuty
         :link-type: doc
 
     .. grid-item-card:: View All Sinks

docs/playbook-reference/kubernetes-examples/kubernetes-change-notifications.rst

@@ -1,4 +1,4 @@
-K8s Change Notification
+Change Tracking Playbooks
 ################################
 
 You can configure Robusta to send push notifications when Kubernetes resources change or become unhealthy. This is done by listening to API Server changes with `kubewatch <https://github.com/robusta-dev/kubewatch/>`_ and then filtering the stream of events in a Robusta playbook.

docs/playbook-reference/triggers/kubernetes.rst

@@ -9,7 +9,7 @@ These triggers work even when Prometheus is not connected to Robusta. They're tr
 
 .. details:: Related Tutorials
 
-    * :doc:`K8s Change Notification </playbook-reference/kubernetes-examples/kubernetes-change-notifications>`
+    * :doc:`Change Tracking Playbooks </playbook-reference/kubernetes-examples/kubernetes-change-notifications>`
 
 
 Crashing Pod Triggers