Improving readability and tone by removing superfluous terms

[puneet-ekline]

Description
Avoid words that assume a specific level of understanding
Reference: https://kubernetes.io/docs/contribute/style/style-guide/#avoid-words-that-assume-a-specific-level-of-understanding

More details about EkLine.io here

[puneet-ekline]

Thanks for the feedback, @shaun-cox and @theletterf. Agree to all of it. Will keep in mind for future PRs :)

[puneet-ekline]

@austinlparker, These commits were created using EkLine's style guide platform. We imported the Kubernetes and OpenTelemetry style guide onto our platform. This configured the engine to detect adherence issues and recommend improvements to bring the docs in line with style guide standards. Then I applied those suggestions and raised a pull request for them.

[ericmustin]

we wanted flying cars instead we got gpu credits being set on fire to do half baked style linting

[theletterf]

@svrnm I'd say let's merge this one?

[svrnm]

@svrnm I'd say let's merge this one?

I think we need to hold back for a while to decide if/how we accept such a PR

[svrnm]

Following up on this based on a decision by @open-telemetry/governance-committee and @open-telemetry/technical-committee: we will review / accept / reject this (and #5164) based on their merit, but we do not want to be part of any sales pitch or growth hacking by this tool vendor (ekline) or any other tool vendor.

If we merge this PR we expect OpenTelemetry to not be mentioned in any written or verbal sales or marketing communication.

A pull request to an open source project is not the right place for any sales motion, the advertisement of a tool, and the offering of any (free) licenses we could obtain for it.

[svrnm]

A few inline comments

[svrnm]

Here the "simple" was more in the sense of "minimal" or "basic", since the setup does not provide a feature richt functionality. A different word may be a better choice.