diff --git a/docs/sources/_index.md b/docs/sources/_index.md
index 66bdb8ff23..4d8e845699 100644
--- a/docs/sources/_index.md
+++ b/docs/sources/_index.md
@@ -30,7 +30,7 @@ cards:
       description: Learn how to install and configure Grafana Pyroscope with several examples.
     - title: Instrument your app and configure the client
       href: ./configure-client/
-      description: When sending profiles to Pyroscope, you can choose between SDK instrumentation and auto-instrumentation using the Grafana Agent. This document explains these two techniques and guide you when to choose each one.
+      description: When sending profiles to Pyroscope, you can choose between SDK instrumentation and auto-instrumentation using Grafana Alloy. This document explains these two techniques and guide you when to choose each one.
     - title: Configure the server
       href: ./configure-server/
       description: Configure your Pyroscope server to meet your needs by setting disk storage, tenant IDs, memberlist, proxies, shuffle sharding, and more. You can also use the server HTTP API.
@@ -52,8 +52,8 @@ Grafana Pyroscope is a multi-tenant, continuous profiling aggregation system, al
 This integration enables a cohesive correlation of profiling data with existing metrics, logs, and traces.
 
 Explore continuous profiling data to gain insights into application performance.
-You can query and analyze production data in a structure way. 
-Use the Pyroscope UI or Grafana to visualize the data. 
+You can query and analyze production data in a structure way.
+Use the Pyroscope UI or Grafana to visualize the data.
 
 <!--video style="border-radius: 1%; width: 75%; display: block; margin-left: auto; margin-right: auto;" autoplay loop>
   <source src="ui.webm" type="video/webm">
diff --git a/docs/sources/configure-client/_index.md b/docs/sources/configure-client/_index.md
index 16359f44b0..d4721e868d 100644
--- a/docs/sources/configure-client/_index.md
+++ b/docs/sources/configure-client/_index.md
@@ -11,7 +11,7 @@ weight: 300
 # Configure the client to send profiles
 
 Pyroscope is a continuous profiling database that allows you to analyze the performance of your applications.
-When sending profiles to Pyroscope, you can choose between two primary methods: SDK instrumentation and auto-instrumentation using Grafana Alloy or Grafana Agent.
+When sending profiles to Pyroscope, you can choose between two primary methods: SDK instrumentation and auto-instrumentation using Grafana Alloy.
 
 This document explains these two techniques and guide you when to choose each one.
 
@@ -19,7 +19,7 @@ This document explains these two techniques and guide you when to choose each on
 
 ## About auto-instrumentation with Grafana Alloy or Agent collectors
 
