Remove a few instances of agent

grafana · Mar 28, 2024 · 368b952 · 368b952
1 parent d58d7b0
commit 368b952
Show file tree

Hide file tree

Showing 4 changed files with 4 additions and 9 deletions.
diff --git a/docs/sources/about.md b/docs/sources/about.md
@@ -118,11 +118,7 @@ The following tables compare {{< param "PRODUCT_NAME" >}} with OpenTelemetry and
 [sla]: https://grafana.com/legal/grafana-cloud-sla
 [observability]: https://grafana.com/docs/grafana-cloud/monitor-applications/application-observability/setup#send-telemetry
 
-[integrations]: https://grafana.com/docs/agent/static/configuration/integrations/
 [components]: ./reference/components
-[Static mode]: https://grafana.com/docs/agent/static/
-[Static mode Kubernetes operator]: https://grafana.com/docs/agent/operator/
-[Flow mode]: https://grafana.com/docs/agent/flow/
 [Prometheus]: ./tasks/collect-prometheus-metrics/
 [OTel]: ./tasks/collect-opentelemetry-data/
 [Loki]: ./tasks/migrate/from-promtail/

diff --git a/docs/sources/concepts/component_controller.md b/docs/sources/concepts/component_controller.md
@@ -94,7 +94,7 @@ If your `local.file` component, which watches API keys, suddenly stops working,
 Components that expose HTTP endpoints, such as [prometheus.exporter.unix][], can expose an internal address that completely bypasses the network and communicate in-memory.
 Components within the same process can communicate with one another without needing to be aware of any network-level protections such as authentication or mutual TLS.
 
-The internal address defaults to `agent.internal:12345`.
+The internal address defaults to `alloy.internal:12345`.
 If this address collides with a real target on your network, change it to something unique using the `--server.http.memory-addr` flag in the [run][] command.
 
 Components must opt-in to using in-memory traffic.

diff --git a/docs/sources/concepts/configuration-syntax/_index.md b/docs/sources/concepts/configuration-syntax/_index.md
@@ -37,7 +37,7 @@ BLOCK_NAME {
 }
 ```
 
-[{{< param "PRODUCT_NAME" >}} is designed][RFC] with the following requirements in mind:
+{{< param "PRODUCT_NAME" >}} is designed with the following requirements in mind:
 
 * _Fast_: The configuration language must be fast so the component controller can quickly evaluate changes.
 * _Simple_: The configuration language must be easy to read and write to minimize the learning curve.
@@ -113,7 +113,6 @@ You can use one or all of the following tools to help you write {{< param "PRODU
 * Editor support for:
   * [VSCode](https://github.com/grafana/vscode-alloy)
   * [Vim/Neovim](https://github.com/grafana/vim-alloy)
-* Code formatting using the [`agent fmt` command][fmt]
+* Code formatting using the [`alloy fmt` command][fmt]
 
-[RFC]: https://github.com/grafana/agent/blob/97a55d0d908b26dbb1126cc08b6dcc18f6e30087/docs/rfcs/0005-river.md
 [fmt]: ../../reference/cli/fmt/
diff --git a/docs/sources/concepts/configuration-syntax/components.md b/docs/sources/concepts/configuration-syntax/components.md
@@ -37,7 +37,7 @@ that configure how and how often the file should be polled and whether its conte
 ```alloy
 local.file "targets" {
   // Required argument
-  filename = "/etc/agent/targets"
+  filename = "/etc/alloy/targets"
 
   // Optional arguments: Components may have some optional arguments that
   // do not need to be defined.