Address feedback

Signed-off-by: Bogdan Drutu <bogdandrutu@gmail.com>

Author: bogdandrutu

releases/new-telemetry-release-process-template.md releases/new-signal-release-process-template.md

@@ -1,12 +1,10 @@
-# Technical Review and Specification Conformance for ${Language}/${TELEMETRY}/${MAJOR_VERSION} library
+# Technical Review and Specification Conformance for ${Language}/${SIGNAL}/${MAJOR_VERSION} library
 
 Technical Committee Sponsor(s): []
 
-Status: [PROPOSAL|REJECTED|APPROVED]
-
 Expected Release Date: []
 
-Spec Compliance Matrix is up to date: [YES|NO]
+Spec Compliance Matrix is up to date: [Permanent link to the matrix]
 
 Versioning And Stability Document: [LINK to version document]
 
@@ -24,7 +22,7 @@ The Language Maintainers MUST:
 
 * Prior to starting the review, update the
 [compliance matrix](https://github.com/open-telemetry/opentelemetry-specification/blob/main/spec-compliance-matrix.md)
-for that language/telemetry.
+for that language/signal.
 * Each language implementation MUST follow
 [the versioning and stability requirements](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/versioning-and-stability.md)
 and prepare the public documentation about the versioning and stability guarantees.
@@ -43,6 +41,6 @@ ensure specification conformance.
 * Ensure conformance with the versioning and stability document.
 * Ensure consistent names across implementations (e.g. TraceId vs Id)
 * Avoid confusions across implementation (e.g same function returns has different behaviors)
-* Ensure no experimental features (signals) are part of the main API package.
+* Ensure no experimental features (signals) are part of the released packages (e.g. api, sdk, etc.).
 
 The OpenTelemetry Technical Committee MUST attend one of the language SIG meetings and have a public discussion with the language maintainers to discuss any issues found during the review process.

releases/new-telemetry-release-process.md releases/new-signal-release-process.md

@@ -1,4 +1,4 @@
-# New Telemetry Release Process
+# New Signal Release Process
 
 This document defines the release requirements and process followed by the
 OpenTelemetry libraries, along with the rules and procedures for meeting those
@@ -10,9 +10,9 @@ refer to the specification or the Collector in this document.
 
 Every OpenTelmetry official major release MUST follow the release process
 proposed in this document. A  "major release" refers to a new version of any
-telemetry type (adding a new telemetry type to an already released major version
-of the library, or a major version bump for an existing telemetry type) for
-OpenTelemetry client libraries.
+[signal](../specification/glossary.md#signals) (adding a new signal to an
+already released major version of the library, or a major version bump for an
+existing signal release) for OpenTelemetry client libraries.
 
 The OpenTelemetry [Technical Committee](https://github.com/open-telemetry/community/blob/main/tech-committee-charter.md) (with guidance from language maintainers) is responsible to setup release dates
 and ensure quality standards of the official releases
@@ -32,8 +32,8 @@ commits to ensure that every decision will be made in less than 14 days after
 the process is started.
 
 To begin the technical and specification compliance review language maintainers
-MUST submit a PR and complete this [template](new-telemetry-release-process-template.md).
-The name of the file MUST be `technical-specification-review-${language}.md`.
+MUST submit a PR and complete this [template](new-signal-release-process-template.md).
+The name of the file MUST be `release-review-${language}-${signal}.md`.
 
 During the review process, breaking changes MAY be needed to comply with the
 specification, it is highly recommended to start the process as soon as possible,