-You can send data from your application using Grafana Alloy or Grafana Agent collectors.
+You can send data from your application using Grafana Alloy (preferred) or Grafana Agent (legacy) collectors.
 Both collectors support profiling with eBPF, Java, and Golang in pull mode.
 
 [Grafana Alloy](https://grafana.com/docs/alloy/latest/) is a vendor-neutral distribution of the OpenTelemetry (OTel) Collector.
@@ -31,7 +31,7 @@ New installations should use Alloy.
 
 {{< docs/shared lookup="agent-deprecation.md" source="alloy" version="next" >}}
 
-The Grafana collectors is a component that runs alongside your application and periodically gathers profiling data from it.
+Alloy is a component that runs alongside your application and periodically gathers profiling data from it.
 This method is suitable when you want to collect profiles from existing applications without modifying their source code.
 This approach is simplified with the eBPF profiling option that doesn't necessitate pull or push mechanisms.
 
@@ -57,16 +57,14 @@ Here's how to use Pyroscope SDKs:
 By using the Pyroscope SDKs, you have the flexibility to customize the profiling process according to your application's specific requirements.
 You can selectively profile specific sections of code or send profiles at different intervals, depending on your needs.
 
-## Choose Grafana Agent or Pyroscope SDK to send profiles
+## Choose Grafana Alloy or Pyroscope SDK to send profiles
 
-{{< docs/shared lookup="agent-deprecation.md" source="alloy" version="next" >}}
-
-You can use Grafana Agent for auto-instrumentation or the Pyroscope instrumentation SDKs.
+You can use Grafana Alloy for auto-instrumentation or the Pyroscope instrumentation SDKs.
 The method you choose depends on your specific use case and requirements.
 
 Here are some factors to consider when making the choice:
 
-- Ease of setup: The Grafana Agent is an ideal choice for a quick and straightforward setup without modifying your application's code. Note that eBPF profiling supports some languages (for example, Golang) better than others. More robust support for Python, Java, and other languages are in development.
+- Ease of setup: The Grafana Alloy is an ideal choice for a quick and straightforward setup without modifying your application's code. eBPF profiling supports some languages (for example, Golang) better than others. More robust support for Python, Java, and other languages are in development.
 - Language support: If you want more control over the profiling process and your application is written in a language supported by the Pyroscope SDKs, consider using the SDKs.
 - Flexibility: The Pyroscope SDKs offer greater flexibility in terms of customizing the profiling process and capturing specific sections of code with labels. If you have particular profiling needs or want to fine-tune the data collection process, the SDKs would be your best bet.
 
@@ -74,7 +72,7 @@ To get started, choose one of the integrations below:
 <table>
    <tr>
       <td align="center"><a href="https://grafana.com/docs/pyroscope/latest/configure-client/grafana-agent/go_pull"><img src="https://github-production-user-asset-6210df.s3.amazonaws.com/223048/257522425-48683963-91ae-4caf-8c52-ce131e25bd65.png" width="100px;" alt=""/><br />
-        <b>Grafana Agent</b></a><br />
+        <b>Grafana Alloy</b></a><br />
           <a href="https://grafana.com/docs/pyroscope/latest/configure-client/grafana-agent/go_pull/" title="Documentation">Documentation</a><br />
           <a href="https://github.com/grafana/pyroscope/tree/main/examples/grafana-agent-auto-instrumentation" title="examples">Examples</a>
       </td>
@@ -125,10 +123,11 @@ To get started, choose one of the integrations below:
 
 ## Enriching profile data
 
-You can add tags to your profiles to help correlate them with your other telemetry signals. Some common tags that are used are version, region, environment, request types, etc. You have the ability to add tags using both the SDK and the agent.
+You can add tags to your profiles to help correlate them with your other telemetry signals. Some common tags that are used are version, region, environment, request types, etc.
+You have the ability to add tags using both the SDK and Alloy.
 
 Valid tag formats may contain ASCII letters and digits, as well as underscores. It must match the regex `[a-zA-Z_][a-zA-Z0-9_]`.
-In Pyroscope, a period (`.`) is not a valid character inside of tags and labels.
+In Pyroscope, a period (`.`) isn't a valid character inside of tags and labels.
 
 ## Assistance with Pyroscope
 
diff --git a/docs/sources/configure-client/grafana-agent/_index.md b/docs/sources/configure-client/grafana-agent/_index.md
index 0ee4af0d21..8046d21c39 100644
--- a/docs/sources/configure-client/grafana-agent/_index.md
+++ b/docs/sources/configure-client/grafana-agent/_index.md
@@ -1,33 +1,41 @@
 ---
-title: "Grafana Alloy and Grafana Agent"
-menuTitle: "Grafana Alloy and Grafana Agent"
-description: "Send data from your application via using Grafana Alloy or Grafana Agent."
+title: "Grafana Alloy"
+menuTitle: "Grafana Alloy"
+description: "Send data from your application via using Grafana Alloy."
 weight: 10
 aliases:
   - /docs/phlare/latest/configure-client/grafana-agent/
 ---
 
-# Grafana Alloy and Grafana Agent
+# Grafana Alloy
 
 You can send data from your application using Grafana Alloy (preferred) or Grafana Agent (legacy) collectors.
 Both collectors support profiling with eBPF, Java, and Golang in pull mode.
 
-[Grafana Alloy](https://grafana.com/docs/alloy/latest/) is a vendor-neutral distribution of the OpenTelemetry (OTel) Collector.
+[Grafana Alloy](https://grafana.com/docs/alloy/<ALLOY_VERSION>/) is a vendor-neutral distribution of the OpenTelemetry (OTel) Collector.
 Alloy uniquely combines the very best OSS observability signals in the community.
-Grafana Alloy uses configuration file written using River.
+Grafana Alloy uses configuration files written in Alloy configuration syntax.
+For  more information, refer to the [Alloy configuration syntax](https://grafana.com/docs/alloy/<ALLOY_VERSION>/get-started/configuration-syntax/).
 
 Alloy is the recommended collector instead of Grafana Agent.
 New installations should use Alloy.
 
-{{< docs/shared lookup="agent-deprecation.md" source="alloy" version="next" >}}
-
-Grafana Agent is a powerful tool for collecting and forwarding profiling data.
-With the introduction of support for eBPF and continuing support for Golang in pull mode, Grafana Agent has become even more versatile in its capabilities.
+The instructions in this section explain how to use Alloy.
 
 {{< admonition type="note" >}}
-Refer to [Available profiling types]({{< relref "../../view-and-analyze-profile-data/profiling-types#available-profiling-types" >}}) for a list of profile types supported.
+Refer to [Available profiling types]({{< relref "../../view-and-analyze-profile-data/profiling-types#available-profiling-types" >}}) for a list of supported profile types.
 {{< /admonition >}}
 
+## Legacy collector, Grafana Agent
+
+{{< docs/shared lookup="agent-deprecation.md" source="alloy" version="next" >}}
+
+Grafana Agent is a legacy tool for collecting and forwarding profiling data.
+Agent supports for eBPF and Golang in pull mode.
+For information about Agent, refer to [Grafana Agent Flow](https://grafana.com/docs/agent/<AGENT_VERSION>/flow/).
+
+Instructions for using Grafana Agent is available in documentation for Pyroscope v1.8 and earlier.
+
 ## eBPF profiling
 
 eBPF (Extended Berkeley Packet Filter) is a modern Linux kernel technology that allows for safe, efficient, and customizable tracing of system and application behaviors without modifying the source code or restarting processes.
@@ -41,13 +49,15 @@ Benefits of eBPF profiling:
 ### Set up eBPF profiling
 
 1. Ensure your system runs a Linux kernel version 4.9 or newer.
-1. Install a collector, such as Grafana Alloy (preferred) or Grafana Agent (legacy), on the target machine or container.
-1. Configure the Agent to use eBPF for profiling. Refer to the [eBPF documentation](/docs/pyroscope/latest/configure-client/grafana-agent/ebpf) for detailed steps.
+1. Install a collector, such as Grafana Alloy, on the target machine or container.
+1. Configure Alloy to use eBPF for profiling. Refer to the [eBPF documentation](/docs/pyroscope/<PYROSCOPE_VERSION>/configure-client/grafana-agent/ebpf) for detailed steps.
 1. The collector collects eBPF profiles and sends them to the Pyroscope server.
 
 ### Supported languages
 
-This eBPF profiler only collects CPU profiles. Generally, natively compiled languages like C/C++, Go, and Rust are supported. Refer to [Troubleshooting unknown symbols][troubleshooting] for additional requirements.
+This eBPF profiler only collects CPU profiles.
+Generally, natively compiled languages like C/C++, Go, and Rust are supported.
+Refer to [Troubleshooting unknown symbols][troubleshooting] for additional requirements.
 
 Python is the only supported high-level language, as long as `python_enabled=true`.
 Other high-level languages like Java, Ruby, PHP, and JavaScript require additional work to show stack traces of methods in these languages correctly.
@@ -61,18 +71,18 @@ In pull mode, the collector periodically retrieves profiles from Golang applicat
 
 - Non-intrusive: No need to modify your application’s source code.
 - Centralized profiling: Suitable for environments with multiple Golang applications or microservices.
-- Automatic: The agent handles the pulling and sending of profiles, requiring minimal configuration.
+- Automatic: Alloy handles the pulling and sending of profiles, requiring minimal configuration.
 
 ### Set up Golang profiling in pull mode
 
 1. Ensure your Golang application exposes pprof endpoints.
-1. Install and configure the collector, either Alloy or Agent, on the same machine or container where your application runs.
-1. Ensure the collector is set to pull mode and targeting the correct pprof endpoints. For step-by-step instructions, visit the [Go (Pull Mode)](/docs/pyroscope/latest/configure-client/grafana-agent/go_pull) documentation.
+1. Install and configure Grafana Alloy on the same machine or container where your application runs.
+1. Ensure Alloy is set to pull mode and targeting the correct pprof endpoints. For step-by-step instructions, visit the [Go (Pull Mode)](https://grafana.com/docs/pyroscope/<PYROSCOPE_VERSION>/configure-client/grafana-agent/go_pull) documentation.
 1. The collector queries the pprof endpoints of your Golang application, collects the profiles, and forwards them to the Pyroscope server.
 
 ## Next steps
 
-Whether using eBPF for versatile system and application profiling or relying on Golang's built-in pprof endpoints in pull mode, Grafana Agent and Grafana Alloy collectors offer streamlined processes to gather essential profiling data.
+Whether using eBPF for versatile system and application profiling or relying on Golang's built-in pprof endpoints in pull mode, Grafana Alloy collectors offer streamlined processes to gather essential profiling data.
 Choose the method that best fits your application and infrastructure needs.
 
-[troubleshooting]: /docs/alloy/latest/reference/components/pyroscope/pyroscope.ebpf/#troubleshooting-unknown-symbols
+[troubleshooting]: /docs/alloy/<ALLOY_VERSION>/reference/components/pyroscope/pyroscope.ebpf/#troubleshooting-unknown-symbols
diff --git a/docs/sources/configure-client/grafana-agent/ebpf/_index.md b/docs/sources/configure-client/grafana-agent/ebpf/_index.md
index b4e55515ea..caee1c08a0 100644
--- a/docs/sources/configure-client/grafana-agent/ebpf/_index.md
+++ b/docs/sources/configure-client/grafana-agent/ebpf/_index.md
@@ -1,5 +1,5 @@
 ---
-title: "Profiling with eBPF with Grafana Agent"
+title: "Profiling with eBPF with Grafana Alloy"
 menuTitle: "Profiling with eBPF"
 description: "Learn about using eBPF for continuous profiling for performance optimization."
 weight: 20
@@ -8,7 +8,7 @@ aliases:
   - /docs/pyroscope/next/configure-client/language-sdks/ebpf
 ---
 
-# Profiling with eBPF with Grafana Agent
+# Profiling with eBPF with Grafana Alloy
 
 <img src="/media/docs/pyroscope/ebpf_logo_color_on_white.png" width="100px;" alt="eBPF"/>
 
@@ -25,9 +25,9 @@ eBPF's low overhead and fine-grained data collection make it an ideal choice for
 
 However, eBPF has some limitations that make it unsuitable for certain use cases:
 
-- It isn't a good fit for profiling applications that are not written in a supported language.
-- It can't be used to profile applications that are not running on Linux.
-- It does not support all profile types such as memory and contention/lock profiling.
+- It isn't a good fit for profiling applications that arn't written in a supported language.
+- It can't be used to profile applications that aren't running on Linux.
+- It doesn't support all profile types such as memory and contention/lock profiling.
 - eBPF requires root access to the host machine, which can be a problem in some environments.
 
 ## Supported languages
@@ -38,15 +38,12 @@ Python is the only supported high-level language, as long as `python_enabled=tru
 Other high-level languages like Java, Ruby, PHP, and JavaScript require additional work to show stack traces of methods in these languages correctly.
 Currently, the CPU usage for these languages is reported as belonging to the runtime's methods.
 
+## eBPF using Grafana Alloy
 
-## eBPF via the Grafana Agent
+The Grafana Alloy is a lightweight, all-in-one collector that can collect, transform, and ship observability data.
+For profiling, Grafana Alloy can be configured to collect eBPF profiles and send them to Pyroscope.
 
-{{< docs/shared lookup="agent-deprecation.md" source="alloy" version="next" >}}
+This section contains instructions for installing and configuring Grafana Alloy to collect eBPF profiles.
+For more information about Alloy itself, refer to the [Grafana Alloy documentation](https://grafana.com/docs/alloy/<ALLOY_VERSION>/).
 
-The Grafana Agent is a lightweight, all-in-one agent that can collect, transform, and ship observability data.
-For profiling, the Grafana Agent can be configured to collect eBPF profiles and send them to Pyroscope.
-
-This section contains instructions for installing and configuring the Grafana Agent to collect eBPF profiles.
-For more information about the Grafana Agent itself, see the [Grafana Agent documentation](/docs/agent/latest/flow/).
-
-[troubleshooting]: /docs/alloy/latest/reference/components/pyroscope/pyroscope.ebpf/#troubleshooting-unknown-symbols
+[troubleshooting]: /docs/alloy/<ALLOY_VERSION>/reference/components/pyroscope/pyroscope.ebpf/#troubleshooting-unknown-symbols
diff --git a/docs/sources/configure-client/grafana-agent/ebpf/configuration/_index.md b/docs/sources/configure-client/grafana-agent/ebpf/configuration/_index.md
index 11165f5567..d3dbc33485 100644
--- a/docs/sources/configure-client/grafana-agent/ebpf/configuration/_index.md
+++ b/docs/sources/configure-client/grafana-agent/ebpf/configuration/_index.md
@@ -1,14 +1,13 @@
 ---
 title: "Configuration reference"
-menuTitle: "Configuration Reference"
-description: "Grafana Agent eBPF Profiling configuration reference"
+menuTitle: "Configuration reference"
+description: "Grafana Alloy eBPF Profiling configuration reference"
 weight: 30
 ---
 
-
 ## Configuration reference
 
-Grafana Agent supports eBPF profiling in [Flow mode](https://grafana.com/docs/agent/latest/flow/).
+Grafana Alloy supports eBPF profiling.
 The configuration file is written in the [River](https://grafana.com/docs/agent/latest/flow/concepts/config-language/) language and is composed of components that are used to collect, transform, and send data.
 
 The `pyroscope.ebpf` component is used to collect application performance profiles via eBPF.
@@ -17,8 +16,10 @@ The `pyroscope.ebpf` component is used to collect application performance profil
 
 The `pyroscope.ebpf` runs on the host machine and collects stack traces associated with a process running on the current host.
 
-Using the `targets` argument, you can specify which processes and containers to profile on the machine. The `targets` can be from discovery components such as `discovery.process`, `dicovery.kubernetes`, `discovery.docker`, and `discovery.dockerswarm`.
-To relabel discovered targets and set your own labels you can use the `discovery.relabel` component. For more information, refer to [Components](/docs/agent/latest/flow/concepts/components/).
+Using the `targets` argument, you can specify which processes and containers to profile on the machine. The `targets` can be from discovery components such as `discovery.process`, [`discovery.kubernetes`](https://grafana.com/docs/alloy/<ALLOY_VERSION>/reference/components/discovery/discovery.kubernetes/), [`discovery.docker`](https://grafana.com/docs/alloy/<ALLOY_VERSION>/reference/components/discovery/discovery.docker/), and [`discovery.dockerswarm`](https://grafana.com/docs/alloy/<ALLOY_VERSION>/reference/components/discovery/discovery.dockerswarm/).
+
+You can use the [`discovery.relabel`](https://grafana.com/docs/alloy/<ALLOY_VERSION>/reference/components/discovery/discovery.relabel/) component to relabel discovered targets and set your own labels.
+For more information, refer to the [Components](https://grafana.com/docs/alloy/<ALLOY_VERSION>/reference/components/) documentation.
 
 The `forward_to` parameter should point to a `pyroscope.write` component to send the collected profiles to your Pyroscope Server or [Grafana Cloud](/products/cloud/).
 
@@ -49,7 +50,7 @@ The `pyroscope.ebpf` component supports the following languages:
 
 When sending to Grafana Cloud Profiles, you can use the following `pyroscope.write` component configuration which makes uses of environment variables:
 
-```river
+```alloy
 pyroscope.write "endpoint" {
     endpoint {
         basic_auth {
@@ -124,4 +125,9 @@ Check out the following resources to learn more about eBPF profiling:
 
 - [The pros and cons of eBPF profiling](https://pyroscope.io/blog/ebpf-profiling-pros-cons) blog post (for more context on flame graphs below)
 - [Demo](https://play-pyroscope.grafana.org) showing breakdown of our examples cluster
-- Grafana Agent documentation for [pyroscope.ebpf](/docs/agent/latest/flow/reference/components/pyroscope.ebpf/), [pyroscope.write](/docs/agent/latest/flow/reference/components/pyroscope.write/), [discovery.kubernetes](/docs/agent/latest/flow/reference/components/discovery.kubernetes/), [discovery.relabel](/docs/agent/latest/flow/reference/components/discovery.relabel/) components
+- [Grafana Alloy](https://grafana.com/docs/alloy/<ALLOY_VERSION>/)
+- [pyroscope.scrape](https://grafana.com/docs/alloy/<ALLOY_VERSION>/reference/components/pyroscope/pyroscope.scrape/)
+- [pyroscope.write](https://grafana.com/docs/alloy/<ALLOY_VERSION>/reference/components/pyroscope/pyroscope.write/)
+- [discovery.kubernetes](https://grafana.com/docs/alloy/<ALLOY_VERSION>/reference/components/discovery/discovery.kubernetes/)
+- [discovery.docker](https://grafana.com/docs/alloy/<ALLOY_VERSION>/reference/components/discovery/discovery.docker/)
+- [discovery.relabel](https://grafana.com/docs/alloy/<ALLOY_VERSION>/reference/components/discovery/discovery.relabel/)
diff --git a/docs/sources/configure-client/grafana-agent/ebpf/setup-docker.md b/docs/sources/configure-client/grafana-agent/ebpf/setup-docker.md
index 02ac9f7cd2..d73b5157a4 100644
--- a/docs/sources/configure-client/grafana-agent/ebpf/setup-docker.md
+++ b/docs/sources/configure-client/grafana-agent/ebpf/setup-docker.md
@@ -1,36 +1,36 @@
 ---
 title: "Setup eBPF Profiling on Docker"
 menuTitle: "Setting up on Docker"
-description: "Setting up eBPF Profiling with Grafana Agent on Docker"
+description: "Setting up eBPF Profiling with Grafana Alloy on Docker"
 weight: 20
 ---
 
 # Setup eBPF Profiling on Docker
 
-To set up eBPF profiling with Grafana Agent on Linux, you need to:
+To set up eBPF profiling with Grafana Alloy on Linux, you need to:
 
 - Verify that your system meets the requirements.
-- Create a Grafana Agent configuration file. For more information, refer to the [Configuration reference][config-reference].
-- Run Grafana Agent or Grafana Alloy.
+- Create a Grafana Alloy configuration file. For more information, refer to the [Configuration reference][config-reference].
+- Run Grafana Alloy.
 - Verify that profiles are received.
 
 {{< docs/shared lookup="agent-deprecation.md" source="alloy" version="next" >}}
 
-## Prerequisites
+## Before you begin
 
 Before you begin, you need:
 
-- A Pyroscope server where the agent will send profiling data.
-- Access to Grafana with the [Grafana Pyroscope datasource][pyroscope-ds] provisioned.
+- A Pyroscope server where Alloy can send profiling data.
+- Access to Grafana with the [Grafana Pyroscope data source][pyroscope-ds] provisioned.
 - [Docker Engine](https://docs.docker.com/engine/install/) installed.
 
 {{% admonition type="note" %}}
-If you don't have a Grafana and/or a Pyroscope server, you can use the [Grafana Cloud][gcloud] free plan to get started.
+If you don't have a Grafana or a Pyroscope server, you can use the [Grafana Cloud][gcloud] free plan to get started.
 {{% /admonition %}}
 
-## Verify system meets the requirements
+## Verify system requirements
 
-The eBPF profiler requires a Linux kernel version >= 4.9 (due to [BPF_PROG_TYPE_PERF_EVENT](https://lkml.org/lkml/2016/9/1/831)).
+The eBPF profiler requires a Linux kernel version >= 4.9 due to [BPF_PROG_TYPE_PERF_EVENT](https://lkml.org/lkml/2016/9/1/831).
 
 `BPF_PROG_TYPE_PERF_EVENT` is a type of eBPF program that can be attached to hardware or software events, such as performance monitoring counters or tracepoints, in the Linux kernel.
 
@@ -40,16 +40,18 @@ To print the kernel version of your docker host, run:
 docker info | grep Kernel
 ```
 
-Make sure you have a kernel version >= 4.9.
+The kernel version must be 4.9 or later.
 
-## Configure Grafana Agent
+## Configure Grafana Alloy
 
-You can configure the Grafana Agent eBPF profiler to profile local containers.
-To do so, use the `discovery.docker` component to discover local containers and the `pyroscope.ebpf` component to profile them.
+You can configure Grafana Alloy eBPF profiler to profile local containers.
+To do so, use the [`discovery.docker` component](https://grafana.com/docs/alloy/<ALLOY_VERSION>/reference/components/discovery/discovery.docker/) to discover local containers and the [`pyroscope.ebpf` component](https://grafana.com/docs/alloy/<ALLOY_VERSION>/reference/components/pyroscope/pyroscope.ebpf/) to profile them
 
-Create a file named `agent.river` with the following content:
+For more information about the Alloy configuration, refer to the [Alloy Components reference](https://grafana.com/docs/alloy/<ALLOY_VERSION>/reference/components/).
 
-```river
+Create a file named `alloy.config` with the following content:
+
+```alloy
 discovery.docker "local_containers" {
  host = "unix:///var/run/docker.sock"
 }
@@ -59,7 +61,6 @@ pyroscope.ebpf "instance" {
  targets = discovery.docker.local_containers.targets
 }
 
-
 pyroscope.write "endpoint" {
  endpoint {
   basic_auth {
@@ -75,37 +76,41 @@ pyroscope.write "endpoint" {
 }
 ```
 
-Replace the `<URL>` placeholder with the appropriate server URL. This could be the Grafana Cloud URL or your own custom Pyroscope server URL.
+Replace the `<URL>` placeholder with the appropriate server URL.
+This could be the Grafana Cloud URL or your own custom Pyroscope server URL.
+
+If you need to send data to Grafana Cloud, you'll have to configure HTTP Basic authentication.
+Replace `<User>` with your Grafana Cloud stack user and `<Password>` with your Grafana Cloud API key.
 
-If you need to send data to Grafana Cloud, you'll have to configure HTTP Basic authentication. Replace `<User>` with your Grafana Cloud stack user and `<Password>` with your Grafana Cloud API key.
+For more information, refer to the [Configure the Grafana Pyroscope data source documentation](https://grafana.com/docs/grafana-cloud/connect-externally-hosted/data-sources/pyroscope/configure-pyroscope-data-source/).
 
 {{% admonition type="note" %}}
 If you're using your own Pyroscope server, you can remove the `basic_auth` section altogether.
 {{% /admonition %}}
 
-For more information, refer to the [Configure the Grafana Pyroscope data source documentation](/docs/grafana-cloud/connect-externally-hosted/data-sources/pyroscope/configure-pyroscope-data-source/).
 
-## Start Grafana Agent
+## Start Grafana Alloy
 
-To start Grafana Agent with Docker, run:
+To start Grafana Alloy with Docker, run:
 
 ```shell
 docker run \
-  -e AGENT_MODE=flow \
-  -v $PWD/agent.river:/etc/agent/config.river \
+  -v $PWD/alloy.config:/etc/alloy/alloy.config \
   -v /var/run/docker.sock:/var/run/docker.sock \
   --pid=host \
   --privileged \
   -p 12345:12345 \
-  grafana/agent:latest \
-    run --server.http.listen-addr=0.0.0.0:12345 /etc/agent/config.river
+  grafana/alloy:latest \
+    run --server.http.listen-addr=0.0.0.0:12345 /etc/alloy/alloy.config
 ```
 
-> Note: The `--pid=host` and `--privileged` flags are required to profile local containers with ebpf.
+{{< admonition type="note >}}
+The `--pid=host` and `--privileged` flags are required to profile local containers with eBPF.
+{{< /admonition >}}
 
 ## Verify profiles are received
 
-To verify that the profiles are received by the Pyroscope server, go to the Pyroscope UI or [Grafana Pyroscope datasource][pyroscope-ds]. Then select a profile type and a service from the dropdown menu.
+To verify that the profiles are received by the Pyroscope server, go to the Pyroscope UI or [Grafana Pyroscope data source][pyroscope-ds]. Then select a profile type and a service from the dropdown menu.
 
 [pyroscope-ds]: /docs/grafana/<GRAFANA_VERSION>/datasources/pyroscope/
 [config-reference]: ../configuration/
diff --git a/docs/sources/configure-client/grafana-agent/ebpf/setup-kubernetes.md b/docs/sources/configure-client/grafana-agent/ebpf/setup-kubernetes.md
index a418acc983..455cbc304c 100644
--- a/docs/sources/configure-client/grafana-agent/ebpf/setup-kubernetes.md
+++ b/docs/sources/configure-client/grafana-agent/ebpf/setup-kubernetes.md
@@ -1,32 +1,30 @@
 ---
 title: "Setup eBPF Profiling on Kubernetes"
 menuTitle: "Setting up on Kubernetes"
-description: "Setting up eBPF Profiling with Grafana Agent on Kubernetes"
+description: "Setting up eBPF Profiling with Grafana Alloy on Kubernetes"
 weight: 10
 ---
 
 # Setup eBPF Profiling on Kubernetes
 
-To set up eBPF profiling with Grafana Agent on Kubernetes, you need to:
+To set up eBPF profiling with Grafana Alloy on Kubernetes, you need to:
 
 - Verify that your cluster meets the prerequisites.
 - Add the Grafana helm repository.
-- Create a Grafana Agent configuration file. For more information, refer to [Configuration reference][config-reference].
-- Install Grafana Agent.
+- Create a Grafana Alloy configuration file. For more information, refer to [Configuration reference][config-reference].
+- Install Grafana Alloy, refer to the [installation instructions](https://grafana.com/docs/alloy/<ALLOY_VERSION>/set-up/install/kubernetes/)
 - Verify that profiles are received.
 
-{{< docs/shared lookup="agent-deprecation.md" source="alloy" version="next" >}}
-
-## Prerequisites
+## Before you begin
 
 Before you begin, you need:
 
 - [Helm][helm] and [kubectl][kubectl] installed with access to your Kubernetes cluster.
-- A Pyroscope server where the Agent will send profiling data.
+- A Pyroscope server where Alloy can send profiling data.
 - Access to Grafana with the [Grafana Pyroscope data source][pyroscope-ds] provisioned.
 
 {{< admonition type="note" >}}
-If you don't have a Grafana and/or a Pyroscope server, you can use the [Grafana Cloud][gcloud] free plan to get started.
+If you don't have a Grafana or a Pyroscope server, you can use the [Grafana Cloud][gcloud] free plan to get started.
 {{< /admonition >}}
 
 ## Verify that your cluster meets the requirements
@@ -45,7 +43,8 @@ Make sure all nodes have a kernel version >= 4.9.
 
 ## Add the Grafana Helm repository
 
-We recommend using [Helm][helm] to install Grafana Agent. To add the Grafana Helm repository, run:
+We recommend using [Helm][helm] to install Grafana Alloy.
+To add the Grafana Helm repository, run:
 
 ```shell
 helm repo add grafana https://grafana.github.io/helm-charts
@@ -55,18 +54,17 @@ helm repo update
 Verify that the repository was added successfully by running:
 
 ```shell
-helm search repo grafana/grafana-agent
+helm search repo grafana/alloy
 ```
 
-It should return a list of available versions of Grafana Agent.
+The command returns a list of available versions of Grafana Alloy.
 
-## Create a Grafana Agent configuration file
+## Create a Grafana Alloy configuration file
 
-Create a file named `values.yaml` with the following content:
+Create a file named `values.yaml` with the content from the sample configuration file.
 
 ```yaml
-agent:
-  mode: 'flow'
+alloy:
   configMap:
     create: true
     content: |
@@ -100,29 +98,39 @@ controller:
   hostPID: true
 ```
 
-Replace the `<URL>` placeholder with the appropriate server URL. This could be the Grafana Cloud URL or your own custom Pyroscope server URL.
+For information about configuring Alloy, refer to [Grafana Alloy on Kubernetes](https://grafana.com/docs/alloy/<ALLOY_VERSION>/configure/kubernetes/).
+
+For information about the specific blocks used, refer to the [Grafana Alloy Reference](https://grafana.com/docs/alloy/<ALLOY_VERSION>/reference/).
 
-If you need to send data to Grafana Cloud, you'll have to configure HTTP Basic authentication. Replace `<User>` with your Grafana Cloud stack user and `<Password>` with your Grafana Cloud API key.
+Replace the `<URL>` placeholder with the appropriate server URL.
+This could be the Grafana Cloud URL or your own custom Pyroscope server URL.
+
+If you need to send data to Grafana Cloud, you'll have to configure HTTP Basic authentication.
+Replace `<User>` with your Grafana Cloud stack user and `<Password>` with your Grafana Cloud API key.
+
+For more information, refer to the [Configure the Grafana Pyroscope data source documentation](/docs/grafana-cloud/connect-externally-hosted/data-sources/pyroscope/configure-pyroscope-data-source/).
 
 {{% admonition type="note" %}}
 If you're using your own Pyroscope server, you can remove the `basic_auth` section altogether.
 {{% /admonition %}}
 
-For more information, refer to the [Configure the Grafana Pyroscope data source documentation](/docs/grafana-cloud/connect-externally-hosted/data-sources/pyroscope/configure-pyroscope-data-source/).
 
-## Install the Grafana Agent
+## Install the Grafana Alloy
 
-To install the Grafana Agent, run:
+To install the Grafana Alloy, run:
 
 ```shell
-helm install pyroscope-ebpf grafana/grafana-agent -f values.yaml
+helm install pyroscope-ebpf grafana/alloy -f values.yaml
 ```
 
-Once configured, the Agent starts collecting eBPF profiles and send them to the Pyroscope server.
+Once configured, Alloy starts collecting eBPF profiles and sends them to the Pyroscope server.
 
 ## Verify profiles are received
 
-To verify that the profiles are received by the Pyroscope server, go to the Pyroscope UI or [Grafana Pyroscope datasource][pyroscope-ds]. Select a profile type and a service from the drop-down menu.
+To verify that the profiles are received by the Pyroscope server:
+
+1. Go to the Pyroscope UI or [Grafana Pyroscope data source][pyroscope-ds].
+1. Select a profile type and a service from the drop-down menu.
 
 [gcloud]: /products/cloud/
 [helm]: https://helm.sh/docs/intro/install/
diff --git a/docs/sources/configure-client/grafana-agent/ebpf/setup-linux.md b/docs/sources/configure-client/grafana-agent/ebpf/setup-linux.md
index 97fbc513e3..7e1b63cb25 100644
--- a/docs/sources/configure-client/grafana-agent/ebpf/setup-linux.md
+++ b/docs/sources/configure-client/grafana-agent/ebpf/setup-linux.md
@@ -1,31 +1,29 @@
 ---
 title: "Set up eBPF profiling on Linux"
 menuTitle: "Set up on Linux"
-description: "Set up eBPF profiling with Grafana Agent on Linux machines."
+description: "Set up eBPF profiling with Grafana Alloy on Linux machines."
 weight: 20
 ---
 
 # Set up eBPF profiling on Linux
 
-To set up eBPF profiling with Grafana Agent on Linux, you need to:
+To set up eBPF profiling with Grafana Alloy on Linux, you need to:
 
 - Verify that your system meets the requirements.
-- Install the Grafana Agent Flow mode.
-- Create a Grafana Agent configuration file. For more information, refer to [Configuration reference][config-reference].
-- Run Grafana Agent or Grafana Alloy.
+- Install [Grafana Alloy](https://grafana.com/docs/alloy/<ALLOY_VERSION>/set-up/install/linux/).
+- Create a [Grafana Alloy configuration file](https://grafana.com/docs/alloy/<ALLOY_VERSION>/configure/linux/). For more information, refer to [Configuration reference](https://grafana.com/docs/alloy/<ALLOY_VERSION>/reference/).
+- Run Grafana Alloy.
 - Finally, verify that profiles are received.
 
-{{< docs/shared lookup="agent-deprecation.md" source="alloy" version="next" >}}
-
-## Prerequisites
+## Before you begin
 
 Before you begin, you need:
 
-- A Pyroscope server where the agent will send profiling data.
-- Access to Grafana with the [Grafana Pyroscope datasource][pyroscope-ds] provisioned.
+- A Pyroscope server where Alloy can send profiling data.
+- Access to Grafana with the [Grafana Pyroscope data source][pyroscope-ds] provisioned.
 
 {{% admonition type="note" %}}
-If you don't have a Grafana and/or a Pyroscope server, you can use the [Grafana Cloud][gcloud] free plan to get started.
+If you don't have a Grafana or a Pyroscope server, you can use the [Grafana Cloud][gcloud] free plan to get started.
 {{% /admonition %}}
 
 ## Verify system meets the requirements
@@ -42,51 +40,41 @@ uname -r
 
 Make sure you have a kernel version >= 4.9.
 
-## Install the Grafana Agent
-
-Follow the [installation instructions][agent-install] to download and install the Grafana Agent for your current Linux distribution.
+## Install Grafana Alloy
 
-Verify that the agent is correctly installed by running:
+Follow the [installation instructions](https://grafana.com/docs/alloy/<ALLOY_VERSION>/set-up/install/linux/) to download and install Alloy for your current Linux distribution.
 
-```shell
-grafana-agent-flow --version
-```
+## Configure Grafana Alloy
 
-## Configure the Grafana Agent
+To configure the Alloy eBPF profiler to profile local processes, you'll need to set the `targets_only` flag to `false` and add a default target in the `pyroscope.ebpf` component.
+All processes are profiled and grouped under the default target.
 
-To configure the Grafana Agent eBPF profiler to profile local processes, you'll need to set the `targets_only` flag to `false` and add a default target in the `pyroscope.ebpf` component.
-All processes will be profiled and grouped under the default target.
-
-{{% admonition type="note" %}}
-We're [working on a more flexible configuration](https://github.com/grafana/agent/pull/5858) that will allow you to specify which processes to profile.
-{{% /admonition %}}
+Create a file named `alloy.config` with the following content:
 
-Create a file named `agent.river` with the following content:
-
-```river
+```alloy
 discovery.process "all" {
 
 }
 
-discovery.relabel "agent" {
+discovery.relabel "alloy" {
     targets = discovery.process.all.targets
     // Filter needed processes
     rule {
         source_labels = ["__meta_process_exe"]
-        regex = ".*/grafana-agent"
+        regex = ".*/alloy"
         action = "keep"
     }
 }
 
 pyroscope.ebpf "instance" {
  forward_to     = [pyroscope.write.endpoint.receiver]
- targets = discovery.relabel.agent.output
+ targets = discovery.relabel.alloy.output
 }
 
 pyroscope.scrape "local" {
   forward_to     = [pyroscope.write.endpoint.receiver]
   targets    = [
-    {"__address__" = "localhost:12345", "service_name"="grafana/agent"},
+    {"__address__" = "localhost:12345", "service_name"="grafana/alloy"},
   ]
 }
 
@@ -105,22 +93,30 @@ pyroscope.write "endpoint" {
 }
 ```
 
+For information about configuring Alloy, refer to [Grafana Alloy on Kubernetes](https://grafana.com/docs/alloy/<ALLOY_VERSION>/configure/kubernetes/).
+
+For information about the specific blocks used, refer to the [Grafana Alloy Reference](https://grafana.com/docs/alloy/<ALLOY_VERSION>/reference/) and [`discovery.process`](https://grafana.com/docs/alloy/<AlLOY_VERSION>/reference/components/discovery/discovery.process/).
+
 Replace the `<URL>` placeholder with the appropriate server URL. This could be the Grafana Cloud URL or your own custom Pyroscope server URL.
 
 If you need to send data to Grafana Cloud, you'll have to configure HTTP Basic authentication. Replace `<User>` with your Grafana Cloud stack user and `<Password>` with your Grafana Cloud API key.
 
+For more information, refer to the [Configure the Grafana Pyroscope data source documentation](/docs/grafana-cloud/connect-externally-hosted/data-sources/pyroscope/configure-pyroscope-data-source/).
+
 {{% admonition type="note" %}}
 If you're using your own Pyroscope server, you can remove the `basic_auth` section altogether.
 {{% /admonition %}}
 
-For more information, refer to the [Configure the Grafana Pyroscope data source documentation](/docs/grafana-cloud/connect-externally-hosted/data-sources/pyroscope/configure-pyroscope-data-source/).
+## Start Grafana Alloy
 
-## Start the Grafana Agent
+{{< admonition type="note">}}
+The eBPF profiler requires root privileges.
+{{< /admonition >}}
 
-To start the Grafana Agent, run:
+To start the Grafana Alloy, run:
 
 ```shell
-grafana-agent-flow run agent.river
+alloy run alloy.config
 ```
 
 If you see the following error:
@@ -129,14 +125,12 @@ If you see the following error:
 level=error msg="component exited with error" component=pyroscope.ebpf.local_pods err="ebpf profiling session start: load bpf objects: field DisassociateCtty: program disassociate_ctty: map events: map create: operation not permitted (MEMLOCK may be too low, consider rlimit.RemoveMemlock)"
 ```
 
-Make sure you're running the agent with root privileges which are required for the eBPF profiler to work.
+Make sure you're running Alloy with root privileges which are required for the eBPF profiler to work.
 
 ## Verify profiles are received
 
-To verify that the profiles are received by the Pyroscope server, go to the Pyroscope UI or [Grafana Pyroscope datasource][pyroscope-ds]. Select a profile type and a service from the drop-down menu.
+To verify that the profiles are received by the Pyroscope server, go to the Pyroscope UI or [Grafana Pyroscope data source][pyroscope-ds]. Select a profile type and a service from the drop-down menu.
 
-[agent-install]: /docs/agent/latest/flow/setup/install/linux/
 [pyroscope-ds]: /docs/grafana/<GRAFANA_VERSION>/datasources/pyroscope/
 [config-reference]: ../configuration/
 [gcloud]: /products/cloud/
-[discovery.process](/docs/agent/next/flow/reference/components/discovery.process/)
diff --git a/docs/sources/configure-client/grafana-agent/ebpf/troubleshooting.md b/docs/sources/configure-client/grafana-agent/ebpf/troubleshooting.md
index 61abd52d82..d7c085f78c 100644
--- a/docs/sources/configure-client/grafana-agent/ebpf/troubleshooting.md
+++ b/docs/sources/configure-client/grafana-agent/ebpf/troubleshooting.md
@@ -11,11 +11,11 @@ Learn how to troubleshoot and resolve eBPF installation issues.
 
 ## Profile interpreted languages
 
-Profiling interpreted languages like Ruby, JavaScript, etc., is not ideal using this implementation.
+Profiling interpreted languages like Ruby, JavaScript, etc., isn't ideal using this implementation.
 The JIT-compiled methods in these languages are typically not in ELF file format, demanding additional steps for
 profiling. For instance, using perf-map-agent and enabling frame pointers for Java.
 
-Interpreted methods will display the interpreter function’s name rather than the actual function.
+Interpreted methods display the interpreter function’s name rather than the actual function.
 
 ## Troubleshoot unknown symbols
 
diff --git a/docs/sources/configure-client/grafana-agent/go_pull.md b/docs/sources/configure-client/grafana-agent/go_pull.md
index c302076f73..0b62b41783 100644
--- a/docs/sources/configure-client/grafana-agent/go_pull.md
+++ b/docs/sources/configure-client/grafana-agent/go_pull.md
@@ -7,17 +7,17 @@ weight: 10
 
 # Set up Go profiling in pull mode
 
-In pull mode, the collector, whether Grafana Alloy (preferred) or Grafana Agent (legacy), periodically retrieves profiles from Golang applications, specifically targeting the
+In pull mode, the collector, Grafana Alloy, periodically retrieves profiles from Golang applications, specifically targeting the
 `/debug/pprof/*` endpoints.
 
 To set up Golang profiling in pull mode, you need to:
 
 1. Expose pprof endpoints.
-2. Install a collector, either Grafana Alloy (preferred) or Grafana Agent (legacy).
+2. Install a collector, such as Grafana Alloy.
 3. Prepare the collector's configuration file.
 4. Start the collector.
 
-### Expose pprof endpoints
+## Expose pprof endpoints
 
 Ensure your Golang application exposes pprof endpoints.
 
@@ -34,27 +34,21 @@ Ensure your Golang application exposes pprof endpoints.
     import _ "github.com/grafana/pyroscope-go/godeltaprof/http/pprof"
     ```
 
-### Install the collector
+## Install the collector
 
 [//]: # (TODO&#40;korniltsev&#41; What should go here?)
 
-This procedure can be used with either Grafana Alloy or Grafana Agent collector.
-You can use the sample collector configuration file to send data to Pyroscope.
-This configuration file works for either Grafana Alloy or Grafana Agent in Flow mode.
-
-Grafana Alloy is the preferred collector.
+You can use the sample Alloy collector configuration file to send data to Pyroscope.
 
 To install Alloy, refer to [Grafana Alloy installation](https://grafana.com/docs/alloy/<ALLOY_VERSION>/get-started/install/).
 
-{{< docs/shared lookup="agent-deprecation.md" source="alloy" version="next" >}}
-
 ### Prepare the collector configuration file
 
-In the Grafana Alloy or Grafana Agent Flow configuration file, you need to add at least two blocks: `pyroscope.write` and `pyroscope.scrape`.
+In the Grafana Alloy configuration file, you need to add at least two blocks: `pyroscope.write` and `pyroscope.scrape`.
 
 1. Add `pyroscope.write` block.
 
-    ```river
+    ```alloy
     pyroscope.write "write_job_name" {
             endpoint {
                     url = "http://localhost:4040"
@@ -64,7 +58,7 @@ In the Grafana Alloy or Grafana Agent Flow configuration file, you need to add a
 
 1. Add `pyroscope.scrape` block.
 
-    ```river
+    ```alloy
     pyroscope.scrape "scrape_job_name" {
             targets    = [{"__address__" = "localhost:4040", "service_name" = "example_service"}]
             forward_to = [pyroscope.write.write_job_name.receiver]
@@ -115,14 +109,9 @@ In the Grafana Alloy or Grafana Agent Flow configuration file, you need to add a
     docker run -p 4040:4040 grafana/pyroscope
     ```
 
-1. Start the collector:
+1. To start Grafana Alloy v1.2 and later: Replace `configuration.alloy` with your configuration filename: <br> `alloy run configuration.alloy`
 
-  * To start Grafana Alloy v1.2: Replace `configuration.alloy` with your configuration file name: <br> `alloy run configuration.alloy`
-  * To start Grafana Alloy v1.0/1.1: Replace `configuration.alloy` with your configuration file name: <br> `alloy run --stability.level=public-preview configuration.alloy`
-    The `stability.level` option is required for `pyroscope.scrape` with Alloy v1.0 or v1.1. For more information about `stability.level`, refer to [The run command](https://grafana.com/docs/alloy/<ALLOY_VERSION>/reference/cli/run/#permitted-stability-levels) documentation.
-  * To start Grafana Agent, replace `configuration.river` with your configuration file name: <br> ` grafana-agent-flow run configuration.river`
-
-1. Open a browser to http://localhost:4040. The page should list profiles.
+1. Open a browser to `http://localhost:4040`. The page should list profiles.
 
 ## Examples
 
@@ -132,7 +121,7 @@ Your Grafana Cloud URL, username, and password can be found on the "Details Page
 grafana.com.
 On this same page, create a token and use it as the Basic authentication password.
 
-```river
+```alloy
 pyroscope.write "write_job_name" {
         endpoint {
                 url = "<Grafana Cloud URL>"
@@ -149,7 +138,8 @@ pyroscope.write "write_job_name" {
 ### Discover Kubernetes targets
 
 1. Select all pods
-  ```river
+
+  ```alloy
   discovery.kubernetes "all_pods" {
           role = "pod"
   }
@@ -158,7 +148,7 @@ pyroscope.write "write_job_name" {
 1. Drop not running pods, create `namespace`, `pod`, `node` and `container` labels.
   Compose `service_name` label based on `namespace` and `container` labels.
   Select only services matching regex pattern `(ns1/.*)|(ns2/container-.*0)`.
-    ```river
+    ```alloy
 
     discovery.relabel "specific_pods" {
             targets = discovery.kubernetes.all_pods.targets
@@ -210,9 +200,9 @@ pyroscope.write "write_job_name" {
     }
     ```
 
-3. Use `discovery.relabel.specific_pods.output` as a target for `pyroscope.scrape` block.
+1. Use `discovery.relabel.specific_pods.output` as a target for `pyroscope.scrape` block.
 
-    ```river
+    ```alloy
         pyroscope.scrape "scrape_job_name" {
                 targets    = discovery.relabel.specific_pods.output
                 ...
@@ -237,20 +227,9 @@ router.PathPrefix("/debug/pprof").Handler(http.DefaultServeMux)
 
 ## References
 
-### Grafana Alloy
-
 - [Grafana Alloy](https://grafana.com/docs/alloy/<ALLOY_VERSION>/)
 - [pyroscope.scrape](https://grafana.com/docs/alloy/<ALLOY_VERSION>/reference/components/pyroscope/pyroscope.scrape/)
 - [pyroscope.write](https://grafana.com/docs/alloy/<ALLOY_VERSION>/reference/components/pyroscope/pyroscope.write/)
 - [discovery.kubernetes](https://grafana.com/docs/alloy/<ALLOY_VERSION>/reference/components/discovery/discovery.kubernetes/)
 - [discovery.docker](https://grafana.com/docs/alloy/<ALLOY_VERSION>/reference/components/discovery/discovery.docker/)
 - [discovery.relabel](https://grafana.com/docs/alloy/<ALLOY_VERSION>/reference/components/discovery/discovery.relabel/)
-
-### Grafana Agent
-
-- [Example using grafana-agent](https://github.com/grafana/pyroscope/tree/main/examples/grafana-agent-auto-instrumentation).
-- [pyroscope.scrape](https://grafana.com/docs/agent/<AGENT_VERSION>/flow/reference/components/pyroscope.scrape/)
-- [pyroscope.write](https://grafana.com/docs/agent/<AGENT_VERSION>/flow/reference/components/pyroscope.write/)
-- [discovery.kubernetes](https://grafana.com/docs/agent/<AGENT_VERSION>/flow/reference/components/discovery.kubernetes/)
-- [discovery.docker](https://grafana.com/docs/agent/<AGENT_VERSION>/flow/reference/components/discovery.docker/)
-- [discovery.relabel](https://grafana.com/docs/agent/<AGENT_VERSION>/flow/reference/components/discovery.relabel/)
diff --git a/docs/sources/configure-client/grafana-agent/java/_index.md b/docs/sources/configure-client/grafana-agent/java/_index.md
index be490cf96a..c90a44be35 100644
--- a/docs/sources/configure-client/grafana-agent/java/_index.md
+++ b/docs/sources/configure-client/grafana-agent/java/_index.md
@@ -1,27 +1,23 @@
 ---
-title: "Profiling Java using Grafana Alloy or Agent"
-menuTitle: "Profiling Java using Alloy or Agent"
-description: "Learn about using Grafana Alloy or Agent for continuous profiling Java processes for performance optimization."
+title: "Profiling Java using Grafana Alloy"
+menuTitle: "Profiling Java using Alloy"
+description: "Learn about using Grafana Alloy for continuous profiling Java processes for performance optimization."
 weight: 20
 ---
 
-# Profiling Java using Grafana Alloy or Agent
-
-Grafana Alloy (preferred) and Grafana Agent (legacy) in [Flow mode](/docs/agent/latest/flow/) support Java profiling.
+# Profiling Java using Grafana Alloy
 
+Grafana Alloy supports Java profiling.
 The collector configuration file is composed of components that are used to collect,
 transform, and send data.
-Alloy configuration files use the Alloy [configuration syntax](https://grafana.com/docs/alloy/<ALLOY_VERSION>/concepts/configuration-syntax/).
-Agent Flow files use the [River](https://grafana.com/docs/agent/<AGENT_VERSION>/flow/concepts/config-language/) language.
-
-{{< docs/shared lookup="agent-deprecation.md" source="alloy" version="next" >}}
+The Alloy configuration files use the Alloy [configuration syntax](https://grafana.com/docs/alloy/<ALLOY_VERSION>/concepts/configuration-syntax/).
 
 ## Configure the components
 
 The [`pyroscope.java` component](https://grafana.com/docs/alloy/<ALLOY_VERSION>/reference/components/pyroscope/pyroscope.java/) is used to continuously profile Java processes running on the local Linux OS
 using [async-profiler](https://github.com/async-profiler/async-profiler).
 
-```river
+```alloy
 pyroscope.java "java" {
   profiling_config {
     interval = "15s"
@@ -75,18 +71,17 @@ see [profiler-options](https://github.com/async-profiler/async-profiler?tab=read
 
 ### Set privileges for the collector
 
-You must run the collector, either Grafana Alloy (recommended) or Agent (legacy), as root and inside host `pid` namespace for the `pyroscope.java`
-and `discover.process` components to work.
+You must run the collector, either Grafana Alloy as root and inside host `pid` namespace for the `pyroscope.java` and `discover.process` components to work.
 
 ### Start the collector
 
-To start Grafana Alloy v1.2 and later, replace `configuration.alloy` with your configuration file name:
+To start Grafana Alloy v1.2 and later, replace `configuration.alloy` with your configuration filename:
 
 ```bash
 alloy run configuration.alloy
 ```
 
-To start Grafana Alloy v1.0/1.1, replace `configuration.alloy` with your configuration file name:
+To start Grafana Alloy v1.0 or 1.1, replace `configuration.alloy` with your configuration file name:
 
 ```bash
 alloy run --stability.level=public-preview configuration.alloy
@@ -94,10 +89,6 @@ alloy run --stability.level=public-preview configuration.alloy
 
 The `stability.level` option is required for `pyroscope.scrape` with Alloy v1.0 or v1.1. For more information about `stability.level`, refer to [the run command](https://grafana.com/docs/alloy/<ALLOY_VERSION>/reference/cli/run/#permitted-stability-levels) documentation.
 
-To start Grafana Agent, replace `configuration.river` with your configuration filename:
-```bash
-grafana-agent-flow run configuration.river
-```
 
 ### Send data to Grafana Cloud Profiles
 
@@ -105,7 +96,7 @@ When sending to Grafana Cloud Profiles, you can use the following `pyroscope.wri
 
 Ensure that you have appropriately configured the `GC_URL`, `GC_USER`, and `GC_PASSWORD` environment variables.
 
-```river
+```alloy
 pyroscope.write "endpoint" {
     endpoint {
         basic_auth {
@@ -117,14 +108,13 @@ pyroscope.write "endpoint" {
 }
 ```
 
-
 ## Examples
 
 For more robust examples, refer to the [Grafana Alloy and Agent Auto-instrumentation](https://github.com/grafana/pyroscope/tree/main/examples/grafana-agent-auto-instrumentation) examples in the Pyroscope repository.
 
 ### Profiling local process
 
-```river
+```alloy
 discovery.process "all" {
 }
 
@@ -167,7 +157,7 @@ pyroscope.write "example" {
 
 For a working example, refer to [Java profiling via auto-instrumentation example in Docker](https://github.com/grafana/pyroscope/tree/main/examples/grafana-agent-auto-instrumentation/java/docker).
 
-```river
+```alloy
 discovery.docker "local_containers" {
   host = "unix:///var/run/docker.sock"
 }
@@ -214,8 +204,7 @@ pyroscope.write "example" {
 
 For a working example, refer to [Grafana Alloy Java profiling via auto-instrumentation with Kubernetes](https://github.com/grafana/pyroscope/tree/main/examples/grafana-agent-auto-instrumentation/java/kubernetes).
 
-```river
-
+```alloy
 discovery.kubernetes "local_pods" {
   selectors {
     field = "spec.nodeName=" + env("HOSTNAME")
@@ -296,17 +285,9 @@ For more information:
 
 * [Examples](https://github.com/grafana/pyroscope/tree/main/examples/grafana-agent-auto-instrumentation/java)
 
-### Grafana Alloy
-
 - [Grafana Alloy](https://grafana.com/docs/alloy/<ALLOY_VERSION>/)
 - [pyroscope.scrape](https://grafana.com/docs/alloy/<ALLOY_VERSION>/reference/components/pyroscope/pyroscope.scrape/)
 - [pyroscope.write](https://grafana.com/docs/alloy/<ALLOY_VERSION>/reference/components/pyroscope/pyroscope.write/)
 - [discovery.kubernetes](https://grafana.com/docs/alloy/<ALLOY_VERSION>/reference/components/discovery/discovery.kubernetes/)
 - [discovery.docker](https://grafana.com/docs/alloy/<ALLOY_VERSION>/reference/components/discovery/discovery.docker/)
 - [discovery.relabel](https://grafana.com/docs/alloy/<ALLOY_VERSION>/reference/components/discovery/discovery.relabel/)
-
-### Grafana Agent
-
-* [`pyroscope.java`](/docs/agent/next/flow/reference/components/pyroscope.java/)
-* [`discovery.process`](/docs/agent/next/flow/reference/components/discovery.process/)
-* [`discovery.kubernetes`](/docs/agent/next/flow/reference/components/discovery.kubernetes/)
diff --git a/docs/sources/configure-client/grafana-agent/sampling.md b/docs/sources/configure-client/grafana-agent/sampling.md
index 49a32f6153..6b50bae290 100644
--- a/docs/sources/configure-client/grafana-agent/sampling.md
+++ b/docs/sources/configure-client/grafana-agent/sampling.md
@@ -1,29 +1,29 @@
 ---
 title: "Sampling scrape targets"
 menuTitle: "Sampling targets"
-description: "Sampling scrape targets with the Grafana Agent"
+description: "Sampling scrape targets with Grafana Alloy"
 weight: 30
 ---
 
 # Sampling scrape targets
 
-Applications often have many instances deployed. While Pyroscope is designed to handle large amounts of profiling data, you may want only a subset of the application's instances to be scraped.
+Applications often have many instances deployed.
+While Pyroscope is designed to handle large amounts of profiling data, you may want only a subset of the application's instances to be scraped.
 
 For example, the volume of profiling data your application generates may make it unreasonable to profile every instance, or you might be targeting cost-reduction.
 
-Through configuration of Grafana Alloy (preferred) or Grafana Agent (legacy) collectors, Pyroscope can sample scrape targets.
-
-{{< docs/shared source="alloy" lookup="agent-deprecation.md" version="next" >}}
+Through configuration of Grafana Alloy collector, Pyroscope can sample scrape targets.
 
 ## Before you begin
 
 Make sure you understand how to configure the collector to scrape targets and are familiar with the component configuration language.
 Alloy configuration files use the Alloy [configuration syntax](https://grafana.com/docs/alloy/latest/concepts/configuration-syntax/).
-Agent Flow files use the [River](https://grafana.com/docs/agent/latest/flow/concepts/config-language/) language.
 
 ## Configuration
 
-The `hashmod` action and the `modulus` argument are used in conjunction to enable sampling behavior by sharding one or more labels. To read further on these concepts, refer to [rule block documentation](/docs/agent/latest/flow/reference/components/discovery.relabel#rule-block). In short, `hashmod` performs an MD5 hash on the source labels and `modulus` performs a modulus operation on the output.
+The `hashmod` action and the `modulus` argument are used in conjunction to enable sampling behavior by sharding one or more labels.
+To read further on these concepts, refer to [rule block documentation](https://grafana.com/docs/alloy/<ALLOY_VERSION>/reference/components/discovery/discovery.relabel/#rule-block).
+In short, `hashmod` performs an MD5 hash on the source labels and `modulus` performs a modulus operation on the output.
 
 The sample size can be modified by changing the value of `modulus` in the `hashmod` action and the `regex` argument in the `keep` action.
 The `modulus` value defines the number of shards, while the `regex` value selects a subset of the shards.
@@ -37,7 +37,7 @@ Choose your source label(s) for the `hashmod` action carefully. They must unique
 For example, consider an application deployed on Kubernetes with 100 pod replicas, all uniquely identified by the label `pod_hash`.
 The following configuration is set to sample 15% of the pods:
 
-```river
+```alloy
 discovery.kubernetes "profile_pods" {
   role = "pod"
 }
diff --git a/docs/sources/configure-client/language-sdks/go_push.md b/docs/sources/configure-client/language-sdks/go_push.md
index e06e6267f7..a5b22f65aa 100644
--- a/docs/sources/configure-client/language-sdks/go_push.md
+++ b/docs/sources/configure-client/language-sdks/go_push.md
@@ -31,12 +31,12 @@ The Pyroscope server can be a local server for development or a remote server fo
 
 To start profiling a Go application, you need to include the Go module in your app:
 
-```
+```go
 go get github.com/grafana/pyroscope-go
 ```
 
 {{% admonition type="note" %}}
-If you'd prefer to use Pull mode you can do so using the [Grafana Agent]({{< relref "../grafana-agent" >}}).
+If you'd prefer to use Pull mode you can do so using [Grafana Alloy](https://grafana.com/docs/pyroscope/<PYROSCOPE_VERSION>/configure-client/grafana-agent/).
 {{% /admonition %}}
 
 Then add the following code to your application:
diff --git a/docs/sources/configure-client/language-sdks/nodejs.md b/docs/sources/configure-client/language-sdks/nodejs.md
index 2e59ccae6d..79baf7bae1 100644
--- a/docs/sources/configure-client/language-sdks/nodejs.md
+++ b/docs/sources/configure-client/language-sdks/nodejs.md
@@ -49,7 +49,7 @@ Pyroscope.start()
 
 [comment]: <> (TODO This needs its own page like https://grafana.com/docs/pyroscope/latest/configure-client/grafana-agent/go_pull/)
 {{< admonition type="note" >}}
-If you'd prefer, you can use Pull mode using [Grafana Alloy](https://grafana.com/docs/alloy/latest/) (recommended) or [Grafana Agent]({{< relref "../grafana-agent" >}}) (legacy).
+If you'd prefer, you can use Pull mode using [Grafana Alloy](https://grafana.com/docs/pyroscope/<PYROSCOPE_VERSION>/configure-client/grafana-agent/).
 {{< /admonition >}}
 
 
@@ -100,7 +100,7 @@ Pyroscope.start()
 
 #### Dynamic labels for Wall/CPU profiles
 
-In Wall/CPU profiles, labels can also be attached dynamically and help to separate different code paths:
+In Wall and CPU profiles, labels can also be attached dynamically and help to separate different code paths:
 
 ```javascript
 Pyroscope.wrapWithLabels({ vehicle: 'bike' }, () =>
diff --git a/docs/sources/deploy-kubernetes/helm.md b/docs/sources/deploy-kubernetes/helm.md
index e6c951bd6f..4565a017d4 100644
--- a/docs/sources/deploy-kubernetes/helm.md
+++ b/docs/sources/deploy-kubernetes/helm.md
@@ -142,15 +142,15 @@ Use a custom namespace so that you don't have to overwrite the default namespace
    ```
 
 1. In a browser, go to the Grafana server at [http://localhost:3000](http://localhost:3000).
-1. On the left-hand side, go to **Configuration** > **Data sources**.
-1. Configure a new Pyroscope data source to query the Pyroscope server, by using the following settings:
+1. On the left side, go to **Configuration** > **Data sources**.
+1. Configure a Pyroscope data source to query the Pyroscope server, by using the following settings:
 
    | Field | Value                                                        |
    | ----- | ------------------------------------------------------------ |
    | Name  | Pyroscope                                                       |
    | URL   | `http://pyroscope-querier.pyroscope-test.svc.cluster.local.:4040/`   |
 
-   To add a data source, see [Add a data source](/docs/grafana/latest/datasources/add-a-data-source/).
+   To add a data source, refer to [Add a data source](/docs/grafana/latest/datasources/add-a-data-source/).
 
 1. Verify success:
 
@@ -184,9 +184,9 @@ Modify the Helm deployment by running:
 ## Optional: Scrape your own workload's profiles
 
 The Pyroscope chart uses a default configuration that causes its agent to scrape Pods, provided they have the correct annotations.
-This functionality uses [relabel_config](https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config) and [kubernetes_sd_config](https://prometheus.io/docs/prometheus/latest/configuration/configuration/#kubernetes_sd_config) you might be familiar with the Prometheus or Grafana Agent config.
+This functionality uses [relabel_config](https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config) and [kubernetes_sd_config](https://prometheus.io/docs/prometheus/latest/configuration/configuration/#kubernetes_sd_config) you might be familiar with the Prometheus or Grafana Alloy configuration.
 
-To get Pyroscope to scrape pods, you must add the following annotations to the  pods:
+To get Pyroscope to scrape pods, you must add the following annotations to the Pods:
 
 ```yaml
 metadata:
@@ -199,7 +199,7 @@ metadata:
     profiles.grafana.com/goroutine.port: "8080"
 ```
 
-The above example will scrape the `memory`, `cpu` and `goroutine` profiles from the `8080` port of the pod.
+The above example will scrape the `memory`, `cpu` and `goroutine` profiles from the `8080` port of the Pod.
 
 Each profile type has a set of corresponding annotations which allows customization of scraping per profile type.
 
@@ -225,7 +225,7 @@ The following table describes the annotations:
 | `profiles.grafana.com/<profile-type>.scheme` | The scheme to scrape the profile type from. | `http` |
 | `profiles.grafana.com/<profile-type>.path` | The path to scrape the profile type from. | default golang path |
 
-By default, the port will be discovered using named port `http2` or ending with `-metrics` or `-profiles`.
-If you don't have a named port, the scraping target will be dropped.
+By default, the port is discovered using named port `http2` or ending with `-metrics` or `-profiles`.
+If you don't have a named port, the scraping target is dropped.
 
 If you don't want to use the port name, then you can use the `profiles.grafana.com/<profile-type>.port` annotation to statically specify the port number.
diff --git a/docs/sources/get-started/_index.md b/docs/sources/get-started/_index.md
index 5ea78e1fc9..595d63de0c 100644
--- a/docs/sources/get-started/_index.md
+++ b/docs/sources/get-started/_index.md
@@ -74,13 +74,13 @@ Verify that you have installed [Docker](https://docs.docker.com/engine/install/)
 1. Configure Pyroscope to scrape profiles.
 
     By default, Pyroscope is configured to scrape itself.
-    To collect more profiles, you must either instrument your application with an SDK or use the Grafana Agent.
+    To collect more profiles, you must either instrument your application with an SDK or use Grafana Alloy.
 
     To learn more about language integrations and the Pyroscope agent, refer to [Pyroscope Agent]({{< relref "../configure-client/_index.md" >}}).
 
 ## Add a Pyroscope data source and query data
 
-1. In a new terminal, run a local Grafana server using Docker:
+1. In a terminal, run a local Grafana server using Docker:
 
     ```bash
     docker run --rm --name=grafana \
@@ -105,4 +105,4 @@ Verify that you have installed [Docker](https://docs.docker.com/engine/install/)
   To learn more about adding data sources, refer to [Add a data source](/docs/grafana/<GRAFANA_VERSION>/datasources/add-a-data-source/).
 
 When you have completed the tasks in this getting started guide, you can query profiles in [Grafana Explore](/docs/grafana/<GRAFANA_VERSION>/explore/)
-and create dashboard panels using the newly configured Pyroscope data source. For more information on working with dashboards with Grafana, see [Panels and visualizations](/docs/grafana/<GRAFANA_VERSION>/panels-visualizations/) in the Grafana documentation.
+and create dashboard panels using the newly configured Pyroscope data source. For more information on working with dashboards with Grafana, refer to [Panels and visualizations](/docs/grafana/<GRAFANA_VERSION>/panels-visualizations/) in the Grafana documentation.