Run text lint on the content

Author: thompson-tomo

CHANGELOG.md

@@ -375,7 +375,7 @@ release.
 - Define syntax for escaping declarative configuration environment variable
   references.
   ([#4375](https://github.com/open-telemetry/opentelemetry-specification/pull/4375))
-- Resolve various declarative config TODOs.
+- Resolve various declarative config todos.
   ([#4394](https://github.com/open-telemetry/opentelemetry-specification/pull/4394))
 
 ## v1.41.0 (2025-01-21)
@@ -508,7 +508,7 @@ release.
   ([#4203](https://github.com/open-telemetry/opentelemetry-specification/pull/4203))
   ([#4221](https://github.com/open-telemetry/opentelemetry-specification/pull/4221))
 - Introduce initial placeholder for the new user-facing Logs API, adding references
-  to existing API's informing of the coming changes while the definition is defined.
+  to existing APIs informing of the coming changes while the definition is defined.
   ([#4236](https://github.com/open-telemetry/opentelemetry-specification/pull/4236))
 
 ### Common
@@ -709,7 +709,7 @@ release.
   ([#4001](https://github.com/open-telemetry/opentelemetry-specification/pull/4001))
 - Error out on invalid identifiers in environment variable substitution.
   ([#4002](https://github.com/open-telemetry/opentelemetry-specification/pull/4002))
-- Add end to end examples for file configuration
+- Add end-to-end examples for file configuration
   ([#4018](https://github.com/open-telemetry/opentelemetry-specification/pull/4018))
 - Clarify the schema for YAML configuration files
   ([#3973](https://github.com/open-telemetry/opentelemetry-specification/pull/3973))
@@ -767,7 +767,7 @@ release.
   ([#3945](https://github.com/open-telemetry/opentelemetry-specification/pull/3945))
 - Prometheus: represent Prometheus Info, StateSet and Unknown-typed metrics in OTLP.
   ([#3868](https://github.com/open-telemetry/opentelemetry-specification/pull/3868))
-- Update and reorganize the prometheus sdk exporter specification.
+- Update and reorganize the prometheus SDK exporter specification.
   ([#3872](https://github.com/open-telemetry/opentelemetry-specification/pull/3872))
 
 ### SDK Configuration
@@ -918,7 +918,7 @@ release.
 
 ### Traces
 
-- Update OpenTelemetry to Zipkin Transformation to handle attributes from older semantic conventions in a backwards compatible way.
+- Update OpenTelemetry to Zipkin Transformation to handle attributes from older semantic conventions in a backward compatible way.
   ([#3794](https://github.com/open-telemetry/opentelemetry-specification/pull/3794))
 
 ### Metrics
@@ -1076,7 +1076,7 @@ release.
 
 ### Logs
 
-- Update two apache access logs mappings.
+- Update two Apache access logs mappings.
   ([#3712](https://github.com/open-telemetry/opentelemetry-specification/pull/3712))
 
 ### Resource
@@ -1545,7 +1545,7 @@ release.
 
 - Rename Logs API to Logs Bridge API to prevent confusion.
   ([#3197](https://github.com/open-telemetry/opentelemetry-specification/pull/3197))
-- Move event language from log README to event-api.
+- Move event language from log readme to event-api.
   ([#3252](https://github.com/open-telemetry/opentelemetry-specification/pull/3252))
 
 ### Resource
@@ -1646,10 +1646,10 @@ release.
 - Rename google openshift platform attribute from `google_cloud_openshift` to `gcp_openshift`
   to match the existing `cloud.provider` prefix.
   ([#3095](https://github.com/open-telemetry/opentelemetry-specification/pull/3095))
-- Changes http server span names from `{http.route}` to `{http.method} {http.route}`
+- Changes HTTP server span names from `{http.route}` to `{http.method} {http.route}`
   (when route is available), and from `HTTP {http.method}` to `{http.method}` (when
   route is not available).
-  Changes http client span names from `HTTP {http.method}` to `{http.method}`.
+  Changes HTTP client span names from `HTTP {http.method}` to `{http.method}`.
   ([#3165](https://github.com/open-telemetry/opentelemetry-specification/pull/3165))
 - Mark `http.server.duration` and `http.client.duration` metrics as required, and mark
   all other HTTP metrics as optional.
@@ -1699,7 +1699,7 @@ release.
 
 - Clarify that the BatchSpanProcessor should export batches when the queue reaches the batch size
   ([#3024](https://github.com/open-telemetry/opentelemetry-specification/pull/3024))
-- Deprecate jaeger exporter, scheduled for spec removal in July 2023.
+- Deprecate Jaeger exporter, scheduled for spec removal in July 2023.
   [#2858](https://github.com/open-telemetry/opentelemetry-specification/pull/2858)
 
 ### Metrics
@@ -1906,7 +1906,7 @@ release.
   ([#2874](https://github.com/open-telemetry/opentelemetry-specification/pull/2874))
 - Add `process.paging.faults` metric to semantic conventions
   ([#2827](https://github.com/open-telemetry/opentelemetry-specification/pull/2827))
-- Define semantic conventions yaml for non-otlp conventions
+- Define semantic conventions YAML for non-otlp conventions
   ([#2850](https://github.com/open-telemetry/opentelemetry-specification/pull/2850))
 - Add more semantic convetion attributes of Apache RocketMQ
   ([#2881](https://github.com/open-telemetry/opentelemetry-specification/pull/2881))
@@ -1958,7 +1958,7 @@ release.
 
 - Add environment variables for configuring the `BatchLogRecordProcessor`.
   ([#2785](https://github.com/open-telemetry/opentelemetry-specification/pull/2785))
-- Fix inconsistencies in log README
+- Fix inconsistencies in log readme
   ([#2800](https://github.com/open-telemetry/opentelemetry-specification/pull/2800)).
 
 ### Resource
@@ -1975,7 +1975,7 @@ release.
   ([#2819](https://github.com/open-telemetry/opentelemetry-specification/pull/2819))
 - Make context propagation requirements explicit for messaging semantic conventions
   ([#2750](https://github.com/open-telemetry/opentelemetry-specification/pull/2750)).
-- Update http metrics to use `http.route` instead of `http.target` for servers,
+- Update HTTP metrics to use `http.route` instead of `http.target` for servers,
   drop `http.url` for clients
   ([#2818](https://github.com/open-telemetry/opentelemetry-specification/pull/2818)).
 
@@ -2077,7 +2077,7 @@ release.
 - Add `rpc.grpc.status_code` to RPC metric semantic conventions
   ([#2604](https://github.com/open-telemetry/opentelemetry-specification/pull/2604))
 - Add `http.*.*.size` metric semantic conventions for tracking size of requests
-  / responses for http servers / clients
+  / responses for HTTP servers / clients
   ([#2588](https://github.com/open-telemetry/opentelemetry-specification/pull/2588))
 - BREAKING: rename `net.peer.ip` to `net.sock.peer.addr`, `net.host.ip` to `net.sock.host.addr`,
   `net.peer.name` to `net.sock.peer.name` for socket-level instrumentation.
@@ -2087,7 +2087,7 @@ release.
   ([#2650](https://github.com/open-telemetry/opentelemetry-specification/pull/2650))
 - Improve the definition of `state` attribute for metric `system.network.connections`
   ([#2663](https://github.com/open-telemetry/opentelemetry-specification/pull/2663))
-- Add `process.parent_pid` attribute for use in reporting parent process id (PID)
+- Add `process.parent_pid` attribute for use in reporting parent process ID (PID)
   ([#2691](https://github.com/open-telemetry/opentelemetry-specification/pull/2691))
 - Add OpenSearch to db.system semantic conventions
   ([#2718](https://github.com/open-telemetry/opentelemetry-specification/pull/2718))
@@ -2174,7 +2174,7 @@ release.
   ([#2536](https://github.com/open-telemetry/opentelemetry-specification/pull/2536))
 - Add database connection pool metrics semantic conventions
   ([#2273](https://github.com/open-telemetry/opentelemetry-specification/pull/2273)).
-- Specify how to obtain a Ruby thread's id
+- Specify how to obtain a Ruby thread's ID
   ([#2508](https://github.com/open-telemetry/opentelemetry-specification/pull/2508)).
 - Refactor jvm classes semantic conventions
   ([#2550](https://github.com/open-telemetry/opentelemetry-specification/pull/2550)).
@@ -2244,8 +2244,8 @@ release.
 ### Semantic Conventions
 
 - Note added that `net.peer.name` SHOULD NOT be set if capturing it would require an
-  extra reverse DNS lookup. And moved `net.peer.name` from common http attributes to
-  just client http attributes.
+  extra reverse DNS lookup. And moved `net.peer.name` from common HTTP attributes to
+  just client HTTP attributes.
   ([#2446](https://github.com/open-telemetry/opentelemetry-specification/pull/2446))
 - Add `net.host.name` and `net.host.ip` conventions for rpc server spans.
   ([#2447](https://github.com/open-telemetry/opentelemetry-specification/pull/2447))
@@ -2484,7 +2484,7 @@ release.
   ([#2191](https://github.com/open-telemetry/opentelemetry-specification/pull/2191))
 - Add `device.manufacturer` to describe mobile device manufacturers.
   ([2100](https://github.com/open-telemetry/opentelemetry-specification/pull/2100))
-- Change golang namespace to 'go', rather than 'gc'
+- Change Go namespace to 'go', rather than 'gc'
   ([#2262](https://github.com/open-telemetry/opentelemetry-specification/pull/2262))
 - Add JVM memory runtime semantic
   conventions. ([#2272](https://github.com/open-telemetry/opentelemetry-specification/pull/2272))
@@ -2579,11 +2579,11 @@ release.
   ([#2004](https://github.com/open-telemetry/opentelemetry-specification/pull/2004))
 - Add Tencent Cloud as a cloud provider.
   ([#2006](https://github.com/open-telemetry/opentelemetry-specification/pull/2006))
-- Don't set Span.Status for 4xx http status codes for SERVER spans.
+- Don't set Span.Status for 4xx HTTP status codes for SERVER spans.
   ([#1998](https://github.com/open-telemetry/opentelemetry-specification/pull/1998))
 - Add attributes for Apache RocketMQ.
   ([#1904](https://github.com/open-telemetry/opentelemetry-specification/pull/1904))
-- Define http tracing attributes provided at span creation time
+- Define HTTP tracing attributes provided at span creation time
   ([#1916](https://github.com/open-telemetry/opentelemetry-specification/pull/1916))
 - Change meaning and discourage use of `faas.trigger` for FaaS clients (outgoing).
   ([#1921](https://github.com/open-telemetry/opentelemetry-specification/pull/1921))
@@ -2596,7 +2596,7 @@ release.
 
 ### OpenTelemetry Protocol
 
-- Clarify default for OTLP endpoint should, not must, be https
+- Clarify default for OTLP endpoint should, not must, be HTTPS
   ([#1997](https://github.com/open-telemetry/opentelemetry-specification/pull/1997))
 - Specify the behavior of the OTLP endpoint variables for OTLP/HTTP more strictly
   ([#1975](https://github.com/open-telemetry/opentelemetry-specification/pull/1975),
@@ -2662,7 +2662,7 @@ Added telemetry schemas documents to the specification ([#2008](https://github.c
 - Update YAML definitions for events
   ([#1843](https://github.com/open-telemetry/opentelemetry-specification/pull/1843)):
   - Mark exception as semconv type "event".
-  - Add YAML definitions for grpc events.
+  - Add YAML definitions for gRPC events.
 - Add `messaging.consumer_id` to differentiate between message consumers.
   ([#1810](https://github.com/open-telemetry/opentelemetry-specification/pull/1810))
 - Clarifications for `http.client_ip` and `http.host`.
@@ -2874,14 +2874,14 @@ Added telemetry schemas documents to the specification ([#2008](https://github.c
 
 ### Logs
 
-- Clarify "key/value pair list" vs "map" in Log Data Model. ([#1604](https://github.com/open-telemetry/opentelemetry-specification/pull/1604))
+- Clarify "key-value pair list" vs "map" in Log Data Model. ([#1604](https://github.com/open-telemetry/opentelemetry-specification/pull/1604))
 
 ### Semantic Conventions
 
 - Fix the inconsistent formatting of semantic convention enums. ([#1598](https://github.com/open-telemetry/opentelemetry-specification/pull/1598/))
 - Add details for filling resource for AWS Lambda. ([#1610](https://github.com/open-telemetry/opentelemetry-specification/pull/1610))
 - Add already specified `messaging.rabbitmq.routing_key` span attribute key to the respective YAML file. ([#1651](https://github.com/open-telemetry/opentelemetry-specification/pull/1651))
-- Clarify usage of "otel." attribute namespace. ([#1640](https://github.com/open-telemetry/opentelemetry-specification/pull/1640))
+- Clarify usage of "OTel." attribute namespace. ([#1640](https://github.com/open-telemetry/opentelemetry-specification/pull/1640))
 - Add possibility to disable `db.statement` via instrumentation configuration. ([#1659](https://github.com/open-telemetry/opentelemetry-specification/pull/1659))
 
 ### Compatibility
@@ -3020,7 +3020,7 @@ Updates:
 - Resource attributes: lowerecased the allowed values of the `aws.ecs.launchtype`
   attribute
   ([#1339](https://github.com/open-telemetry/opentelemetry-specification/pull/1339))
-- Trace Exporters: Fix TODOs in Jaeger exporter spec
+- Trace Exporters: Fix todos in Jaeger exporter spec
   ([#1374](https://github.com/open-telemetry/opentelemetry-specification/pull/1374))
 - Clarify that Jaeger/Zipkin exporters must rely on the default Resource to
   get service.name if none was specified.
@@ -3077,7 +3077,7 @@ New:
     [#946](https://github.com/open-telemetry/opentelemetry-specification/pull/946))
 - Allow samplers to modify tracestate
   ([#988](https://github.com/open-telemetry/opentelemetry-specification/pull/988/))
-- Update the header name for otel baggage, and version date
+- Update the header name for OTel baggage, and version date
   ([#981](https://github.com/open-telemetry/opentelemetry-specification/pull/981))
 - Define PropagationOnly Span to simplify active Span logic in Context
   ([#994](https://github.com/open-telemetry/opentelemetry-specification/pull/994))
@@ -3134,12 +3134,12 @@ Updates:
   ([#610](https://github.com/open-telemetry/opentelemetry-specification/pull/610))
 - Rename ProbabilitySampler to TraceIdRatioBasedSampler and add requirements
   ([#611](https://github.com/open-telemetry/opentelemetry-specification/pull/611))
-- Version attributes no longer have a prefix such as semver:
+- Version attributes no longer have a prefix such as SemVer:
   ([#873](https://github.com/open-telemetry/opentelemetry-specification/pull/873))
 - Add semantic conventions for process runtime
   ([#882](https://github.com/open-telemetry/opentelemetry-specification/pull/882),
    [#1137](https://github.com/open-telemetry/opentelemetry-specification/pull/1137))
-- Use hex encoding for trace id and span id fields in OTLP JSON encoding:
+- Use hex encoding for trace ID and span ID fields in OTLP JSON encoding:
   ([#911](https://github.com/open-telemetry/opentelemetry-specification/pull/911))
 - Explicitly specify the SpanContext APIs IsValid and IsRemote as required
   ([#914](https://github.com/open-telemetry/opentelemetry-specification/pull/914))
@@ -3185,7 +3185,7 @@ New:
   ([#650](https://github.com/open-telemetry/opentelemetry-specification/pull/650))
 - Add conventions for naming of exporter packages
   ([#629](https://github.com/open-telemetry/opentelemetry-specification/pull/629))
-- Add semantic conventions for container id
+- Add semantic conventions for container ID
   ([#673](https://github.com/open-telemetry/opentelemetry-specification/pull/673))
 - Add semantic conventions for HTTP content length
   ([#641](https://github.com/open-telemetry/opentelemetry-specification/pull/641))
@@ -3224,7 +3224,7 @@ Updates:
 - Update api-metrics-user.md and api-metrics-meter.md with the latest metrics
   API.
 - Normalize Instrumentation term for instrumentations.
-- Change w3c correlation context to custom header.
+- Change W3C correlation context to custom header.
 
 ## v0.4.0 (2020-05-12)
 

CONTRIBUTING.md

@@ -19,7 +19,7 @@ Proposal](https://github.com/open-telemetry/oteps) process.
 Smaller changes can follow a shorter process:
 
 - [Create an issue](https://github.com/open-telemetry/opentelemetry-specification/issues/new/choose)
-  in this repo and describe the proposed change.
+  in this repository and describe the proposed change.
 - Follow the [issue workflow](#issue-triaging) and make sure the issue is accepted with
   a "Yes" response. If the response to the issue is not "Yes" then do not create a PR
   that implements the change since it will be rejected.
@@ -49,7 +49,7 @@ issue.
 
 ## Writing specs
 
-Specification is written in markdown format. Please make sure files are rendered
+Specification is written in Markdown format. Please make sure files are rendered
 correctly on GitHub.
 
 Be sure to clearly define the specification requirements using appropriate
@@ -131,7 +131,7 @@ In this repository we follow the
 with some customizations. See [markdownlint](.markdownlint.yaml) or
 [settings](.vscode/settings.json) for details.
 
-We highly encourage to use line breaks in markdown files at `80` characters
+We highly encourage to use line breaks in Markdown files at `80` characters
 wide. There are tools that can do it for you effectively. Please submit proposal
 to include your editor settings required to enable this behavior so the out of
 the box settings for this repository will be consistent.
@@ -146,7 +146,7 @@ To fix style violations, follow the
 [instruction](https://github.com/DavidAnson/markdownlint#optionsresultversion)
 with the Node version of markdownlint. If you are using Visual Studio Code,
 you can also use the `fixAll` command of the
-[vscode markdownlint extension](https://github.com/DavidAnson/vscode-markdownlint).
+[Visual Studio Code markdownlint extension](https://github.com/DavidAnson/vscode-markdownlint).
 
 ### Text Correction
 
@@ -160,7 +160,7 @@ make language-analysis
 
 > [!NOTE]
 > The `misspell` make target will also fetch and build the tool if
-> necessary. You'll need [Go](https://go.dev) to build the spellchecker.
+> necessary. You'll need [Go](https://go.dev) to build the spell checker.
 
 To quickly common misspellings and style, use
 
@@ -223,7 +223,7 @@ pull requests (PRs).
 
 To [create a new
 PR](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request),
-fork the project in GitHub and clone the upstream repo:
+fork the project in GitHub and clone the upstream repository:
 
 ```sh
 git clone https://github.com/open-telemetry/opentelemetry-specification.git
@@ -244,7 +244,7 @@ $ git commit
 $ git push fork feature
 ```
 
-Open a pull request against the main `opentelemetry-specification` repo.
+Open a pull request against the main `opentelemetry-specification` repository.
 
 If the PR is not ready for review, please mark it as
 [`draft`](https://github.blog/news-insights/product-news/introducing-draft-pull-requests/).

README.md

@@ -29,7 +29,7 @@ APAC timezone friendly meetings are held on request. See
 [OpenTelemetry calendar](https://github.com/open-telemetry/community#calendar).
 
 Escalations to technical committee may be made over the
-[e-mail](https://github.com/open-telemetry/community/blob/main/README.md#mailing-lists).
+[email](https://github.com/open-telemetry/community/blob/main/README.md#mailing-lists).
 Technical committee holds regular meetings, notes are held
 [here](https://docs.google.com/document/d/1hOHPCu5TGenqTeWPB9qQB_qd33uITZBcvK1FnWxYJAw/edit?usp=sharing).