From 4c5b836ea9eaaa198c2dbeb3a78e1eeff7e95cb2 Mon Sep 17 00:00:00 2001 From: Patrice Chalin Date: Tue, 16 Jan 2024 09:46:30 -0500 Subject: [PATCH] Fix format --- content/en/blog/2022/k8s-otel-expose/index.md | 4 ++-- content/en/docs/collector/_index.md | 7 +++---- content/en/docs/collector/management.md | 4 ++-- content/en/docs/languages/python/getting-started.md | 6 +++--- 4 files changed, 10 insertions(+), 11 deletions(-) diff --git a/content/en/blog/2022/k8s-otel-expose/index.md b/content/en/blog/2022/k8s-otel-expose/index.md index ef7a97739328..e04bf6e6c0b5 100644 --- a/content/en/blog/2022/k8s-otel-expose/index.md +++ b/content/en/blog/2022/k8s-otel-expose/index.md @@ -106,8 +106,8 @@ in this setup are mentioned in brackets. [v1.2.1] installed. - A Kubernetes [v1.23.3] edge cluster to create a test cluster. Using [Kind](https://kind.sigs.k8s.io/) is recommended. -- Installed [OpenTelemetry Operator](/docs/kubernetes/operator/) [v0.58.0] - on both ends. +- Installed [OpenTelemetry Operator](/docs/kubernetes/operator/) [v0.58.0] on + both ends. - Installed [Jaeger Operator](https://www.jaegertracing.io/docs/1.37/operator/) [v1.37.0] on your public cluster. - Installed [cert-manager](https://cert-manager.io/) [v1.9.1] on your public diff --git a/content/en/docs/collector/_index.md b/content/en/docs/collector/_index.md index 9f4dd98d26ce..c98f5c07f718 100644 --- a/content/en/docs/collector/_index.md +++ b/content/en/docs/collector/_index.md @@ -48,10 +48,9 @@ it allows your service to offload data quickly and the collector can take care of additional handling like retries, batching, encryption or even sensitive data filtering. -It is also easier to [setup a collector](quick-start) than you might -think: the default OTLP exporters in each language assume a local collector -endpoint, so if you launch a collector it will automatically start receiving -telemetry. +It is also easier to [setup a collector](quick-start) than you might think: the +default OTLP exporters in each language assume a local collector endpoint, so if +you launch a collector it will automatically start receiving telemetry. ## Status and releases diff --git a/content/en/docs/collector/management.md b/content/en/docs/collector/management.md index 42a8c04a8116..d41987eea02b 100644 --- a/content/en/docs/collector/management.md +++ b/content/en/docs/collector/management.md @@ -11,8 +11,8 @@ deployment at scale. To get the most out of this page you should know how to install and configure the collector. These topics are covered elsewhere: -- [Quick Start](/docs/collector/quick-start/) to understand how to install - the OpenTelemetry Collector. +- [Quick Start](/docs/collector/quick-start/) to understand how to install the + OpenTelemetry Collector. - [Configuration][otel-collector-configuration] for how to configure the OpenTelemetry Collector, setting up telemetry pipelines. diff --git a/content/en/docs/languages/python/getting-started.md b/content/en/docs/languages/python/getting-started.md index 35fd467b7261..b9e291389f93 100644 --- a/content/en/docs/languages/python/getting-started.md +++ b/content/en/docs/languages/python/getting-started.md @@ -640,9 +640,9 @@ emitted to the console, with separate counts for each roll value: ## Send telemetry to an OpenTelemetry Collector -The [OpenTelemetry Collector](/docs/collector/) is a critical -component of most production deployments. Some examples of when it's beneficial -to use a collector: +The [OpenTelemetry Collector](/docs/collector/) is a critical component of most +production deployments. Some examples of when it's beneficial to use a +collector: - A single telemetry sink shared by multiple services, to reduce overhead of switching exporters