Update environment variable descriptions to match signal #4222
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Hi Python! 👋 I'm normally in Rubyland, but today I'm investigating OpenTelemetry implementations across different languages to learn more about how they manage configuration. While I was reading
opentelemetry-sdk/src/opentelemetry/sdk/environment_variables/__init__.py
, I realized some of the documentation might reference the wrong signals. It seems like they were minor copy/paste oversights.Type of change
How Has This Been Tested?
Since this is a documentation update, I haven't attempted to test the changes. Happy to find a way to do so if this is required.
Does This PR Require a Contrib Repo Change?
Checklist: