open-telemetry · jsoref · Jan 12, 2025 · Jan 12, 2025 · Jan 12, 2025 · Jan 12, 2025
@@ -10,7 +10,7 @@ jobs:
   auto-update-versions:
     name: Auto-update community members page
     runs-on: ubuntu-24.04
-    # Remove the if statement below when testing againt a fork
+    # Remove the if statement below when testing against a fork
     if: github.repository == 'open-telemetry/opentelemetry.io'
     steps:
       - name: Checkout

@@ -10,7 +10,7 @@ jobs:
   auto-update-versions:
     name: Auto-update registry versions
     runs-on: ubuntu-20.04
-    # Remove the if statement below when testing againt a fork
+    # Remove the if statement below when testing against a fork
     if: github.repository == 'open-telemetry/opentelemetry.io'
     steps:
       - name: Checkout

@@ -5,7 +5,7 @@ echo "For localization docs, see https://opentelemetry.io/docs/contributing/loca
 CHANGES=`git status --porcelain`
 
 if [[ -z $CHANGES ]]; then
-  echo "All localization pages have the requisit commit hash. <3"
+  echo "All localization pages have the requisite commit hash. <3"
   exit;
 fi
 

@@ -35,6 +35,6 @@ jobs:
       - name: Add comment to PR if author is not a member
         if: env.MEMBER_FOUND == 'false'
         run: |
-          gh pr comment ${PR_NUM} --body "Thank you for your contribution! 🎉 We would like to hear from you about your experience contributing to OpenTelemetry by taking a few minutes to fill out out this survey: ${SURVEY_URL}"
+          gh pr comment ${PR_NUM} --body "Thank you for your contribution! 🎉 We would like to hear from you about your experience contributing to OpenTelemetry by taking a few minutes to fill out this survey: ${SURVEY_URL}"
         env:
           GH_TOKEN: ${{ secrets.OPENTELEMETRYBOT_GITHUB_TOKEN }}
@@ -30,7 +30,7 @@ markdown formatter (see below).
 
 ## Images
 
-If you use images, make sure that your blog post is located in it's own
+If you use images, make sure that your blog post is located in its own
 directory. Put the images into the same directory.
 
 If you have an image stored at `content/en/{{ .File.Dir }}imagename.png`, you

@@ -7,9 +7,8 @@ author: '[Sergey Kanzhelev](https://github.com/SergeyKanzhelev)'
 cSpell:ignore: Kanzhelev Novotny Sergey
 ---
 
-This article describes the functions and responsibilities of the OpenTelemetry
-Governance Committee, based on the charter document found
-[here](https://github.com/open-telemetry/community/blob/main/governance-charter.md).
+This article describes the functions and responsibilities of the
+[OpenTelemetry Governance Committee's charter document](https://github.com/open-telemetry/community/blob/main/governance-charter.md).
 It is an opinion, not the formal definition. The primary role of the Governance
 Committee is not to centralize power, but to enable and empower the broader
 community by establishing processes. Let me explain.

@@ -14,7 +14,7 @@ announce
 With this demo, you’ll be able to quickly run a complete end-to-end distributed
 system instrumented with 100% OpenTelemetry Traces and Metrics.
 
-![The system architecture of the demo application represented as directed acyclic graph in Jaeger UI](sytem-architecture.png)
+![The system architecture of the demo application represented as directed acyclic graph in Jaeger UI](system-architecture.png)
 
 One of our primary goals of this project has been to create a robust sample
 application for developers to use in learning OpenTelemetry, and we’re proud to
@@ -37,16 +37,16 @@ Now, it’d be enough to just provide a great demonstration of OpenTelemetry, bu
 one thing we wanted to focus on for our 1.0 release was showing not just the
 ‘how’, but the ‘why’, of OpenTelemetry. To that end, we’ve built a framework for
 implementing [failure scenarios](/docs/demo/#scenarios) gated by feature flags.
-In addition, we include pre-configured dashboards and walk-throughs in our docs
+In addition, we include pre-configured dashboards and walkthroughs in our docs
 on how to read and interpret the telemetry data each service emits to discover
 the underlying cause of performance regressions in the application.
 
 Another goal of this demo is to streamline the ability of vendors and commercial
 implementers of OpenTelemetry to have a standardized target for building demos
 around. We’ve already seen quite a bit of adoption, with five companies
 including Datadog, Dynatrace, Honeycomb, Lightstep, and New Relic integrating
-the community demo application into their product demos (you can find a list
-[here](https://github.com/open-telemetry/opentelemetry-demo#demos-featuring-the-astronomy-shop)).
+the community demo application into their
+[product demos](https://github.com/open-telemetry/opentelemetry-demo#demos-featuring-the-astronomy-shop).
 We hope to encourage further contributions and collaboration along these lines.
 
 However, just because we reached 1.0, that doesn’t mean we’re stopping -- this

@@ -7,7 +7,7 @@ author: '[Carter Socha](https://github.com/cartersocha)'
 
 ## TL;DR
 
-The OpenTelemetry community has taken a good pre-existing demo (thanks,
+The OpenTelemetry community has taken a good preexisting demo (thanks,
 [Google](https://github.com/GoogleCloudPlatform/microservices-demo)!) and is in
 the process of making it even better. Every GA SDK (besides Swift) will be
 represented, demo support will be extended to Metrics and Logs, and canonical
@@ -66,8 +66,8 @@ backend choice, and they’re overly reliant on instrumentation libraries.
 As a starting point, we have selected a fork of the popular GCP microservices
 demo. Our first feature additions have been to simplify local deployment by
 consolidating the project onto a single docker compose file, updating the
-documentation, and replacing a pre-existing service with a Ruby example.
-Otherwise the pre-existing feature set from the GCP demo remains the same:
+documentation, and replacing a preexisting service with a Ruby example.
+Otherwise the preexisting feature set from the GCP demo remains the same:
 
 - 10 application microservice with support for 6 languages (C#, Go, Java,
   Node.js, Python, and Ruby)

@@ -57,8 +57,7 @@ Please, give us your **feedback** (using your preferred method):
 
 - [Submit a GitHub issue](https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/issues/new).
 - Write to us on [Slack](https://cloud-native.slack.com/archives/C01NR1YLSE7).
-  If you are new, you can create a CNCF Slack account
-  [here](https://slack.cncf.io/).
+  If you are new, you can [create a CNCF Slack account](https://slack.cncf.io/).
 
 [^devopsnote]:
     The

@@ -30,5 +30,4 @@ Please, give us your feedback (using your preferred method):
 
 - [Submit a GitHub issue](https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/issues/new).
 - Write to us on [Slack](https://cloud-native.slack.com/archives/C01NR1YLSE7).
-  If you are new, you can create a CNCF Slack account
-  [here](https://slack.cncf.io/).
+  If you are new, you can [create a CNCF Slack account](https://slack.cncf.io/).
@@ -53,16 +53,16 @@ Slack `#opentelemetry` channel.
 
 Upcoming sessions:
 
-- **EMEA**: every third Tuesday of the month at 11AM CET (GMT +1), join
-  [here](https://us06web.zoom.us/j/85691064809?pwd=c0VCejh)
+- **[EMEA](https://us06web.zoom.us/j/85691064809?pwd=c0VCejh)**: every third
+  Tuesday of the month at 11AM CET (GMT +1)
   - December 20, 2022
   - January 17, 2023
-- **APAC**: every third Wednesday of the month at 11AM IST (GMT +5.5), join
-  [here](https://us06web.zoom.us/j/82702918447?pwd=WllKc0hmdTNuelhFdlhMM1Q3TktSQT09)
+- **[APAC](https://us06web.zoom.us/j/82702918447?pwd=WllKc0hmdTNuelhFdlhMM1Q3TktSQT09)**:
+  every third Wednesday of the month at 11AM IST (GMT +5.5)
   - March 15, 2023 ([register here](https://lu.ma/1w129wgu))
   - April 19, 2023
-- **AMER**: every third Thursday of the month at 9AM PST (GMT -8), join
-  [here](https://us06web.zoom.us/j/87037874951?pwd=WGo3eUZpeWFZTlhJQXhJeXZhQmwvUT09)
+- **[AMER](https://us06web.zoom.us/j/87037874951?pwd=WGo3eUZpeWFZTlhJQXhJeXZhQmwvUT09)**:
+  every third Thursday of the month at 9AM PST (GMT -8)
   - December 15, 2022
   - January 19, 2023
 

@@ -34,8 +34,8 @@ October 2022 23:59 UTC on
 [Helios Voting](https://vote.heliosvoting.org/helios/elections/76558134-3384-11ed-8688-02871af94755/view);
 voters will need to sign in with their GitHub account.
 
-To learn more about the election process, read about all of the details
-[here](https://github.com/open-telemetry/community/blob/main/elections/2022/governance-committee-election.md).
+For more information, see the
+[OpenTelemetry 2022 Governance Committee election](https://github.com/open-telemetry/community/blob/main/elections/2022/governance-committee-election.md).
 
 ## Interested in joining the Governance Committee?
 
@@ -48,9 +48,9 @@ refer to the
 [charter document](https://github.com/open-telemetry/community/blob/main/governance-charter.md).
 You may nominate yourself (or others!) by submitting a Pull Request against the
 [list of candidates](https://github.com/open-telemetry/community/blob/main/elections/2022/governance-committee-candidates.md)
-by 7 October 2022 23:59 UTC — more detailed requirements about the nomination
-and ratification process can be found
-[here](https://github.com/open-telemetry/community/blob/main/elections/2022/governance-committee-election.md).
+by 7 October 2022 23:59 UTC — see the detailed requirements under
+[nominations](https://github.com/open-telemetry/community/blob/main/elections/2022/governance-committee-election.md#nominations)
+for the Governance Committee election.
 
 We would like to thank the GC members who have helped grow OpenTelemetry, and
 invite them to run for re-election if they so choose: Alolita Sharma, Daniel

@@ -65,7 +65,7 @@ The simpler and automatic approach is by adding tracing to your application with
 no changes or additions into your application code. You also don't need to add
 any dependencies to OpenTelemetry specific libraries. It is possible by using
 the OpenTelemetry agent you can download from
-[here](https://github.com/open-telemetry/opentelemetry-java-instrumentation/releases).
+[opentelemetry-java-instrumentation/releases](https://github.com/open-telemetry/opentelemetry-java-instrumentation/releases).
 This agent has to run alongside your application in order to inject the logic
 for tracing messages sent and received to/from a Kafka cluster.
 

@@ -4,9 +4,9 @@ linkTitle: Instrument Nginx
 date: 2022-08-22
 author: >-
   [Debajit Das](https://github.com/debajitdas), [Kumar
-  Pratyus](https://github.com/kpratyus), [Severin
+  Pratyush](https://github.com/kpratyus), [Severin
   Neumann](https://github.com/svrnm) (Cisco)
-cSpell:ignore: Debajit Kumar Pratyus webserver
+cSpell:ignore: Debajit Kumar Pratyush webserver
 ---
 
 Apache HTTP Server and NGINX are the most popular web servers. It's most likely

@@ -48,8 +48,8 @@ Below are the repositories that we’ll be using for today’s tutorial:
 
 - My modified [HashiQube Repository](https://github.com/avillela/hashiqube)
   (fork of [servian/hashiqube](https://github.com/servian/hashiqube)). If you’re
-  curious, you can see what modifications I’ve made
-  [here](https://github.com/avillela/hashiqube).
+  curious, you can see
+  [the modifications I’ve made to hashiqube](https://github.com/avillela/hashiqube/commits).
 - My [Nomad Conversions](https://github.com/avillela/nomad-conversions)
   repository
 
@@ -91,8 +91,8 @@ to add the following entries to `/etc/hosts` on your host machine:
 
 #### 2- Provision a Local Hashi Environment with HashiQube
 
-Start HashiQube by following the detailed instructions
-[here](https://github.com/avillela/hashiqube#quickstart).
+Start HashiQube by following the detailed
+[Quickstart instructions](https://github.com/avillela/hashiqube#quickstart).
 
 > **NOTE:** Be sure to check out the
 > [Gotchas](https://github.com/avillela/hashiqube#gotchas) section, if you get

@@ -222,8 +222,8 @@ separate processors to do tail sampling will be more performant than just the
 tail sampling processor. It's important to note that nothing will be released
 without a backward-compatible solution. For the collector, there are limited
 options to monitor the collector, which is critical for troubleshooting. See
-[here](https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/troubleshooting.md#observability)
-for more information.
+[Collector Troubleshooting](/docs/collector/troubleshooting/) for more
+information.
 
 _A version of this article was [originally posted][] on the New Relic blog._
 

@@ -1,5 +1,5 @@
 ---
-title: OpenTelemetry Erlang/Elixir, Javascript, and Ruby v1.0 (Medium)
+title: OpenTelemetry Erlang/Elixir, JavaScript, and Ruby v1.0 (Medium)
 linkTitle: Erlang/Elixir, JS, and Ruby 1.0
 date: 2022-02-01
 canonical_url: https://medium.com/opentelemetry/opentelemetry-erlang-elixir-javascript-and-ruby-v1-0-3a0c32e0add4

@@ -53,19 +53,21 @@ don't. This usually means that I have to do a bit more digging beyond the docs,
 by seeking out external blog posts, bugging techie friends, etc. Once I'm able
 to fill that knowledge gap, I do two things:
 
-1. I blog about it. See examples [here](https://shorturl.at/vLYZ0),
-   [here](https://shorturl.at/hlqtE), and [here](https://shorturl.at/czHST).
+1. I blog about it. See examples
+   [OTel Python Logging Auto-Instrumentation with the OTel Operator](https://medium.com/cloud-native-daily/lets-learn-about-otel-python-logging-auto-instrumentation-with-the-otel-operator-663247666570)
+   and
+   [Let’s Learn About the OTel Operator’s Target Allocator!](https://adri-v.medium.com/lets-learn-about-the-otel-operator-s-target-allocator-47a2b1f07562).
 2. I contribute to the OTel docs. See examples
-   [here](https://github.com/open-telemetry/opentelemetry.io/pull/3195),
-   [here](https://github.com/open-telemetry/opentelemetry.io/pull/3098), and
-   [here](https://github.com/open-telemetry/opentelemetry.io/pull/2130).
+   [Include docs about Python logs auto-instrumentation](https://github.com/open-telemetry/opentelemetry.io/pull/3195),
+   [Add troubleshooting guidance to OTel Operator auto-instrumentation docs](https://github.com/open-telemetry/opentelemetry.io/pull/3098),
+   and
+   [Update Python auto-instrumentation docs](https://github.com/open-telemetry/opentelemetry.io/pull/2130).
 
 > ✨ **NOTE:** ✨ Number two is _especially_ important, because the best way for
 > the OTel docs to be the Source of Truth for All Things OTel<sup>TM</sup> is to
 > have folks like us contributing to the docs whenever we see a gap.
 
-Learn more about contributing to the OTel docs
-[here](https://github.com/open-telemetry/opentelemetry.io/blob/main/CONTRIBUTING.md).
+Learn more about [contributing to the OTel docs](/docs/contributing/).
 
 > ✨ **NOTE:** ✨ If you find the contribution guidelines for the OTel Docs to
 > be confusing or have a mistake, improving them is a great way to contribute!
@@ -81,11 +83,10 @@ community at large. As long as your work isn't promoting a product you're
 selling or requires readers to make a purchase in order to replicate your work,
 your blog post is most welcome!
 
-You can check out an example of one of my previous blog posts
-[here](/blog/2022/otel-demo-app-nomad/).
+You can check out an example of one of my previous blog posts:
+[Running the OpenTelemetry Demo App on HashiCorp Nomad](/blog/2022/otel-demo-app-nomad/).
 
-Learn more about submitting a post to the OTel blog
-[here](https://github.com/open-telemetry/opentelemetry.io#submitting-a-blog-post).
+Learn more about [submitting a post to the OTel blog](/docs/contributing/blog/).
 
 ### Join the OTel End User Working Group
 
@@ -105,7 +106,7 @@ OpenTelemetry practitioners who come together a few times a month to:
 
 As an added bonus, I'm one of the co-chairs. Just sayin'… 😉
 
-Learn more about the OTel EUWG [here](/community/end-user/).
+Learn more about the [OTel EUWG](/community/end-user/).
 
 ### Contribute to the OpenTelemetry Demo
 
@@ -133,10 +134,10 @@ greatest versions of things like the [OTel Collector](/docs/collector/) and
 language-specific instrumentation. In short, there's always work to be done!
 
 You can check out an example of one of my contributions
-[here](https://github.com/open-telemetry/opentelemetry-demo/pull/432).
+[Integrate with existing metrics code](https://github.com/open-telemetry/opentelemetry-demo/pull/432).
 
-Learn more about how to contribute to the OTel Demo
-[here](https://github.com/open-telemetry/opentelemetry-demo/blob/main/CONTRIBUTING.md).
+Learn more about how to
+[contribute to the OTel Demo](https://github.com/open-telemetry/opentelemetry-demo/blob/main/CONTRIBUTING.md).
 
 ### Join a Special Interest Group
 
@@ -168,9 +169,9 @@ community member to implement these types of code changes. I've found folks
 within OTel to be nothing but helpful and welcoming.
 
 You can check out an example of one of my contributions
-[here](https://github.com/open-telemetry/opentelemetry-helm-charts/pull/531).
+[Specify gRPC endpoint in otlp receiver config](https://github.com/open-telemetry/opentelemetry-helm-charts/pull/531).
 
-Learn more about the OTel SIGs [here](/community/#special-interest-groups).
+Learn more about the [OTel SIGs](/community/#special-interest-groups).
 
 ### Final thoughts
 

@@ -88,8 +88,8 @@ different backends, what’s the best way to go about it?
 [Connectors](https://github.com/open-telemetry/opentelemetry-collector/pull/6140)
 (a new Collector component that acts as an exporter/receiver pair to join
 pipelines together) can be used to solve this. Connectors will be launching
-soon. For more info, see the Connector PR
-[here](https://github.com/open-telemetry/opentelemetry-collector/pull/6372).
+soon. For more info, see the
+[Connector PR](https://github.com/open-telemetry/opentelemetry-collector/pull/6372).
 
 Another approach would be to use a
 [routing processor](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/routingprocessor).

@@ -134,8 +134,8 @@ out metrics in Prometheus format, you can configure your OTel Collector to
 scrape Prometheus metrics. There is also a
 [statsd receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/statsdreceiver)
 that is available. If you have something that is already working, then you don’t
-need to change it. You can check the list of receivers
-[here](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver).
+need to change it. You can check the
+[list of receivers](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver).
 
 #### 2 - Emitting business metrics
 
@@ -195,9 +195,8 @@ endpoints via the Kubernetes API.
 Azure to collect telemetry from Azure App Services and Azure functions?
 
 **A:** Usually, the community relies on folks from Microsoft to provide best
-practices. There is some issue with the latest version of OTel and Azure
-functions. You can track it
-[here](https://github.com/Azure/azure-functions-host/issues/8938).
+practices. There was an
+[issue with the 1.4 version of OTel and Azure functions 7](https://github.com/Azure/azure-functions-host/issues/8938).
 
 ## Meeting Notes & Recordings
 

@@ -265,8 +265,9 @@ to Jaeger.
 
 ## What's next?
 
-If you’d like to see my conversation with Doug in full, you can check out the
-video [here](https://www.youtube.com/watch?v=ptYWBF-R1Fc).
+If you’d like to see my conversation with Doug in full, there is a
+[private video](https://www.youtube.com/watch?v=ptYWBF-R1Fc) -- you’ll have to
+ask someone for permission to be able to watch it.
 
 If anyone would like to continue the conversation with Doug, please reach out to
 him in the