Skip to content

Commit b520443

Browse files
authored
[chore] Spelling: walkthroughs + workaround (#6021)
1 parent 14daaf1 commit b520443

File tree

2 files changed

+6
-6
lines changed
  • content/en
    • blog/2022/announcing-opentelemetry-demo-release
    • docs/collector/building/connector

2 files changed

+6
-6
lines changed

content/en/blog/2022/announcing-opentelemetry-demo-release/index.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ Now, it’d be enough to just provide a great demonstration of OpenTelemetry, bu
3737
one thing we wanted to focus on for our 1.0 release was showing not just the
3838
‘how’, but the ‘why’, of OpenTelemetry. To that end, we’ve built a framework for
3939
implementing [failure scenarios](/docs/demo/#scenarios) gated by feature flags.
40-
In addition, we include pre-configured dashboards and walk-throughs in our docs
40+
In addition, we include pre-configured dashboards and walkthroughs in our docs
4141
on how to read and interpret the telemetry data each service emits to discover
4242
the underlying cause of performance regressions in the application.
4343

content/en/docs/collector/building/connector/index.md

+5-5
Original file line numberDiff line numberDiff line change
@@ -41,11 +41,11 @@ services. Both these processors ingest trace data and convert them to metrics
4141
data. Since pipelines in the OpenTelemetry Collector are for only one type of
4242
data, it is necessary to convert the trace data from the processor in the traces
4343
pipeline and send it to the metrics pipeline. Historically, some processors
44-
transmitted data by making use of a work-around that follows a bad practice
45-
where a processor directly exports data after processing. The connector
46-
component solves the need for this work-around and the processors that used the
47-
work around have been deprecated. On the same line, above mentioned processors
48-
are also now deprecated in recent releases and are replaced by the connectors.
44+
transmitted data by making use of a workaround that follows a bad practice where
45+
a processor directly exports data after processing. The connector component
46+
solves the need for this work-around and the processors that used the work
47+
around have been deprecated. On the same line, above mentioned processors are
48+
also now deprecated in recent releases and are replaced by the connectors.
4949

5050
Additional details about the connector's full capabilities can be found at the
5151
following links:

0 commit comments

Comments
 (0)