Editorial changes to Concepts > Signals (#6067)

Author: chalin

content/en/docs/concepts/signals/_index.md

@@ -1,13 +1,11 @@
 ---
 title: Signals
 description: Learn about the categories of telemetry supported by OpenTelemetry
-aliases:
-  - /docs/concepts/data-sources
-  - /docs/concepts/otel-concepts
+aliases: [./data-sources, ./otel-concepts]
 weight: 11
 ---
 
-The purpose of OpenTelemetry is to collect, process, and export **[signals][]**.
+The purpose of OpenTelemetry is to collect, process, and export [signals].
 Signals are system outputs that describe the underlying activity of the
 operating system and applications running on a platform. A signal can be
 something you want to measure at a specific point in time, like temperature or
@@ -16,11 +14,21 @@ system that you'd like to trace. You can group different signals together to
 observe the inner workings of the same piece of technology under different
 angles.
 
-OpenTelemetry currently supports [traces](/docs/concepts/signals/traces),
-[metrics](/docs/concepts/signals/metrics), [logs](/docs/concepts/signals/logs)
-and [baggage](/docs/concepts/signals/baggage). _Events_ are a specific type of
-log, and
-[_profiles_ are being worked on](https://github.com/open-telemetry/opentelemetry-specification/blob/main/oteps/profiles/0212-profiling-vision.md)
-by the Profiling Working Group.
+OpenTelemetry currently supports:
 
+- [Traces](traces)
+- [Metrics](metrics)
+- [Logs](logs)
+- [Baggage](baggage)
+
+Also under development or at the [proposal] stage:
+
+- [Events], a specific type of [log](logs)
+- [Profiles] are being worked on by the Profiling Working Group.
+
+[Events]: /docs/specs/otel/logs/data-model/#events
+[Profiles]:
+  https://github.com/open-telemetry/opentelemetry-specification/blob/main/oteps/profiles/0212-profiling-vision.md
+[proposal]:
+  https://github.com/open-telemetry/opentelemetry-specification/tree/main/oteps/#readme
 [signals]: /docs/specs/otel/glossary/#signals

content/en/docs/concepts/signals/baggage.md

@@ -6,13 +6,12 @@ description: Contextual information that is passed between signals.
 
 In OpenTelemetry, Baggage is contextual information that resides next to
 context. Baggage is a key-value store, which means it lets you
-[propagate](/docs/concepts/context-propagation/#propagation) any data you like
-alongside [context](/docs/concepts/context-propagation/#context).
+[propagate](../../context-propagation/#propagation) any data you like alongside
+[context](../../context-propagation/#context).
 
 Baggage means you can pass data across services and processes, making it
-available to add to [traces](/docs/concepts/signals/traces/),
-[metrics](/docs/concepts/signals/metrics/), or
-[logs](/docs/concepts/signals/logs/) in those services.
+available to add to [traces](../traces/), [metrics](../metrics/), or
+[logs](../logs/) in those services.
 
 ## Example
 
@@ -24,13 +23,12 @@ another service, and some logs along the way. Because the trace may span
 multiple services, you need some way to propagate that data without copying the
 `clientId` across many places in your codebase.
 
-By using
-[Context Propagation](/docs/concepts/signals/traces/#context-propagation) to
-pass baggage across these services, the `clientId` is available to add to any
-additional spans, metrics, or logs. Additionally, instrumentations automatically
-propagate baggage for you.
+By using [Context Propagation](../traces/#context-propagation) to pass baggage
+across these services, the `clientId` is available to add to any additional
+spans, metrics, or logs. Additionally, instrumentations automatically propagate
+baggage for you.
 
-![OTel Baggage](/img/otel-baggage.svg)
+![OTel Baggage](../otel-baggage.svg)
 
 ## What should OTel Baggage be used for?
 
@@ -45,7 +43,7 @@ like "which users are experiencing the slowest database calls?" You can also log
 information about a downstream operation and include that same User ID in the
 log data.
 
-![OTel Baggage](/img/otel-baggage-2.svg)
+![OTel Baggage](../otel-baggage-2.svg)
 
 ## Baggage security considerations
 
@@ -70,10 +68,10 @@ To add baggage entries to attributes, you need to explicitly read the data from
 baggage and add it as attributes to your spans, metrics, or logs.
 
 Because a common use cases for Baggage is to add data to
-[Span Attributes](/docs/concepts/signals/traces/#attributes) across a whole
-trace, several languages have Baggage Span Processors that add data from baggage
-as attributes on span creation.
+[Span Attributes](../traces/#attributes) across a whole trace, several languages
+have Baggage Span Processors that add data from baggage as attributes on span
+creation.
 
-> For more information, see the [baggage specification][].
+> For more information, see the [baggage specification].
 
 [baggage specification]: /docs/specs/otel/overview/#baggage-signal

content/en/docs/concepts/signals/logs.md

@@ -16,7 +16,7 @@ OpenTelemetry does not define a bespoke API or SDK to create logs. Instead,
 OpenTelemetry logs are the existing logs you already have from a logging
 framework or infrastructure component. OpenTelemetry SDKs and
 autoinstrumentation utilize several components to automatically correlate logs
-with [traces](/docs/concepts/signals/traces).
+with [traces](../traces).
 
 OpenTelemetry's support for logs is designed to be fully compatible with what
 you already have, providing capabilities to wrap those logs with additional
@@ -25,7 +25,7 @@ across many different sources.
 
 ### OpenTelemetry logs in the OpenTelemetry Collector
 
-The [OpenTelemetry Collector](/docs/collector) provides several tools to work
+The [OpenTelemetry Collector](/docs/collector/) provides several tools to work
 with logs:
 
 - Several receivers which parse logs from specific, known sources of log data.

content/en/docs/concepts/signals/metrics.md

@@ -91,10 +91,10 @@ aggregation for each instrument which can be overridden using the Views. The
 OpenTelemetry project aims to provide default aggregations that are supported by
 visualizers and telemetry backends.
 
-Unlike [request tracing](/docs/concepts/signals/traces/), which is intended to
-capture request lifecycles and provide context to the individual pieces of a
-request, metrics are intended to provide statistical information in aggregate.
-Some examples of use cases for metrics include:
+Unlike [request tracing](../traces/), which is intended to capture request
+lifecycles and provide context to the individual pieces of a request, metrics
+are intended to provide statistical information in aggregate. Some examples of
+use cases for metrics include:
 
 - Reporting the total number of bytes read by a service, per protocol type.
 - Reporting the total number of bytes read and the bytes per request.

static/img/otel-baggage-2.svg content/en/docs/concepts/signals/otel-baggage-2.svg

@@ -160,8 +160,7 @@ source or vendor backend of your choice.
 Context Propagation is the core concept that enables Distributed Tracing. With
 Context Propagation, Spans can be correlated with each other and assembled into
 a trace, regardless of where Spans are generated. To learn more about this
-topic, see the concept page on
-[Context Propagation](/docs/concepts/context-propagation).
+topic, see the concept page on [Context Propagation](../../context-propagation).
 
 ## Spans
 
@@ -231,8 +230,7 @@ Span context is an immutable object on every span that contains the following:
   information
 
 Span context is the part of a span that is serialized and propagated alongside
-[Distributed Context](#context-propagation) and
-[Baggage](/docs/concepts/signals/baggage).
+[Distributed Context](#context-propagation) and [Baggage](../baggage).
 
 Because Span Context contains the Trace ID, it is used when creating
 [Span Links](#span-links).

static/img/otel-baggage.svg content/en/docs/concepts/signals/otel-baggage.svg

@@ -38,7 +38,7 @@ the site.
 | OpenTelemetry | OpenTelemetry should always be capitalized. Don't use Open-Telemetry. |
 | OTel | OTel is the accepted short form of OpenTelemetry. Don't use OTEL. |
 | Collector | When referring to the OpenTelemetry Collector, always capitalize Collector. Write "The Collector" or "The Opentelemetry Collector" if you're starting a sentence. Write "the Collector" or "the OpenTelemetry Collector" in the middle or end of a sentence. Use just "Collector" if you are using Collector as an adjective (for example, "Collector configuration").|
-| OTEP | OpenTelemetry Enhancement Proposal. Write "OTEPs" as plural form. Don't write "OTep" or "otep". |
+| OTEP | [OpenTelemetry Enhancement Proposal]. Write "OTEPs" as plural form. Don't write "OTep" or "otep". |
 | OpAMP | Open Agent Management Protocol. Don't write "OPAMP" or "opamp" in descriptions or instructions. |
 <!-- prettier-ignore-end -->
 
@@ -116,3 +116,6 @@ submitting a PR, or run it afterwards and push an additional commit.
 All file names should be in
 [kebab case](https://en.wikipedia.org/wiki/Letter_case#Kebab_case). Run
 `npm run fix:filenames` to automatically rename your files.
+
+[OpenTelemetry Enhancement Proposal]:
+  https://github.com/open-telemetry/opentelemetry-specification/blob/main/oteps/README.md

content/en/docs/concepts/signals/traces.md

@@ -22,7 +22,7 @@ OpenTelemetryでは、バゲッジ（Baggage）はコンテキストの隣にあ
 [コンテキスト伝搬](/docs/concepts/signals/traces/#context-propagation)を使用して、これらのサービス間でバゲッジを渡すことで、 `clientId` を追加のスパン、メトリクス、またはログに追加できます。
 さらに、計装は自動的にバゲッジを伝搬してくれます。
 
-![OTel Baggage](/img/otel-baggage.svg)
+![OTel Baggage](../otel-baggage.svg)
 
 ## OTelバゲッジの使い道 {#what-should-otel-baggage-be-used-for}
 
@@ -33,7 +33,7 @@ OpenTelemetryでは、バゲッジ（Baggage）はコンテキストの隣にあ
 たとえば、データベース呼び出しを追跡するスパンにユーザーIDのような情報を含めると、「どのユーザーがもっとも遅いデータベース呼び出しを経験しているか」のような質問に、より簡単に答えられます。
 また、下流の操作に関する情報をログに記録し、同じユーザーIDをログデータに含めることもできます。
 
-![OTel Baggage](/img/otel-baggage-2.svg)
+![OTel Baggage](../otel-baggage-2.svg)
 
 ## バゲッジのセキュリティに関する懸念事項 {#baggage-security-considerations}
 

content/en/docs/contributing/style-guide.md

@@ -32,7 +32,7 @@ Usando a
 para passar a bagagem entre esses serviços, o `clientId` estará disponível para
 ser adicionado a quaisquer trechos, métricas ou logs. Além disso, as
 instrumentações automaticamente propagam a Bagagem para você.
-![OTel Baggage](/img/otel-baggage.svg)
+![OTel Baggage](../otel-baggage.svg)
 
 ## Para que a Bagagem do OTel deve ser usada?
 
@@ -49,7 +49,7 @@ enfrentando as chamadas de banco de dados mais lentas?". Você também pode
 registrar informações sobre uma operação posterior e incluir esse mesmo ID de
 usuário nos dados do log.
 
-![OTel Baggage](/img/otel-baggage-2.svg)
+![OTel Baggage](../otel-baggage-2.svg)
 
 ## Considerações de segurança da Bagagem
 

content/ja/docs/concepts/signals/baggage.md

@@ -11239,6 +11239,10 @@
     "StatusCode": 206,
     "LastSeen": "2025-01-17T16:51:50.076193-05:00"
   },
+  "https://github.com/open-telemetry/opentelemetry-specification/blob/main/oteps/README.md": {
+    "StatusCode": 206,
+    "LastSeen": "2025-01-24T07:05:45.681053-05:00"
+  },
   "https://github.com/open-telemetry/opentelemetry-specification/blob/main/oteps/profiles/0212-profiling-vision.md": {
     "StatusCode": 206,
     "LastSeen": "2025-01-17T16:51:52.507046-05:00"
@@ -11375,6 +11379,10 @@
     "StatusCode": 200,
     "LastSeen": "2024-01-30T15:25:05.874801-05:00"
   },
+  "https://github.com/open-telemetry/opentelemetry-specification/tree/main/oteps/#readme": {
+    "StatusCode": 206,
+    "LastSeen": "2025-01-24T07:06:27.879024-05:00"
+  },
   "https://github.com/open-telemetry/opentelemetry-specification/tree/main/specification/README.md": {
     "StatusCode": 206,
     "LastSeen": "2025-01-17T16:52:05.751476-05:00"