@@ -26,7 +26,7 @@ mechanisms we'll use to get there.
2626 complexity of OpenTelemetry and lack of stability creates impediments to
2727 production deployments.
2828
29- ** Our Goals**
29+ ### Our Goals
3030
3131- Ensure that all OpenTelemetry distributions are 'stable by default' and
3232 provide standardized mechanisms for users to opt-in to experimental or
@@ -172,7 +172,7 @@ feedback on these objectives in the
172172In order to achieve our stability goals, we'll need to address semantic
173173convention stability and processes as well.
174174
175- ### Background
175+ ### Semantic Convention Challenges
176176
177177Semantic conventions evolve slowly and deliberately because they must work
178178across diverse telemetry systems. While OpenTelemetry is designed for
@@ -191,7 +191,7 @@ requires a long commitment. Finally, we're internally inconsistent in
191191instrumentation across the project; Some libraries are mapped to conventions,
192192others exist independently of it.
193193
194- ### Goals and Objectives
194+ ### Instrumentation and Convention Goals
195195
196196Our goals here are designed to achieve three outcomes.
197197
@@ -237,7 +237,7 @@ semantic conventions are a big part of that.
237237
238238## 3. Confident and Stable Releases.
239239
240- ## Background
240+ ### The Challenge
241241
242242OpenTelemetry isn't just a single binary deployed into a Kubernetes cluster.
243243Subtle differences in everything from configuration to telemetry output between
@@ -248,7 +248,7 @@ Collector. Enterprise deployments and upgrades are slow, deliberate things --
248248teams simply do not have the bandwidth to validate and roll out changes at the
249249cadence we ship.
250250
251- ## Goals and Objectives
251+ ### Release Goals and Strategy
252252
253253Ultimately, our goal here is to make it easier for large organizations to deploy
254254OpenTelemetry. Please keep in mind that in many organizations, 'deployment' and
0 commit comments