Skip to content

Commit a3fd615

Browse files
committed
review feedback
1 parent 129cb8f commit a3fd615

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

docs/migration_0.29.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -8,15 +8,15 @@ please refer to the detailed changelog for each crate. This document covers only
88
the most common scenarios. Note that changes that only affect custom
99
exporter/processor authors are not mentioned in this doc.
1010

11-
OpenTelemetry Metrics API, Log-Bridge API were declared stable in 0.28, and has
11+
OpenTelemetry Metrics API and Log-Bridge API were declared stable in 0.28, and have
1212
no breaking changes.
1313

1414
## Baggage Changes
1515

1616
The Baggage API has been redesigned to align with the OpenTelemetry
1717
specification. While the core API for interacting with Baggage remains the same,
1818
the accepted data types have changed. Baggage Keys now only allow strings (ASCII
19-
visual characters), and Baggage values are restricted to strings.
19+
printable characters), and Baggage values are restricted to strings.
2020

2121
For detailed changes, see the [changelog](../opentelemetry/CHANGELOG.md). With
2222
version 0.29, the Baggage API has reached "Release Candidate" status, meaning
@@ -50,7 +50,7 @@ current `opentelemetry-prometheus` crate requires a major rewrite to eliminate
5050
dependencies on unmaintained crates. We may reintroduce a dedicated Prometheus
5151
exporter in the future once these issues are resolved.
5252

53-
### Migration guide
53+
### Migration Guide
5454

5555
For those using Prometheus as a backend, you can integrate with Prometheus using
5656
the following methods:
@@ -68,8 +68,8 @@ focus on achieving a stable 1.0 release for OpenTelemetry Rust.
6868
In the [next
6969
release](https://github.com/open-telemetry/opentelemetry-rust/milestone/21), we
7070
expect to stabilize the Metrics SDK and resolve the long-standing question of
71-
`tokio-tracing` vs. `opentelemetry tracing`, which is an pre-req before
72-
stabilizing Distributed Tracing. Additionally `Context` is also expected to be
71+
`tokio-tracing` vs. `opentelemetry tracing`, which is an prerequisite before
72+
stabilizing Distributed Tracing. Additionally, `Context` is also expected to be
7373
enhanced with the ability to suppress telemetry-induced-telemetry.
7474

7575
## Instrumentation Libraries

0 commit comments

Comments
 (0)